masquerading domain name 1170

On 17 Apr 2006 12:27:31 -0700, Liam staggered into the Black Sun and said:

Postfix and Exim are just a tiny bit easier to configure and understand, IMHO.

What does that mean? Specifics, please. Did you mean "mail.example.com has IP 1.2.3.4, but 1.2.3.4 is the firewall, and the firewall forwards 1.2.3.4:25 to 192.168.1.5"? It's usually considered bad form to have a machine without a name. People usually have an easier time dealing with "fuzzball.example.com just fell over!" than "192.168.1.5 just fell over!".

This sounds like a bad rDNS record. The routable IP your mail appears to be coming from *must* have a valid rDNS record, or a number of large places like AOL will reject all mail from that IP. (rDNS lets you do "host 1.2.3.4" and get "somewhere.example.com". Go to a machine outside your LAN and make sure you can do a host on your routable IP(s) and get a valid response.) Note, if you send all your traffic through one gateway-firewall, and that gateway-firewall has multiple routable IPs buttigned to one interface, the *first* IP is typically where all the traffic appears to originate from. Make sure that IP has a valid rDNS.

If you run your own DNS, all you have to do is add a valid PTR record and restart named-whatever. If not, you have to call your ISP and either ask them to add a valid PTR record, or ask them to set up an RFC2317-style delegation. The former is generally easier for you and them, but less flexible.

Wrong thing to do.

Er, from what you told me, the problem isn't with the MTA configuration, but with remote users' ISPs policies and the lack of a good rDNS. BTDTGTTS. HTH anyway,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL