Xref: utzoo comp.mail.uucp:2646 comp.mail.misc:1547
Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!mailrus!b-tech!zeeff
From: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Newsgroups: comp.mail.uucp,comp.mail.misc
Subject: Re: smail 3.x
Message-ID: <5068@b-tech.ann-arbor.mi.us>
Date: 17 Jan 89 15:01:18 GMT
References: <392@mjbtn.MFEE.TN.US> <6616@killer.DALLAS.TX.US> <430@zinn.MV.COM> <7095@xanth.cs.odu.edu> <437@zinn.MV.COM>
Reply-To: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Organization: Branch Technology Ann Arbor, MI
Lines: 25

Last time I checked, smail 3.x couldn't do the following:

1) Send copies of all mail this site bounces to a specified user.  Very
important for catching problems.

2) Rewrite addresses in a header very well (or very flexibly) when changing
from uucp format to domain format.  xxx!foo.com!user was rewritten to
xxx!foo.com!user@thissite.domain instead of user@foo.com.

3) Support rerouting if the specified route failed.  If you mail to 
xxx!yyy!zzz and xxx is unavailable (or misspelled), the mail is bounced.
It's my experience that it creates fewer problems to reroute it to
yyy!zzz (yes, I know the arguments here).

4) Convert outgoing addresses to pure uucp form for dumb uucp only sites.
(some of my neighbors don't understand user@domain).

 In general, I felt that smail 3.x had a bit of an attitude about how 
things should be done and wasn't going to give you the flexibility to 
do it differently.  


-- 
  Jon Zeeff			zeeff@b-tech.ann-arbor.mi.us
  Ann Arbor, MI			umix!b-tech!zeeff