From: Simon Josefsson <jas@extundo.com>
Subject: Re: Dumplicated 'To' fields
Date: Mon, 02 Jun 2003 23:23:16 +0200 [thread overview]
Message-ID: <ilur86ckwcb.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3el2ci4ge.fsf@defun.localdomain> (Jesper Harder's message of "Mon, 02 Jun 2003 22:56:17 +0200")
Jesper Harder <harder@myrealbox.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Xavier Maillard <zedek@gnu-rox.org> writes:
>>
>>> 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.
>
> Nope, multiple To fields are not allowed, cf. the table in RFC 2822,
> Section 3.6.
RFC 2822 is just a PS, so 822 behavior is still valid, I believe. See
RFC 2822 4.5 for the obs-to field definition, which is identical to
the to field definition, but can occur several times.
next prev parent reply other threads:[~2003-06-02 21:23 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
2003-06-02 20:56 ` Jesper Harder
2003-06-02 21:23 ` Simon Josefsson [this message]
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=ilur86ckwcb.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).