Re: Multiple "To:" and "Cc:" header lines in SMTP messages

Harald.T.Alvestrand@uninett.no Fri, 27 September 1996 09:04 UTC

Received: from cnri by ietf.org id aa03796; 27 Sep 96 5:04 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa25280; 27 Sep 96 5:04 EDT
Received: from localhost (localhost.0.0.127.in-addr.arpa [127.0.0.1]) by list.cren.net (8.7.6/8.6.12) with SMTP id EAA15958; Fri, 27 Sep 1996 04:22:10 -0400 (EDT)
Received: from domen.uninett.no (domen.uninett.no [129.241.131.10]) by list.cren.net (8.7.6/8.6.12) with SMTP id EAA15944 for <ietf-smtp@list.cren.net>; Fri, 27 Sep 1996 04:21:58 -0400 (EDT)
Received: from domen.uninett.no by domen.uninett.no with SMTP (PP) id <14399-0@domen.uninett.no>; Fri, 27 Sep 1996 10:21:40 +0200
Message-Id: <14386.843812494@domen.uninett.no>
Date: Fri, 27 Sep 1996 10:21:34 +0200
Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
From: Harald.T.Alvestrand@uninett.no
To: "O'Brien, Walt" <Walt_OBrien@dg-webo.webo.dg.com>
Cc: 'ieft-smtp' <ietf-smtp@list.cren.net>
Subject: Re: Multiple "To:" and "Cc:" header lines in SMTP messages
In-Reply-To: Your message of "Thu, 26 Sep 1996 05:22:52 EDT." <c=US%a=telemail%p=dg%l=GROUCHO-960926092252Z-413@groucho.webo.dg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: Harald.T.Alvestrand@uninett.no
X-Mailer: exmh version 1.6.7 5/3/96
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

This has been discussed on the DRUMS list, which is the list charged
with clarifying matters  like these.

The more-or-less conclusion was:

- In certain situations (namely where the To: lines would be more than
  8 Kbytes or so in length when unwrapped), certain mailers break,
  whereas they accept multiple To: lines
- Therefore, people will go on breaking things onto multiple To: lines.
- The practice should be frowned upon; having multiple To: lines with
  a single address on each is silly. So it's a SHOULD NOT GENERATE.
- The only recipient semantics that make sense is to treat it as if it
  was a single long To: field. So it's a SHOULD ACCEPT.

Or something like that. Go to the DRUMS archives if you want details.

               Harald A