From: Tatsuya Ichikawa <ichikawa@hv.epson.co.jp>
Subject: Re: Invalid message-id header when unplugged.
Date: 16 Sep 1998 17:02:39 +0900 [thread overview]
Message-ID: <u90jk4h9c.fsf@hv08.hv.epson.co.jp> (raw)
In-Reply-To: <graham7lz4ikcc.fsf@barnowl.demon.co.uk> (Graham Murray's message of 16 Sep 1998 07:32:19 +0000)
>>>>> In <graham7lz4ikcc.fsf@barnowl.demon.co.uk>
>>>>> Graham Murray <graham@barnowl.demon.co.uk> wrote:
Graham> That looks right to me. I have tested (using gnus 5.6.43)
Graham> sending a message from gnus when unplugged and the message-id
Graham> is *exactly* the same format as when I use gnus in non-agent
Graham> mode.
You might have tested in message-requrired-news-headers's value like
following.
message-required-news-headers's value is
(From Newsgroups Subject Date Message-ID
(optional . Organization)
Lines
(optional . User-Agent))
But I have tested in message-required-news-headers's value like
following.
message-required-news-headers's value is
(From Newsgroups Subject Date
(optional . Organization)
Lines
(optional . User-Agent))
Message-ID header in news message must be unique all around the
world.
So , unplugged-gnus must not add message-id header.
ISP's news server add it like this environment.
Graham> So, Lars, please may I request that you do *not* apply this
Graham> patch and leave the message-id generation as it is.
So this patch may need , I think.
Thanks.
--
Tatsuya Ichikawa <ichikawa@hv.epson.co.jp>
# PGP Public Key : See X-Info header in this message.
next prev parent reply other threads:[~1998-09-16 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-16 4:20 Tatsuya Ichikawa
1998-09-16 7:32 ` Graham Murray
1998-09-16 8:02 ` Tatsuya Ichikawa [this message]
1998-09-16 9:45 ` 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=u90jk4h9c.fsf@hv08.hv.epson.co.jp \
--to=ichikawa@hv.epson.co.jp \
/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).