Re: [Evolution] Evolution generating invalid message-ids

On Fri, 2002-07-26 at 20:43, Richard Zach wrote:
Just FYI:  Balsa had a similar wasn't accepting
messages for delivery if they have a Message-ID.  In the ensuing
discussion, the possibility of adding a config option "Do not generate
Message-ID" was considered. It wasn't implemented. The thread starts

Jamie Zawinski wrote something for DRUMS on message-id's:
(I know this is an Internet Draft and there's no reason whatsoever to
do anything recommended there--other than that Jamie Zawinski is a
pretty bright guy.)

From what Matt Curtin and he are saying, it's clear that they take
"globally unique" in RFC 822 to mean actually unique, not just unique
for the generating host.  They suggest to use the host/domain part of
the user's address as a fallback if you can't get the FQDN of the host.
They also say that "use of an unqualified hostname for the domain part 
of the Message-ID header would be foolish, and should never be done." 
By extension, I take it, using "localhost" or "localhost.localdomain" 
for the rhs of the message-id would not be advisable.

if it ever uses localhost or localhost.localdomain then the user's
system is broken and there's nothing we can do about it.

we use gethostname() and then pass that into gethostbyname() and use
h->h_name so the hostname we use should be fine.


Jeffrey Stedfast
Evolution Hacker - Ximian, Inc.
fejj ximian com  -

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