From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: missing message-id
Date: Sat, 03 Jan 2004 21:19:31 -0500 [thread overview]
Message-ID: <4nwu88o3po.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <m3isju3rdo.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 02 Jan 2004 23:41:39 +0100")
On Fri, 02 Jan 2004, larsi@gnus.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> I've seen some spam recently that was missing a message-id header.
>> I fixed the registry to ignore that on spool-actions, and
>> nnmail-insert-cache also had trouble with nil message-ids, but I
>> was wondering if maybe Gnus can add a message-id header to new mail
>> without that header?
>
> Hm... I really thought that all the mail backends adds a Message-ID
> if it doesn't exist. (Gnus gets very unhappy when dealing with
> messages that don't have Message-IDs.)
This was happening during spooling of incoming mail with nnml or
nnimap - the header was added appropriately later. It's been a while,
sorry I can't be more helpful. I can try to reproduce if it's of
interest to anyone.
Ted
prev parent reply other threads:[~2004-01-04 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 19:49 Ted Zlatanov
2004-01-02 22:41 ` Lars Magne Ingebrigtsen
2004-01-04 2:19 ` Ted Zlatanov [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=4nwu88o3po.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.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).