Re: header-munging

RANDY@mpa15ab.mv.unisys.com Tue, 24 September 1996 22:48 UTC

Received: from cnri by ietf.org id aa03344; 24 Sep 96 18:48 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa13428; 24 Sep 96 18:47 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 SAA02196; Tue, 24 Sep 1996 18:10:41 -0400 (EDT)
Received: from bbmail1.unisys.com (192-63-2005.unisys.com [192.63.200.5]) by list.cren.net (8.7.6/8.6.12) with ESMTP id SAA02176 for <ietf-smtp@LIST.CREN.NET>; Tue, 24 Sep 1996 18:10:31 -0400 (EDT)
Received: from mvdns1.mv.unisys.com (mvdns1.mv.unisys.com [192.59.253.100]) by bbmail1.unisys.com (8.7.3/8.6.12) with SMTP id WAA23425; Tue, 24 Sep 1996 22:09:29 GMT
Received: from MPA15AB.MV.UNISYS.COM by mvdns1.mv.unisys.com (4.1/SMI-4.1-1.8) id AA05541; Tue, 24 Sep 96 22:10:36 GMT
Message-Id: <EL1R0845D8123F@MPA15AB>
Date: Tue, 24 Sep 1996 15:10:00 -0000
Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
From: RANDY@mpa15ab.mv.unisys.com
To: Ned.Freed%Innosoft.com@mv.unisys.com, ietf-smtp%LIST.CREN.NET@mv.unisys.com, moore%CS.UTK.EDU@mv.unisys.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: Re: header-munging
In-Reply-To: Your message of "24 Sep 1996 17:28:52 -0400"
References: <199609242128.RAA01948@ig.cs.utk.edu>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

On 24 Sep 1996 17:28:52 -0400, Keith Moore <moore@cs.utk.edu> wrote:

> It's not possible in general (or even widely feasible) to determine
> the sender's user name or domain given the IP address from which a
> message was submitted.  Many environments do not do static IP address
> assignment; others share PCs or workstations between several people.
> And given the scarcity of IPv4 address space, it's not a solution we
> want to encourage.

But many ISPs can determine user identity from the dynamic IP address,
since they authenticated that user and assigned that IP address.


> In fact, your messages provide a convenient example as to why having
> submission agents do message fixup should be strongly discouraged.
>
> ] To: <ietf-smtp%LIST.CREN.NET@MV.Unisys.COM>,
> ] <moore%CS.UTK.EDU@MV.Unisys.COM>,
> ]         <Ned.Freed%Innosoft.com@MV.Unisys.COM>
>
> By attempting to compensate for your UA or gateway's incorrect
> configuration (i.e. lack of knowledge of your return address), your
> SMTP server has damaged several perfectly valid addresses.

Actually, I manually percent-hacked the addresses, because the firewall
prevents the SMTP server I am using (the one my user agent talks to)
from opening an outbound SMTP port.  I have to percent-hack to force it
to route the messages such that they arrive at a server which is
authorized to open an outbound SMTP connection.  (The server does have
an option that forces such routing, but there is a bug in it, so I
resort to manual percent-hacking until the bug is fixed *sigh*).

This is actually a case where the server would correct my return address
(from "randy@mpa15ab" to "randy@mpa15ab.mv.unisys.com") and everything
would be fine, but for the firewall and a different bug in the server
routing override options.



--
|Randall Gellens             |                    randy@mv.unisys.com|
|(714) 380-6350              | fax (714)597-8053 can add ,,,,,,,,6350|
|Opinions are personal;  facts are suspect;   I speak only for myself|