Re: header-munging

"D. J. Bernstein" <djb@koobera.math.uic.edu> Wed, 25 September 1996 01:51 UTC

Received: from cnri by ietf.org id aa05665; 24 Sep 96 21:51 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa27302; 24 Sep 96 21:51 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 VAA05271; Tue, 24 Sep 1996 21:06:31 -0400 (EDT)
Received: from koobera.math.uic.edu (KOOBERA.MATH.UIC.EDU [128.248.178.247]) by list.cren.net (8.7.6/8.6.12) with SMTP id VAA05255 for <ietf-smtp@list.cren.net>; Tue, 24 Sep 1996 21:06:26 -0400 (EDT)
Received: (qmail 3124 invoked by uid 666); 25 Sep 1996 01:11:13 -0000
Message-Id: <19960925011113.3123.qmail@koobera.math.uic.edu>
Date: Wed, 25 Sep 1996 01:11:13 -0000
Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
From: "D. J. Bernstein" <djb@koobera.math.uic.edu>
To: ietf-smtp@list.cren.net
Subject: Re: header-munging
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

> Given the
> growing popularity of disconnected clients,

It's worth noting that many disconnected clients (1) let the user decide
when to connect to the ISP and (2) give the user an easy way to delete
messages before #1.

In this situation, the moment of sending is #1. Before the user tells
the client to connect, he hasn't authorized mailing.

I don't know whether these clients are more popular than the other type.

> But at present we have frequently occuring operational problems with
> Internet mail that are caused by a misapplication of this very
> technique. 

Then it should be easy for you to show us some real examples.

When you say ``this type of problem: joe at foo.com ---> joe@zot.net,''
I don't see what the problem is. The client specifically told Joe to
fill in his username at the ISP, so joe@zot.net will work just fine.

Similarly, I don't see why ``joe@foo ---> joe@foo.zot.net'' is a
problem. That looks like a sensible default. What are you complaining
about?

``mrc@panda.com ---> mrc@panda.com.utk.edu'' is an example of why qmail
uses syntactic rules rather than DNS for qualification.

> And if there's a significant chance that the SMTP server is providing
> the *wrong* domain, it's botching the message.  

No. ``Wrong'' doesn't even make sense; do you expect the computer to
read the user's mind? The computer is providing a _default_. If the user
doesn't want that default, he can override it.

> If we really want users to be happy, we can fix up their envelope
> return addresses to be unreplyable.  That way, they will never be
> annoyed by nondelivery reports!

Perhaps you should stop using such an annoying report format.

---Dan