Re: Inbound email problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

DNS checks out OK.

Could it be that Qwest is blocking port 25 traffic? Probably not if
outbound mail works.

As a test, change the port that Exchange smtp listens on (and make sure you
port forward the new setting to your sbs external nic)

look at: http://support.microsoft.com/kb/274842

When is the last time you ran the CEICW? Maybe you should try that first.

Thanks,
Buddy G ~



"KC" <kcalfee@xxxxxxxxx> wrote in message
news:c0ff7746-03d1-4921-bdf8-e314e87ed5ff@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 16, 1:49 pm, "Buddy" <bu...@xxxxxxxxxxxxxxxxx> wrote:
What is the name of your company domain and what is the public ip address?
It sounds like they are not matching in DNS.
Can you telnet into your exchange server?
Do you have exchange server antispam or connection filtering enabled?

Buddy G ~

"KC" <kcal...@xxxxxxxxx> wrote in message

news:353019c8-68d4-4b57-9a04-5d3fb7a2672b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



I am running SBS 2003 Standard on a Dell PowerEdge 1800 with 2 NICs.
External NIC is connected to Qwest provided Actiontec GT701WG modem/
router. I can RWW, I can send email, I can receive pop mail for our
qwestoffice email addresses. I cannot receive inbound email if it is
sent to our company domain name address. I have a public static IP
with MX and A records setup. When I used dnsstuff to obtain a dns
report, the report indicated fail at connect to mail servers (Error: I
could not complete a connection to any of your mailservers) When I
did an email test I received the error "The mailserver terminated the
connection before the transaction was complete (state1). This is not
RFC compliant, and therefore either due to an error, or it may be the
result of a non-RFC-compliant mailserver or non-RFC-complaint anti-
spam program.

Any insight on what is creating my problem would be greatly
appreciated.- Hide quoted text -

- Show quoted text -

company domain: stpaulsumctucson.net
public IP: 65.101.185.33
no connection filtering enabled
Intelligent message filtering gateway blocking - block messages with
SCL rating greater than or equal to 8
Recipient filtering - filter recipients not in the directory
Telnet fails - error - Could not complete connection to host. on port
25: connect failed


.

Relevant Pages

  • dns queries...
    ... i've recently upgraded my internal server hardware, ... dns, however, being the only problem so far. ... after ssh'ing to a remote box i've ran nmap which is reporting the port to ... its almost like its half opening the connection. ...
    (alt.os.linux)
  • Re: fc3, sendmail, dovecot: cannot receive from outside
    ... The details of that connection are in the ... That has nothing to do with any DNS ... > will find their way to the LAN hosts with private block IPs? ... ID Public Port Private Port TCP/UDP Private Address ...
    (Fedora)
  • Re: blocking RFC 793 ports 1024-49151
    ... not much you can do about UDP, but for TCP just block all packets with the ... SYN bit set, except on the DNS, ftp and http ports. ... a TCP connection cannot be formed. ... The port numbers are chosen by the kernel, and as far as I know ...
    (comp.os.linux.security)
  • Re: blocking RFC 793 ports 1024-49151
    ... not much you can do about UDP, but for TCP just block all packets with the ... SYN bit set, except on the DNS, ftp and http ports. ... a TCP connection cannot be formed. ... The port numbers are chosen by the kernel, and as far as I know ...
    (comp.security.firewalls)
  • Re: blocking RFC 793 ports 1024-49151
    ... not much you can do about UDP, but for TCP just block all packets with the ... SYN bit set, except on the DNS, ftp and http ports. ... a TCP connection cannot be formed. ... The port numbers are chosen by the kernel, and as far as I know ...
    (comp.security.unix)