Undelivereable - Bounced Mail- Dynamic IP, Smarthost Issues with Exchange 2003
Posted on 2008-01-26
I installed an Small Business Server 2003 at a location with a DSL connection that does not have a static IP, but a dynamic IP. Our ISP is Windstream/Alltel. Our web hosting company is SiteTurn. We have Exchange working and use Outlook 2007 and or Outlook Web Access. We can send and receive messages, BUT many messages go undelivered to such places as YAHOO, RoadRunner and a local ISP Modem Madness and others. Currently we are trying to use the "Default SMTP Virtual Server" configured to use a "Smart host" of mail.domainname.com and as directed by our hosting company outbound port 587 not port 25. (Not sure if the port matters) We use DYNDNS to provide DNS for our Windows 2003 Small Business Server, so that we can easily get to the Outlook Web Acess when on the road. Our Internet provider charges big $$ for a Static IP.
We use the POP3 connector in Exchange to download our mail to the Exchange server.
We try to use the Smart Host to route mail back to mail.domainname.com hosted on SiteTurn.
I believe the problem is that our web hosting company, SiteTurn holds our MX records and when we send mail our Exchange server cannot route the mail back to SiteTurn i.e. mail.domainname.com before going to the recipient thus it looks like SPAM to many recipients mail servers. We checked SPAMHAUS and we are not on a Blacklist. My mail/web hosting company is Infinology and I get the messages.
I don't believe I can have the MX record moved to our sever as it has a dynamic IP, yet a static name thanks to DYNDNS.com The message header on messages that ARE successfully sent indicates that our ISP is invloved in the sending of the message, yet there is no setting, that I am aware of, that uses our ISP. I am caught between a seperate web hosting company that also holds our mail records, a different ISP for our location and the home of the Small Business Server, and our Exchange server.
I am willing to purchase a outbound mail service if needed. DYNDNS sells such a service, but does not fully support Exchange so I am on my own to set this up and do not have enoungh experience with Exchange.
So my question is how can I resolve the undeliverable message problem in my scenario?