From: Simon Josefsson <jas@extundo.com>
Subject: Re: Dumplicated 'To' fields
Date: Mon, 02 Jun 2003 22:38:51 +0200 [thread overview]
Message-ID: <iluznl06wpw.fsf@latte.josefsson.org> (raw)
In-Reply-To: <plop87wug5asra.fsf@gnu-rox.org> (Xavier Maillard's message of "Mon, 02 Jun 2003 08:38:33 +0200")
Xavier Maillard <zedek@gnu-rox.org> writes:
> Hi,
>
> I've recently received what I have seen as a weird mail. In fact the
> headers contained two 'To' fields in it. As I am curious on the purpose
> of such a method, I've tried by myself using Gnus and it worked.
It is valid, so it should work.
> Now I am asking if this is really authorized by any RFC and if we
> shouldn't disable such a feature in case it is not.
Gnus didn't generate the situation, did it? So if the user typed the
headers manually, I think it is better to do what she said. See RFC
(2)822.
next prev parent reply other threads:[~2003-06-02 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 6:38 Xavier Maillard
2003-06-02 20:38 ` Simon Josefsson [this message]
2003-06-02 20:56 ` Jesper Harder
2003-06-02 21:23 ` Simon Josefsson
2003-06-02 22:38 ` Jesper Harder
2003-06-02 22:55 ` Simon Josefsson
2003-06-03 3:03 ` Xavier Maillard
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=iluznl06wpw.fsf@latte.josefsson.org \
--to=jas@extundo.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).