* Message-Ids
@ 1996-05-01 17:07 Scott Hofmann
1996-05-01 19:53 ` Message-Ids Steven L Baur
1996-05-02 14:20 ` Message-Ids Lars Magne Ingebrigtsen
0 siblings, 2 replies; 3+ messages in thread
From: Scott Hofmann @ 1996-05-01 17:07 UTC (permalink / raw)
How is the Message-Id header built? I've just moved my newsreading from using
XEmacs 19.13/sgnus 0.80 on an HP-UX 10.01 box to XEmacs 19.13/sgnus 0.80 on an
IRIX 5.2 box, and now I'm getting bogus Message-Id headers:
Message-Id: <something>@foo
The problem is the lack of a domain - on the HP it looked like this:
Message-Id: <something>@bar.visix.com
Where does sgnus get the Message-Id from? The info files didn't say. Thanks,
scott
-------------------------------------------------------------------------------
J. Scott Hofmann | "At first [Kate Mulgrew] sounds like Katherine
Visix Software, Inc. | Hepburn playing a Munchkin. Then she begins
scotth@visix.com | sounding more like Jane Curtin as Mama Conehead."
...!uupsi!visix!scotth | -_Washington Post_ review of _Star Trek: Voyager_
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Message-Ids
1996-05-01 17:07 Message-Ids Scott Hofmann
@ 1996-05-01 19:53 ` Steven L Baur
1996-05-02 14:20 ` Message-Ids Lars Magne Ingebrigtsen
1 sibling, 0 replies; 3+ messages in thread
From: Steven L Baur @ 1996-05-01 19:53 UTC (permalink / raw)
>>>>> "Scott" == Scott Hofmann <scotth@visix.com> writes:
Scott> How is the Message-Id header built? I've just moved my
Scott> newsreading from using XEmacs 19.13/sgnus 0.80 on an HP-UX
Scott> 10.01 box to XEmacs 19.13/sgnus 0.80 on an IRIX 5.2 box, and
Scott> now I'm getting bogus Message-Id headers:
Scott> Message-Id: <something>@foo
Scott> The problem is the lack of a domain - on the HP it looked like this:
Scott> Message-Id: <something>@bar.visix.com
Both of these Message-ID:'s are bogus. A proper one looks like:
Message-ID: <m2oho86vck.fsf@deanna.miranova.com>
The angle brackets should always be on the outside.
Scott> Where does sgnus get the Message-Id from? The info files didn't
Scott> say. Thanks,
Message IDs *must* be unique across every mail & netnews message ever
sent in the past, or ever will be sent in the future.
The algorithm used by September Gnus is contained in the functions
message-make-message-id and message-unique-id in message.el.
The part after the @ is generated by the function message-make-fqdm,
which calls the XEmacs builtin function (system-name). This routine
has serious problems (IMHO) in 19.13 (it is not a problem with any
version of Emacs I've tried). I was able to get satisfactory results
only after using a FQDN for the system hostname
(eg. ``deanna.miranova.com'' versus ``deanna'').
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Message-Ids
1996-05-01 17:07 Message-Ids Scott Hofmann
1996-05-01 19:53 ` Message-Ids Steven L Baur
@ 1996-05-02 14:20 ` Lars Magne Ingebrigtsen
1 sibling, 0 replies; 3+ messages in thread
From: Lars Magne Ingebrigtsen @ 1996-05-02 14:20 UTC (permalink / raw)
Scott Hofmann <scotth@visix.com> writes:
> IRIX 5.2 box, and now I'm getting bogus Message-Id headers:
>
> Message-Id: <something>@foo
I thought only Sun boxes had this problem.
Anyways, set `mail-host-address' to be the fully qualified domain name
of your machine, and things should work better.
--
"Yes. The journey through the human heart
would have to wait until some other time."
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1996-05-02 14:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1996-05-01 17:07 Message-Ids Scott Hofmann
1996-05-01 19:53 ` Message-Ids Steven L Baur
1996-05-02 14:20 ` Message-Ids Lars Magne Ingebrigtsen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).