Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 666
  • Last Modified:

exchange 2003 cannot send to comcast.net

As of 48 hours (or so) ago, mail stopped flowing to comcast.net.  The queue for comcast.net in exchange server says "an smtp protocol error has occurred".

Mail has been flowing fine to comcast for years and now i cannot get mail to go to them.

Mail to all other domains flows fine.  

No changes to nameserver since October last year, Not blacklisted.  Nothing new done on server.  

Ideas?
0
AndyMT
Asked:
AndyMT
  • 4
  • 3
1 Solution
 
michaelgoldsmithCommented:
Try to telnet to their mail server from your mail server.
Also run SMTPdiag on your mail server to see what the error message is from their end. You may be blacklisted.
0
 
AndyMTAuthor Commented:
We are clean on all the blacklists.  Will telnet shortly.  Thanks
0
 
michaelgoldsmithCommented:
SMPTdiag will give you the error info you need to trace.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
AndyMTAuthor Commented:
Here's the results.  I had added Google's DNS servers earlier today in case the problem was there, but that made no difference.  I need education on the "serial numbers do not match".


C:\SmtpDiag>smtpdiag larry@balcombgreen.com mritrash@comcast.net

Searching for Exchange external DNS settings.
Computer name is SERVER.
VSI 1 has the following external DNS servers:
208.72.70.5,208.72.71.5,8.8.8.8,8.8.4.4

Checking SOA for comcast.net.
Checking external DNS servers.
Checking internal DNS servers.
Serial numbers do not match: 2008177974  2008177972
Serial numbers do not match: 2008177974  2008177972
Serial numbers do not match: 2008177974  2008177972
SOA serial number match: Failed with one or more failures.

Checking local domain records.
Checking MX records using TCP: balcombgreen.com.
Checking MX records using UDP: balcombgreen.com.
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Checking MX records using TCP: comcast.net.
Checking MX records using UDP: comcast.net.
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for mritrash@comcast.net.
Connecting to mx1.comcast.net [68.87.26.147] on port 25.
Error: Expected "220". Server is not accepting connections.
Failed to submit mail to mx1.comcast.net.
Connecting to mx2.comcast.net [76.96.40.147] on port 25.
Error: Expected "220". Server is not accepting connections.
Failed to submit mail to mx2.comcast.net.
0
 
AndyMTAuthor Commented:
Reran the same test with the "/v".  Turns out Comcast has the domain blacklisted even though it passes every blacklist check.  Problem solved I think.
0
 
michaelgoldsmithCommented:
Glad to see you resolved the issue. I suspected blacklist initially. Email them and they should get u removed within 24-48 hours.
0
 
AndyMTAuthor Commented:
Even though all the normal blacklists were clean, Comcast had blocked their domain.  Running SMTPDIAG /v gave me the info I needed to resolve the situation
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now