🚀 go-pugleaf

I was wondering what the thoughts of developers would be towards allowing a
user (host?) to invoke a routine to rewrite a To: address that has been
automatically generated by elm.

Most of the time that I would be interested in utilizing this involve mail
which was posted to a mailing list.  For example, if a user on BITNET sends me
mail by posting to a list, the return address is likely to be:

user%node.bitnet@<gateway>

where the <gateway> is the one that is appropriate to the site that hosts the
list.  My mail setup would allow me to send the mail to simply:

user@node.bitnet

I realize that this rewriting is not necessarily correct for all sites, and
that is why I think it needs to be customizeable.  The primary motivation for
rewriting is for an efficiency gain.  Note that for many mailing lists, If I
were to reply to a user on my own machine, the return address would still be:

user%wubios.wustl.edu@<gateway>

an obviously inefficient way to send mail to someone on my own system.

Now I suppose that it is a philosophical question about whether this should be
done by the MUA or the MTA.  I would think that the MTA is obligated to send
the mail the way that it is addressed, and thus if optimization is to be
achieved, it is the MUA's responsibility.

I do not know the details of the plans which are designed to differentiate
between a return address which is a user on the current system and one which
is a private (or public, even) alias, but perhaps this functionality could be
incorporated into the revised design for 3.0.

-phil
-- 
     J. Philip Miller, Professor, Division of Biostatistics, Box 8067
	 Washington University Medical School, St. Louis MO 63110
	  phil@wubios.WUstl.edu - (314) 362-3617 [362-2694(FAX)]