From: Brian May <bmay@csse.monash.edu.au>
Subject: Gnus cannot parse message-id?
Date: 14 Feb 2000 16:14:24 +1100 [thread overview]
Message-ID: <x3r900ol61b.fsf@lyell.csse.monash.edu.au> (raw)
I noticed the message with the following header:
Return-Path: <jmay@rlmsystems.com.au>
X-Gnus-Mail-Source: maildir:~/Maildir/new
Message-ID: <x3ritzsl70k.fsf@totally-fudged-out-message-id>
Delivered-To: bmay@lyell.csse.monash.edu.au
[ I assume this has been added by Gnus... ]
[ received: lines truncated]
[ other headers truncated ]
Message-id:
<153147E594F3D1119B650000F879DDB8015714DA@unclasses01.rlmsystems.com.au>
[ etc ]
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?)
My MTA is postfix, but I doubt this postfix did this.
--
Brian May <bmay@csse.monash.edu.au>
next reply other threads:[~2000-02-14 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 5:14 Brian May [this message]
2000-04-20 21:22 ` 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=x3r900ol61b.fsf@lyell.csse.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).