>...
>
>List Mail User wrote:
>
>> Also, just curious, but do you have problems with the forward
>> and reverse DNS of you mail servers not mapping together (ex.
>> mail.dailykos.com
>> maps to 69.9.164.210, but the reverse of 69.9.164.210 is faye.voxel.net - in
>> particular do you have problems with ISPs like AOL?).
>
>I'm pretty sure AOL just requires a valid reverse DNS. They definitely
>don't require that the reverse DNS and the MX or the HELO match. Doing
>that would block a huge amount of legitimate mail, since many, many mail
>servers handle mail for multiple domains.
>
>--
>Keith C. Ivey <[EMAIL PROTECTED]>
>Washington, DC
>
Keith,
I handle mail for multiple domains, just the servers are 'MX's for
all of them. You can either HELO/EHLO with the machines hostname or the
machine can reverse map to an 'MX' for the name that you do use - both
cases are "legal" (I HELO/EHLO with plectere.com, but the machine will
always map back to some 'MX' for plectere.com, sine there is no 'A' record
for the bare domain) and while commonly ignored, one case or the other is
required by RFCs 2821/2. (This isn't any special or custom code, just the
Postfix options "reject_invalid_hostname", "reject_unknown_hostname" and
"reject_unknown_client" - I do require a RFC style match for a list of
large ISPs who are often forged, but is just the example list from the
Postfix distribution with about 5 companies I do business with added;
I long ago gave up on the general "reject_unverified_sender" option as
having too many problems with machines/domains run by clueless admins).
Paul Shupak
[EMAIL PROTECTED]
