Re: My open issues with RFC3028bis
Kjetil Torgrim Homme <kjetilho@ifi.uio.no> Tue, 05 July 2005 13:12 UTC
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j65DCmH6059819; Tue, 5 Jul 2005 06:12:48 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j65DCmcR059818; Tue, 5 Jul 2005 06:12:48 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j65DCk3d059786 for <ietf-mta-filters@imc.org>; Tue, 5 Jul 2005 06:12:47 -0700 (PDT) (envelope-from kjetilho@ifi.uio.no)
Received: from mail-mx3.uio.no ([129.240.10.44]) by pat.uio.no with esmtp (Exim 4.43) id 1DpnEA-0003Vq-NR; Tue, 05 Jul 2005 15:12:42 +0200
Received: from 80.80-202-166.nextgentel.com ([80.202.166.80] helo=chico.njus.no) by mail-mx3.uio.no with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.43) id 1DpnD7-0008UD-7E; Tue, 05 Jul 2005 15:11:37 +0200
Subject: Re: My open issues with RFC3028bis
From: Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
To: Philip Guenther <guenther+mtafilters@sendmail.com>
Cc: ietf-mta-filters@imc.org
In-Reply-To: <200507020058.j620w4SP031225@lab.smi.sendmail.com>
References: <E1Do7RW-0002QU-TU@nostromo.freenet-ag.de> <01LQ31LDKJ0200004T@mauve.mrochek.com> <20050701091231.GC10060@nostromo.freenet-ag.de> <01LQ44NF85CE00004T@mauve.mrochek.com> <200507020058.j620w4SP031225@lab.smi.sendmail.com>
Content-Type: text/plain
Date: Tue, 05 Jul 2005 15:11:30 +0200
Message-Id: <1120569090.4185.56.camel@chico.njus.no>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.1
Content-Transfer-Encoding: 7bit
X-UiO-Spam-info: not spam, SpamAssassin (score=-2.283, required 12, autolearn=disabled, AWL 0.88, FORGED_RCVD_HELO 0.05, RCVD_IN_NJABL_DUL 1.66, RCVD_IN_SORBS_DUL 0.14, UIO_MAIL_IS_INTERNAL -5.00)
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>
On Fri, 2005-07-01 at 17:58 -0700, Philip Guenther wrote: > Works for me. 2.4.2.2 now reads: [...] > > Folding of long header lines (as described in [IMAIL] 2.2.3) is > removed prior to interpretation of the data. The folding syntax (the > CRLF that ends a line plus any leading whitespace at the beginning of > the next line that indicates folding) are interpreted as if they were > a single space. > > <pause> > > Hmmm, that last paragraph actually differs from RFC 2822, section 2.2.3, > which says: > Unfolding is accomplished by simply removing any CRLF > that is immediately followed by WSP. > > I.e., the leading whitespace should *not* be treated as a single space > but rather be left as is. Unless I hear screams, I'm going to remove > the sentence that starts "The folding syntax..." as conflicting. that's fine, but I find it a bit misleading to only refer to [IMAIL], since RFC 2047 changes the folding rule in the presence of two encoded-words: any folding whitespace between them must be removed (see section 6.2 paragraph 3). e.g., Subject: =?utf-8?q?hell?= =?utf-8?q?o?= should be presented as: Subject: hello on the other hand, Subject: =?utf-8?q?hell?= o should be folded into Subject: hell o my suggestion is to add the reference, perhaps like so Long header lines are unfolded (as described in [IMAIL] 2.2.3 and [MIME] part 3 6.2) prior to interpretation of the data. -- Kjetil T.
- My open issues with RFC3028bis Michael Haardt
- Re: My open issues with RFC3028bis Philip Guenther
- Re: My open issues with RFC3028bis Michael Haardt
- Re: My open issues with RFC3028bis Ned Freed
- Re: My open issues with RFC3028bis Philip Guenther
- Re: My open issues with RFC3028bis Michael Haardt
- Re: My open issues with RFC3028bis Michael Haardt
- Re: My open issues with RFC3028bis Ned Freed
- Re: My open issues with RFC3028bis Philip Guenther
- Re: My open issues with RFC3028bis Ned Freed
- NUL handling and security considerations [was: Re… Philip Guenther
- Re: NUL handling and security considerations [was… Ned Freed
- Re: My open issues with RFC3028bis Alexey Melnikov
- Re: My open issues with RFC3028bis Kjetil Torgrim Homme
- Re: My open issues with RFC3028bis Ned Freed
- Re: My open issues with RFC3028bis Kjetil Torgrim Homme
- Re: My open issues with RFC3028bis Mark E. Mallett
- Re: My open issues with RFC3028bis Mark E. Mallett
- Re: My open issues with RFC3028bis Kjetil Torgrim Homme
- Re: My open issues with RFC3028bis Philip Guenther
- Re: My open issues with RFC3028bis Alexey Melnikov
- Re: My open issues with RFC3028bis Ned Freed
- Re: My open issues with RFC3028bis Ned Freed
- Re: My open issues with RFC3028bis Philip Guenther
- Re: NUL handling and security considerations [was… Alexey Melnikov