0000174: MPro wraps long reference headers after the colon in contravention of RFC 5536 (USEFOR), section 2.2

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000174

[Gemini] misc

major

always

21 Jan 10 20:11

17 Jun 10 20:57

Reporter

freder

View Status

public

Assigned To

mark

Priority

high

Resolution

fixed

Status

closed

Summary

0000174: MPro wraps long reference headers after the colon in contravention of RFC 5536 (USEFOR), section 2.2

Description

As in response from News.individual. Net:

So, we've had a closer look at it, and have come to the conclusion that
your newsreader (Messenger Pro, presumably) is violating usenet
standards. This is what your header lines look like:

| Message-ID: <mpro.kvu810000010p01q1@ypical.nospam.invalid>
| References:
| <1jbwray.1w0eduh1c287fbN%real-not-anti-spam-address@apple-juice.co.uk>
| Organization: @ypical ink

That is, the Message-ID of the article you refer to is wrapped to the
next line such that the first line of the References: header doesn't
actually contain anything. This I believe is not according to the
standard:

RFC 5536 (USEFOR), section 2.2 second bullet point:
| Every line of a header field body (including the first and any
| that are subsequently folded) MUST contain at least one non-
| whitespace character.
http://tools.ietf.org/html/rfc5536#section-2.2 [^]

Likewise, RFC 5322 / 2822 (Internet Message Format), section 3.2.2,
third paragraph:
| However, where CFWS occurs in this specification, it MUST NOT
| be inserted in such a way that any line of a folded header field is
| made up entirely of WSP characters and nothing else.
http://tools.ietf.org/html/rfc5322#section-3.2.2 [^]

I think you should take this up with the creator of your newsreading
software, as this is a bug that's probably hard to spot for a user but
may have serious consequences for any message (including email) produced
by Messenger Plus...

Now, while our server has correctly spottet a flaw, this doesn't help
you as a user, and instead of implementing a rejection of such messages
with a proper error message, we decided to have our server automatically
correct the problem and take away the line break. That is, you should
now be able to reply to articles without starting a new thread
unintentionally - if not, or if you notice other unusual behaviour,
please don't hesitate to drop us a line. Also, should you find that your
newsreader has been fixed, we'd be interested to know so we can
phase-out the workaround.

Additional Information

Issue History
Date Modified	Username	Field	Change
21 Jan 10 20:11	freder	New Issue
23 Jan 10 12:32	mark	Status	new => confirmed
23 Jan 10 12:33	mark	Priority	normal => high
25 Jan 10 13:08	mark	Note Added: 0000156
25 Jan 10 13:08	mark	Status	confirmed => resolved
25 Jan 10 13:08	mark	Resolution	open => fixed
25 Jan 10 13:08	mark	Assigned To	=> mark
17 Jun 10 20:57	mark	Status	resolved => closed

Notes
(0000156) mark (administrator) 25 Jan 10 13:08	Fixed in 2.61.7

Relationships