[Mimedefang] X-Auto-Response-Suppress header

George Roberts groberts at purity.net
Wed May 16 18:47:58 EDT 2012


If one looks carefully, RFC 5321 3.7.2 states:

"As another consequence  of trace header fields arising in non-SMTP environments, receiving  systems MUST NOT reject mail based on the format of a trace header field and SHOULD be extremely robust in the light of unexpected information or formats in those header fields."

I'm not going to quote the whole RFC to you, but from what I've read it's pretty clear that the Received: line is for debugging purposes ("...  the most important use of Received: lines is for debugging mail faults ...", Section 3.7.2). I'm hard-pressed to find any justification for blocking of mail generated or handled by Exchange. In fact, I think it's pretty clear the RFC states you MUST NOT block them.

---
Regards,

George

-----Original Message-----
From: mimedefang-bounces at lists.roaringpenguin.com [mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of kd6lvw at yahoo.com
Sent: Wednesday, May 16, 2012 5:23 PM
To: mimedefang at lists.roaringpenguin.com
Subject: Re: [Mimedefang] X-Auto-Response-Suppress header

--- On Wed, 5/16/12, David F. Skoll <dfs at roaringpenguin.com> wrote:
> After gnashing my teeth at Microsoft because its dumb software ignores
> Precedence: and List-*: headers and cheerfully sends out-of-office 
> replies to list owners, I discovered this:
> 
> http://msdn.microsoft.com/en-us/library/ee219609%28v=exchg.80%29.aspx
> 
> I've set up a MIMEDefang filter to add X-Auto-Response-Suppress: OOF 
> to all list traffic.  Just passing it along as a tip to other list 
> owners.

I take a stronger approach:  Since M$ Exchange is incapable of generating proper "Received:" headers, I reject all mail which has transited such a system using that software.

If one looks carefully, their chosen syntax violates even the old RFC 821/822 standards (STD 10), let alone the 5321/5322 modern versions.
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang



More information about the MIMEDefang mailing list