Subject: Message-Id

From: Nils Holland <[email-masked]>
Date: Mon, 5 Nov 2001 16:46:01 +0100 (CET)

Hallo!

This question is not really about a problem, but about something I noticed
recntly and now I'm curious why it is happening. Here is the issue:

I remember that in the past, when I sent a message with Pine, it created a
Message-Id header field of the form "Pine.BSF.xxxxxxxxx" (assuming that it
is running on FreeBSD, which is true in my case). However, if you have a
look at the headers of this message, which has been written using Pine on
FreeBSD, you will see a standard sendmail Message-Id of the form
"<date/time>[email-masked]".

Now, the question is this:

Does Pine no longer create its own Message-IDs, or is my sendmail actually
overwriting Pine's Message-ID? Another thing I could imagine is that Pine
can be configured not to create its own Message-IDs, though I don't
remember having changed anything like that in the options.

Any information on this issue regarding Pine's Message-ID generation would
be welcome.

Greetings
Nils

Nils Holland
Ti Systems - FreeBSD in Tiddische, Germany
http://www.tisys.org * [email-masked]

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Stephen Casner <[email-masked]>
Date: Tue, 6 Nov 2001 22:17:24 -0800 (PST)

> remember having changed anything like that in the options.

The FreeBSD port of Pine includes patches that change the way the
Message-ID string is constructed.  I don't know the motivation for
this patch.
							-- Steve