I have searched the subjects listed here and elsewhere, tried different things, but to no avail.
All emails go out of exchange except to those going to aol.com or comcast.net. This started occuing 2 weeks ago when our isp changed our static ip address. I know both aol & comcast require reverse-dns. My isp told me that the static ip address is set to reverse-dns.
Our email hosting (not hosted by our isp) has not changed. Our isp stated that it is probably an email hosting issue. Correct me if I'm wrong, but I thought Exchange sent the emails out directly and did not go through my email provider (that we use for pop3)
I have run telnet to both aol & comcast (using the ip listed in the event log) and I was able to connect from the SBS server. AOL gave me a message on reverse-DNS and then just waited for me with a blinking cursor. Comcast gave me the following message:
t comcast 220.127.116.11 Comcast requires
that all mail servers must have a PTR record with a valid Reverse DNS entry.
Currently your mail server does not fill that requirement. For more information,
refer to: http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18784
Connection to host lost.
From the Event-ID here are the warnings:
AOL Issue Event-ID 4007 for MSExchangeTransport
Message delivery to the host '18.104.22.168' failed while delivering to the remote domain 'aol.com' for the following reason: The connection was dropped due to an SMTP protocol event sink.
he SMTP verb which caused the error is 'quit'. The response from the remote server is ''.
Comcast Issue Event-ID 4006 for MSExchangeTransport
Message delivery to the host '22.214.171.124' failed while delivering to the remote domain 'comcast.net' for the following reason: An SMTP protocol error occurred.
I don't know if this is related, but I receive a DNS warning Event-ID 7062 though with different domains listed as well as symantec liveupdate.
The DNS server encountered a packet addressed to itself on IP address 192.168.1.254. The packet is for the DNS name "pop.emailsrvr.com.". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
If you have any solutions, take it easy on me with the terminology and procedures, I am not an expert at this.