severity 531052 wishlist thanks Hi Ian,
On Fri, 29 May 2009 06:45:21 -0700 Ian Bruce <ian_br...@fastmail.net> wrote: > Package: claws-mail > Version: 3.7.1-2 > Severity: important > > > Claws-Mail generates Message-ID headers of the form > <time.num...@hostname> ; for example, <20090529055315.7f6ad...@foobar> . > > This does not conform to RFC-2822, which requires that the string > after the "@" character be a fully-qualified domain name, in order > to make the Message-ID globally unique. That's simply not true: it requires the Message-ID to be globally unique and provides an example of algorithm to generate it, and *recommends* the domain name to be in the right side to help it to be unique. Mandatory quote of RFC 2822: ,----- | 3.6.4. Identification fields [...] | The message identifier (msg-id) itself MUST be a globally unique | identifier for a message. The generator of the message identifier | MUST guarantee that the msg-id is unique. There are several | algorithms that can be used to accomplish this. [...] | Though other algorithms will work, it is RECOMMENDED that the right hand | side contain some domain identifier (either of the host itself or | otherwise) such that the generator of the message identifier can | guarantee the uniqueness of the left hand side within the scope of that | domain. `----- > Some mailing list software will refuse to process messages because of this > problem. That's interesting because they are wrongly interpreting then the RFC in the way you exposed here while the RFC clearly states that there's several algorithms to get a globally unique identifier and they would also work. IOW: these list software are buggy regarding RFC 2822. Do you have a list of them? > A better choice would be for the Message-ID to be of the form > <time.number.use...@fqdn> , where "use...@fqdn" is the sender's email > address; for example, <20090309043710.b6bc3b96.ian_br...@fastmail.net> . > This is what Sylpheed already does. This doesn't guarantee the identifier is globally unique and is just slightly better than current one. Notice also the FQDN can also be poorly configured in lots of machines which simply return the hostname. The main source of uniqueness of the identifier goes to the number part which I think is correct as it is. > Please import the relevant code section from Sylpheed, and also send > this patch upstream. Thanks. It can be somewhat better to use the FQDN, hence I will probably prepare a patch, but that won't solve the problem on machines whose FQDN is the hostname. regards, -- Ricardo Mones http://people.debian.org/~mones «Soap and education are not as sudden as a massacre, but they are more deadly in the long run. -- Mark Twain»
signature.asc
Description: PGP signature
