We are running an Exchang 2003 server. Our mail is relayed through frontbridge for spam blocking purposes for both incoming and outgoing mail and we have a Sonic Wall. We have been unsuccessful in sending email to a few domains and I cannot figure out why. We accept their mail, but cannot reply.
I tried to telnet the domain we are trying to email and the connection failed through port. 25.
Our SMTP on the exchange is set to Anonymous access and the SMTPDiag I ran threw back the following results:
C:\SMTP\SmtpDiag>smtpdiag "stacys@satty.com" "jdunn@fairwaymarket.com" /v
Searching for Exchange external DNS settings.
Computer name is EXCHANGE1.
VSI 1 has the following external DNS servers:
4.2.2.2
Checking SOA for fairwaymarket.com.
Checking external DNS servers.
Checking TCP/UDP SOA serial number using DNS server [4.2.2.2].
TCP test succeeded.
UDP test succeeded.
Serial number: 2008071563
Checking internal DNS servers.
Checking TCP/UDP SOA serial number using DNS server [127.0.0.1].
TCP test succeeded.
UDP test succeeded.
Serial number: 2008071555
Checking TCP/UDP SOA serial number using DNS server [167.206.112.3].
Failed: DNS server [167.206.112.3] may be down.
DNS server [167.206.112.3] did not return a valid SOA record.
SOA serial number match: Failed with one or more failures.
Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: satty.com.
A: satty.com [192.168.1.252]
Checking MX records using UDP: satty.com.
A: satty.com [192.168.1.252]
Both TCP and UDP queries succeeded. Local DNS test passed.
Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: fairwaymarket.com.
MX: mail.fairwaymarket.com (5)
A: mail.fairwaymarket.com [64.115.137.190]
Checking MX records using UDP: fairwaymarket.com.
MX: mail.fairwaymarket.com (5)
Both TCP and UDP queries succeeded. Remote DNS test passed.
Checking MX servers listed for jdunn@fairwaymarket.com.
Connecting to mail.fairwaymarket.com [64.115.137.190] on port 25.
Connecting to the server failed. Error: 10053
Failed to submit mail to mail.fairwaymarket.com.
I set a DNS on the SMTP on the exchange, but still have the problem. There are at least three domains we are getting this or similar messages from AND I checked for us on blacklists, but we are not listed on most.
Start Free Trial
