From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus cannot parse message-id?
Date: 20 Apr 2000 23:22:52 +0200 [thread overview]
Message-ID: <m3zoqoxyab.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <x3r900ol61b.fsf@lyell.csse.monash.edu.au>
Brian May <bmay@csse.monash.edu.au> writes:
> Message-ID: <x3ritzsl70k.fsf@totally-fudged-out-message-id>
> Delivered-To: bmay@lyell.csse.monash.edu.au
[...]
> Message-id:
> <153147E594F3D1119B650000F879DDB8015714DA@unclasses01.rlmsystems.com.au>
[...]
> I believe this is because Gnus got confused with the newline and
> thinks the message-id is blank when it isn't (or perhaps the message
> id is simply too long?)
I've had a peek over the code, and it looks to me like Gnus should
grok the original Message-ID. Do you get this in other messages as
well, or just this one?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2000-04-20 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 5:14 Brian May
2000-04-20 21:22 ` 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=m3zoqoxyab.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).