Re: Email Subaddressing

"Donald E. Eastlake 3rd" <dee@cybercash.com> Fri, 01 August 1997 15:27 UTC

Received: from cnri by ietf.org id aa21597; 1 Aug 97 11:27 EDT
Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid LAA03067; Fri, 1 Aug 1997 11:26:18 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.5/8.7.3) id HAA11884 for ietf-822-bks; Fri, 1 Aug 1997 07:48:48 -0700 (PDT)
Received: from callandor.cybercash.com (callandor.cybercash.com [204.178.186.70]) by mail.proper.com (8.8.5/8.7.3) with SMTP id HAA11875 for <ietf-822@imc.org>; Fri, 1 Aug 1997 07:48:43 -0700 (PDT)
Received: by callandor.cybercash.com; id KAA25954; Fri, 1 Aug 1997 10:41:04 -0400
Received: from cybercash.com(204.149.68.52) by callandor.cybercash.com via smap (3.2) id xma025934; Fri, 1 Aug 97 10:40:48 -0400
Received: by cybercash.com (4.1/SMI-4.1) id AA25771; Fri, 1 Aug 97 10:46:29 EDT
Date: Fri, 01 Aug 1997 10:46:28 -0400
From: "Donald E. Eastlake 3rd" <dee@cybercash.com>
To: ietf-822@imc.org
Subject: Re: Email Subaddressing
In-Reply-To: <19970731083054.3080.qmail@koobera.math.uic.edu>
Message-Id: <Pine.SUN.3.91.970731124659.6252A-100000@cybercash.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf-822@imc.org
Precedence: bulk

Dan,

I'm not sure if the benefits warrant standardization but I don't accept
your arguments by dogmatic assertion:

On 31 Jul 1997, D. J. Bernstein wrote:

> Date: 31 Jul 1997 08:30:54 -0000
> From: D. J. Bernstein <djb@koobera.math.uic.edu>
> 
> > There are two cases where MUAs need to cooperate with subaddresses:
> > 1) MUAs which don't allow from to be edited otherwise.
> 
> This is a purely local configuration problem.

If agents wish to constrain from addresses to fight spoofing or whatever but
allow subaddress editing, they can't do it because there is no uniformity of
subadressing.  If there were a standard, they could.  I believe this would be
a benefit. 

Standarizing things has benefits and costs.  The benefits are not eliminated
by you enormous distaste for the particular standarization or your 
failure to acknowledge the benefits.

> > 2) MUAs which validate local addresses against a white pages or authdb
> > service.
> 
> A service that claims to check mail addresses obviously has to
> understand subaddresses. This is a purely local configuration problem.
> 
> > 1) List server restricts posting to subscribers.
> 
> You have no right to demand that list owners accept your mail.

The closest thing I've seen to a demand is your demand that this not be
standardized.  Most list owners want to accept mail and if subaddressing were
standardized, I believe many list servers would adapt to the standard.  If it
is not standardized, some sort of informal consensus might develop but it
would be much slower. 

> > There are several cases where a final delivery agent needs to cooperate
> > with subaddresses:
> 
> All of those cases are purely local configuration problems.
> 
> I suppose next we're going to see a document explaining how sendmail
> interacts with procmail, and requiring that all MTAs and LDAs work the
> same way.

I don't know where you get this idea that IETF standards are requirements.  I
supose you could say that of the tiny handful that are classified as
"mandatory", but that certainly doens't include *any* of the email standards
most of which are in the "recommended" or "elective" categories of IETF
standards.  See RFC 2200.

> ---Dan
> Set up a new mailing list in a single command. http://pobox.com/~djb/ezmlm.html

Donald
=====================================================================
Donald E. Eastlake 3rd     +1 508-287-4877(tel)     dee@cybercash.com
   318 Acton Street        +1 508-371-7148(fax)     dee@world.std.com
Carlisle, MA 01741 USA     +1 703-620-4200(main office, Reston, VA)
http://www.cybercash.com           http://www.eff.org/blueribbon.html