unable to email to comcast.net or aol.com. I'm running exchange server 2003

I have tried to find out why I'm unable to email to comcast.net or aol.com. I can receive there emails I just cannot reply to them. I look into my Quenes and they are just sitting there unprocessed. I'm so frustrated because I cannot figure this one out. Please HELP!
Who is Participating?

Improve company productivity with a Business Account.Sign Up

ryansotoConnect With a Mentor Commented:
Your probably need to create a reverse DNS record with your ISP.  AOL and a few other providers require it to send to their domain
try this from the server

telnet smtp.aol.com

telnet smtp.comcast.com

Does it allow you to connect?
ATOGHAuthor Commented:
unable to open connection to port 23 and port 25
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Exchange_GeekConnect With a Mentor Commented:
"Success! It appears you have Reverse DNS. Please note the following points:
If the sender's domain is the only domain sending mail from a specific IP address, we recommend that the reverse DNS entry (PTR Record) match the domain name (A Record), but we do not require it.

AOL does require that all connecting Mail Transfer Agents have established reverse DNS, regardless of whether it matches the domain.

Reverse DNS must be in the form of a fully-qualified domain name. Reverse DNSes containing in-addr.arpa are not acceptable, as these are merely placeholders for a valid PTR record. Reverse DNSes consisting only of IP addresses are also not acceptable, as they do not correctly establish the relationship between domain and IP address."

Ref Link:

ATOGHAuthor Commented:
My ISP is small business yahoo/ sbcglobal
Thats fine just give them a call and tell them you need a reverse DNS created.
I am sure your ISP would be very very wel aware of such issues and wont mind creating a reverse dNS records in order to help you guys out.
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
1. ) whoever manages your public dns server, have them to register an A host record
           mysmtpmail.mydomain.com  >
2. ) Contact your ISP and have them to register a PTR record
    >    mysmtpmail.mydomain.com
3. ) make the necessary changes to the public FQDN on the exchange server ( as pointed out by feptias)

Go here and run a dns report for you domain to verify the records are setup properly.

you can always try changing your outgoing port to 587 that works with most ISP's
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.

All Courses

From novice to tech pro — start learning today.