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

bill@lynxhub.ho.att.com Thu, 26 September 1996 16:37 UTC

Received: from cnri by ietf.org id aa11620; 26 Sep 96 12:37 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa16870; 26 Sep 96 12:37 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 LAA12038; Thu, 26 Sep 1996 11:47:26 -0400 (EDT)
Received: from kcgw1.att.com (kcgw1.att.com [192.128.133.1]) by list.cren.net (8.7.6/8.6.12) with SMTP id LAA11984 for <ietf-smtp@list.cren.net>; Thu, 26 Sep 1996 11:45:45 -0400 (EDT)
Received: from attrh1.attrh.att.com by kcig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id KAA23059; Thu, 26 Sep 1996 10:42:14 -0500
Received: from lynxhub.ho.att.com by attrh1.attrh.att.com (8.7.3/EMS-1.1 SunOS) id LAA06972 for ; Thu, 26 Sep 1996 11:45:04 -0400 (EDT)
Received: by lynxhub.ho.att.com (5.x/SMI-SVR4) id AA14121; Thu, 26 Sep 1996 11:44:05 -0400
Message-Id: <BILL.96Sep26114451@pegasus4.ATT.COM>
Date: Thu, 26 Sep 1996 11:44:05 -0400
Reply-To: WJCarpenter <bill@attmail.com>
Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
From: bill@lynxhub.ho.att.com
To: tjm24297@rpc1220.daytonoh.ncr.com
Cc: ietf-smtp@list.cren.net
Subject: RE: Multiple "To:" and "Cc:" header lines in SMTP messages
In-Reply-To: Tom Moore's note of 08:17:42, 26 September 1996
References: <3.0b24.32.19960926081741.0051af38@rpc1220.daytonoh.ncr.com>
Content-Type: text
X-Mailer: emacs 18.58.1 (via feedmail 3-beta-4 I) WJC
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

tjm> I recently posted a similar inquiry to news and got a few
tjm> responses.  From these it would seem that the only official
tjm> statement is that provided by RFC 822.  Based on that, neither
tjm> Microsoft nor Qualcomm are doing anything wrong but together
tjm> their actions result in a problem.

Although RFC-822 discourages multiple occurences of header fields that
aren't explicitly allowed, in practice there should be little
ambiguity in what to do.  Whereas if there were multiple DATE: fields,
you wouldn't know what to do with them, it's pretty obvious what to do
with multiple TO: fields.

If someone clarified things and specifically ruled out multiple TO:,
CC:, etc, fields, I sure wouldn't get too lathered up trying to get
everyone to be compliant.  If Qualcomm's mailer behaves as you
described when replying to some messages, I'd be more inclined to
blame the Qualcomm software than whatever produced the original email
with multiple TO: fields.
-- 
  bill@attmail.com                    LZ 1C-320
  bill@att.com      (Voice/Fax) +1.908.576.2932
  AT&T Labs       /       AT&T WorldNet Service