-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Thank you all for the input and the rfc url. To my surprise the central IT dept. is going to make the change to allow the envelope from to be empty! I'm pretty sure it was the rfc url I gave them to help my cause. So I'm reverting the code back to the original state.
Charles Marcus wrote:
On 8/12/2008, CJ Keist (cj.keist@colostate.edu) wrote:
I understand what you are saying in trying to keep a vicious cycle of auto-replies responding to each other. But in our environment I don't have any choice as our central virus/spam email gateway will can any message without a valid from address in the headers. I will forward this on to our central IT guys that maintain the email gateway, but I don't hold much hope that they will listen ;) .
My advice? Throw away the gateway and find one that works correctly.
Doing this results in your users NOT getting 99.99% of valid/legitimate DSN notifications (since they all use the NULL sender, as prescribed by the RFCs).
Blocking all messages with a NULL sender is not only violating the RFCs, and will possibly result in your getting on certain blacklists, like dsn.rfc-ignorant.org, it is lazy and dumb.
But, to each his own...
C. J. Keist Email: cj.keist@colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301
All I want is a chance to prove 'Money can't buy happiness' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIohcFA29OFr7C6jcRAhotAKDH0tZz/zVL/z7VLMHhKAG+mTvTVgCg3XwR n8jdXJOrZk0biQt04cUUkWI= =Bhdt -----END PGP SIGNATURE-----