Hey Len, What I'm talking about isn't in the helo, it's in the data header. Trying to be able to distinguish the difference between:
### Received into postfix from external sender as: To: <username> getting rewritten into the following by trivial-rewrite: To: <[EMAIL PROTECTED]> VS: ### Received info postfix from external sender already as: To: <[EMAIL PROTECTED]> Or in other words: How do I monitor whether I am receiving this To: field in the data header from the sender with my gateway hostname already in it, or is my copy of Postfix rewriting it, appending $myorigin to an unqualified address during cleanup? I think if I understand the 'big picture' and related docs correctly that the former is happening, append_at_myorigin=yes will tack my gateway's hostname to any address in the data header to/cc/bcc fields that doesn't have @domain.tld on the end of it. For a relay-only server as IMGate is designed to be, this tends to be not only confusing for my userbase, but non-RFC compliant if I understand RFC2821 correctly, as a relay machine is supposed to add it's 'Received:' fields and not otherwise mess with it (again "if I understand the RFC correctly"). I don't think it is people forging my mx (at least not for most samples I've seen), I think it is simply a matter of my postfix seeing a partial address in a To/Cc/Bcc data header and it slapping my hostname on it, because that's what the config told it to do - when as long as the ENVELOPE receiver and sender is FQDN, I see no valid reason to play with the existing data header fields. I think setting append_at_myorigin=no will fix this undesirable rewriting, but really want to know the best way to see this in logging to be sure 1) I have a good handle on the original problem, and 2) how to monitor that I have fixed properly without collateral damage. :-) - Tony >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Len Conrad >Sent: Wednesday, February 04, 2004 8:20 PM >To: [EMAIL PROTECTED] >Subject: [IMGate] Re: append_at_myorigin > > > >>How would you test for that? > >to block forging your MX in helo_hostnames.regexp: > >/myMX\.mydomain\.com$/ REJECT > >Len > > > >
