From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Problem with Message-ID and agent Unplugged
Date: Thu, 01 May 2003 09:07:15 +0200 [thread overview]
Message-ID: <m3vfwv16xo.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <86znm8f0tv.fsf@totally-fudged-out-message-id> (Thomas Havlovec's message of "Wed, 30 Apr 2003 17:43:08 +0200")
Thomas Havlovec <hatx@gmx.at> writes:
> and the article gets posted with the fudged-MID. Is this a bug, or can
> I somehow tell the agent to leave the article without MID?
All the messages in Gnus has to have Message-IDs. When you post
unplugged, the message is posted to nndraft, which will create a
Message-ID.
So what you want isn't supported by Gnus, and I'd suggest you let
Gnus generate proper Message-IDs for you.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-05-01 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 15:43 Thomas Havlovec
2003-05-01 7:07 ` Lars Magne Ingebrigtsen [this message]
2003-05-01 11:33 ` Reiner Steib
2003-05-01 12:15 ` 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=m3vfwv16xo.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).