From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Bad Gnus-generated Message-ID:
Date: 02 Apr 1999 15:56:26 +0200 [thread overview]
Message-ID: <m3yakbjfcl.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Jason L Tibbitts III's message of "28 Mar 1999 21:22:57 -0600"
Jason L Tibbitts III <tibbs@math.uh.edu> writes:
> A message just went out which bounced off of some sites because the
> Message-ID: was bad. Here are some headers:
[...]
> Message-Id: <m34sn5oxmh.fsf@serpent.laymusic.>
Hm. I think this probably means that the `system-name' returns
something bogus. I don't think Message could check for that. Well,
it could, but how much should it check?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-04-02 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-29 3:22 Jason L Tibbitts III
1999-04-02 13:56 ` Lars Magne Ingebrigtsen [this message]
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=m3yakbjfcl.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).