[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: retreive_field does not strip \r from the headers

From: Michail Vidiassov
Subject: Re: retreive_field does not strip \r from the headers
Date: Wed, 29 Oct 2003 09:21:24 +0300 (MSK)

Dear Dan,
On Tue, 28 Oct 2003, Dan Nelson wrote:

> > But why not to add a trivial workaround - it the last character of
> > a field is \r - strip it?
> I will probably have to do that.  But what if the author put a trailing
> \r in his subject for some reason?  I'm fixing your problem but
> creating another, less frequent problem.  I don't like solutions like
> that :)

The author is a RFC violator!
Trailing \r is not allowed!
spamass_milter should generate an auto_reply to such message,
with several megabytes of excellent swap attached, or (better)
publish the e-mail of the sender on a web-page, known to be visited
by e-mail address harvesters ;)

RFC 2822:
2.2. Header Fields

   Header fields are lines composed of a field name, followed by a colon
   (":"), followed by a field body, and terminated by CRLF.  A field
   name MUST be composed of printable US-ASCII characters (i.e.,
   characters that have values between 33 and 126, inclusive), except
   colon.  A field body may be composed of any US-ASCII characters,
   except for CR and LF.  However, a field body may contain CRLF when
   used in header "folding" and  "unfolding" as described in section
   2.2.3.  All field bodies MUST conform to the syntax described in
   sections 3 and 4 of this standard.

Am I correct in readin it? Or there is some other MIME RFC, that
allows CR in the filed body?
             Sincerely, Michail

reply via email to

[Prev in Thread] Current Thread [Next in Thread]