From: Steven L Baur <steve@miranova.com>
Subject: Re: Message-Ids
Date: 01 May 1996 12:53:18 -0700 [thread overview]
Message-ID: <m2n33s6uhd.fsf@deanna.miranova.com> (raw)
In-Reply-To: Scott Hofmann's message of 01 May 1996 10:07:33 -0700
>>>>> "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.
next prev parent reply other threads:[~1996-05-01 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-01 17:07 Message-Ids Scott Hofmann
1996-05-01 19:53 ` Steven L Baur [this message]
1996-05-02 14:20 ` Message-Ids Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2n33s6uhd.fsf@deanna.miranova.com \
--to=steve@miranova.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).