🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.mail.misc
Article #1247

Re: is uunet breaking your headers?

#1247
From: David A. Fox
Date: Fri, 25 May 1990 05:27
56 lines
2819 bytes
In article <1258@chinacat.Unicom.COM> chip@chinacat.Unicom.COM (Chip Rosenthal) writes:
>In an attempt to cater to broken mailers, uunet is munging From: lines.
>Even in the case of a legal and valid FQDN it is converting them to bang
>addresses.  I think this is evil and rude.  Am I alone in this?
>

Nope. And neither is uunet -- My forwarder (uxc.cso.uiuc.edu) also does 
this. They didn't originally (i.e., years ago), but they started sometime 
in the past couple years. It seems to be the "standard" technique for 
MX forwarders, as far as I can tell. 

In article <KARL.90May23204613@giza.cis.ohio-state.edu> karl_kleinpaste@cis.ohio-state.edu writes:
>peter@ficc.ferranti.com writes:
>   (I was expecting to get user@ficc.ferranti.com, and didn't have any check
>   in there for ficc.ferranti.com!user)
>
>If you use sendmail, in S3 do:
>R$*.$*!$*		$3@$1.$2		invert to @-format
>but only after verifying that there are no @'s in the address already.
>(That is, my use of the above rule is as the last stage of my Domain
>Absolutist Rabid Rerouter ruleset trio.)
>

I suppose. I thought that S3 wasn't quite the place to put it; In fact,
I was afraid to put it into S1 as well, since that would affect mail
"just passing through" my site. Furthermore, I suspect that the above
rule matches more addresses than I would care to see attacked anyway -
Wouldn't this turn "some.place!some.other.place!user" into
"user@some.place.some!other.place"?  Or do I misunderstand the pattern
matching rules? 

I've recently seen some of these misformed addresses (user@site!site), 
BTW - I won't say where from... :-) 

I thought it prudent to apply this "mx-hack" rewriting only under the 
following conditions:

1. When the mail is destined for a host *in* my domain. 
2. When the return address looks (exactly) like: 

	"mx-servant!some.domain.thing!user"

I wound up putting my fix into my mailer specific sender rewriting 
rules for my local (intra-domain) mailers. 

Was this too paranoid, or what? 

-- 
--
David  A. Fox					Quadratron Systems Inc.	
Inet: david@quad.com, Postmaster@quad.com
UUCP: david@quad1.uucp 
      uunet!psivax!quad1!david

"Man, woman, child... All is up against the wall - of science." 
Technical Details
Message-ID: <8955@gouda.quad.com>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!srhqla!quad1!david
References: <1258@chinacat.Unicom.COM> <QCN3ISG@xds13.ferranti.com> <KARL.90May23204613@giza.cis.ohio-state.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!srhqla!quad1!david
From: david@quad1.quad.com (David A. Fox)
Newsgroups: comp.mail.misc
Subject: Re: is uunet breaking your headers?
Summary: Careful with that ax, eugene.
Message-ID: <8955@gouda.quad.com>
Date: 25 May 90 05:27:59 GMT
References: <1258@chinacat.Unicom.COM> <QCN3ISG@xds13.ferranti.com> <KARL.90May23204613@giza.cis.ohio-state.edu>
Organization: Lost Electricity Reclamation Agency, City of the Future
Lines: 56