Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uwm.edu!linac!Firewall!genesis!kdenning From: kdenning@genesis.Naitc.Com (Karl Denninger) Newsgroups: comp.mail.uucp Subject: Re: address re-writing in smail 3.1.18 Summary: Smail3.1.18 will do this automatically Message-ID: <1991Jun2.182421.11107@Firewall.Nielsen.Com> Date: 2 Jun 91 18:24:21 GMT References: <1991Jun2.165657.16810@unixland.natick.ma.us> Sender: news@Firewall.Nielsen.Com (Usenet News) Organization: AC Nielsen Co., Bannockburn IL Lines: 57 Nntp-Posting-Host: genesis.naitc.com In article <1991Jun2.165657.16810@unixland.natick.ma.us> bill@unixland.natick.ma.us (Bill Heiser) writes: >I have been informed by my mail forwarding site that my smail isn't >writing address headers correctly. For example, if I send something >to user@site, it goes out like that ... and that is an incomplete >address (it should be user@site.domain). > >Since I am a UUCP site (with a FQDN), I guess I should rewrite user@host >addresses as user@host.uucp, bouncing incomplete addresses back to the >sender. An alternative would be to re-write the incomplete addresses as >host!user. NO! You should not rewrite the To: line. The internal addressing information (ie: the SMTP "RCPT TO: " info or the uux'd command for uucp sites) is another matter entirely, and is handled properly by Smail3. The "From:" line should always have a FQDN in it if you have one. To do so in smail3, set "hostnames" in the config file such that it has two entries -- the first of which is your FQDN, the second is your UUCP name. This will get you a "local" match on both address forms, yet send the mail out with the proper FQDN in the From: line. For example, on my home machine (which is a UUCP connected site with a FQDN) I have: hostnames=ddsw1.mcs.com:ddsw1 in /usr/lib/smail/config This forces all outbound mail that doesn't have a "From:" line specified, or has only a username there (ie: a local form) to have the first entry (called the "$primary_name" in smail3) inserted appropriately. >How is this done in smail 3.1? What are those of you running smail 3.1 >on uucp sites doing to make sure you transmit only valid addresses? If the "uucp" flag is on in the transport definition, or you have any "!"s in the address when it gets to the transport level, it will normally be rewritten in the "!" form for the transport ONLY. The To: line will be untouched (as it should be). This is Smail3.21 now... (which is what I have here). I don't think this changed from smail3.18 however. If you send via SMTP or other transport without the "uucp" flag, then the address is not messed with. This is a >good thing<; I personally run a funny "half-baked SMTP" to a number of sites, and it allows the other end to use all their DNS lookup power without having to mangle the address back into Internet form. When in doubt, use the source, Luke ;-) -- Karl Denninger - AC Nielsen, Bannockburn IL (708) 317-3285 kdenning@nis.naitc.com "The most dangerous command on any computer is the carriage return." Disclaimer: The opinions here are solely mine and may or may not reflect those of the company.