Using Exchange 2003 to send out to POP3 user accounts via web host provider
We have a situation where a company is running Windows Server 2003, using an internal domain of NAME.com. This company also has the same domain name (NAME.com) registered with a web hosting provider. The companies web site is hosted externally by this web provider. But the email MX records for NAME.com have been forwarded to the static IP of the company. On the Windows 2003 server is running exchange 2003 Server. This is the primary email system for the company. On the Exchange server, the SMTP connector is setup to send out email via standard DNS lookup, so other email servers see it being delivered by the static IP of the company.
This seemed to work fine for a few weeks. But now some mail sent from the company is being rejected by other email servers. The general error is "no authorization to send mail due to abuse". I've checked various blacklisting tools, and the only site to show any problem is a site called NOMOREFUNN. Here is the result of the spamcheck:
x.x.x.x was found in NOMOREFUNN! no-more-funn.moensted.dk -> 127.0.0.3 vnnyca.adelphia.net. Dynamic IP or generic rDNS. Use your ISPs mail service, or whitelist at: http://moensted.dk/spam/no-more-funn/?addr=x.x.x.x 1159792606 (Mon Oct 2 14:36:46 2006) # dul.dnsbl.sorbs.net
I had suspected that this might be a reverse DNS problem. The email server IP not matching the domain IP. So I attempted to add a POP3 account to every Outlook 2003 user, and make that the default account. The POP3 account is configured to send through email accounts created at the web hosting company. It seems to work, but I have 2 concerns. One - i don;t know 100% that this will sove the original blacklist problem. Two - Outlook has a stupid feature, where when you reply or forward an email, it uses the account that it was sent to. So even though the default account is POP3, it will send it to EExchange server account. I have also requested(via automatic script) to be removed from the blacklisted database at the nomorefunn site. But I still fear my blacklisting will not go away.
Can anyone please suggest the best approach for going back to a single Ezxchange 2003 solution with no POP3 accounts? Thanks.
Software/Hardware used:
Server 2003, Exchange 2003
This seemed to work fine for a few weeks. But now some mail sent from the company is being rejected by other email servers. The general error is "no authorization to send mail due to abuse". I've checked various blacklisting tools, and the only site to show any problem is a site called NOMOREFUNN. Here is the result of the spamcheck:
x.x.x.x was found in NOMOREFUNN! no-more-funn.moensted.dk -> 127.0.0.3 vnnyca.adelphia.net. Dynamic IP or generic rDNS. Use your ISPs mail service, or whitelist at: http://moensted.dk/spam/no-more-funn/?addr=x.x.x.x 1159792606 (Mon Oct 2 14:36:46 2006) # dul.dnsbl.sorbs.net
I had suspected that this might be a reverse DNS problem. The email server IP not matching the domain IP. So I attempted to add a POP3 account to every Outlook 2003 user, and make that the default account. The POP3 account is configured to send through email accounts created at the web hosting company. It seems to work, but I have 2 concerns. One - i don;t know 100% that this will sove the original blacklist problem. Two - Outlook has a stupid feature, where when you reply or forward an email, it uses the account that it was sent to. So even though the default account is POP3, it will send it to EExchange server account. I have also requested(via automatic script) to be removed from the blacklisted database at the nomorefunn site. But I still fear my blacklisting will not go away.
Can anyone please suggest the best approach for going back to a single Ezxchange 2003 solution with no POP3 accounts? Thanks.
Software/Hardware used:
Server 2003, Exchange 2003
ASKED:
April 1, 2010 2:43 AM
UPDATED:
April 1, 2010 11:24 AM
Answer Wiki:
First remove the POP3 accounts from the users Outlook configs. That is like trying to kill an ant with a hand grenade.
You need to change the forward and reverse DNS for your public IP that your exchange server is on to be the same name. It doesn't matter what the name is, so long as they match. It should be something like smtp.name.com. You'll probably need to contact your ISP and have them change the reverse DNS to this, then put a DNS entry in the public name.com DNS zone with the public IP and this name.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
