Bowie Bailey writes:
I had an email come through to one of my users. The To: header had apparently been malformed and Courier had rewritten it. My question is: why? The original header looked like this:To: John S. Smith, II <jsm...@example.com> Courier rewrote the header like this: To: j...@example.com, s.sm...@example.com, II <jsm...@example.com> I understand the reason it is interpreted that way due to the lack of quotes. What I don't understand is why Courier was looking at that header in the first place. The RCPT TO in the envelope should have (and did) determine the recipients. Why does Courier care about the To: header?
Somewhere along the line you probably have the message fed back into Courier via a script. Either forwarded back into Courier by invoking $SENDMAIL directly, or via cc/to in a maildrop filter.
Courier fixes up headers of locally-originated mail. So, if you type the recipient as "postmaster", in mutt, or some other simple mail client, it gets fully qualified, and structured to looked like a valid recipient address.
pgpDbm1FtbV6x.pgp
Description: PGP signature
------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
