Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!decwrl!uunet!intercon!news
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.mail.misc
Subject: Re: is uunet breaking your headers?
Message-ID: <2666872B.212F@intercon.com>
Date: 1 Jun 90 15:18:03 GMT
References: <QCN3ISG@xds13.ferranti.com> <KARL.90May23204613@giza.cis.ohio-state.edu> <8955@gouda.quad.com> <13952@ucsd.Edu> <2752.26638923@mccall.com> <May.31.11.25.58.1990.23299@turbo.bio.net>
Sender: usenet@intercon.com (USENET The Magnificent)
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Organization: InterCon Systems Corporation, Herndon, VA
Lines: 29

In article <May.31.11.25.58.1990.23299@turbo.bio.net>, lear@turbo.bio.net
(Eliot) writes:
> It was said that if you
> tell UUNET that you have a smart mailer, they'll do the right thing.
> What more can you ask for?

I'll also come in on UUNET's side on this one (even though it took me a
while to realize that I could tell them I could handle domain-style
addresses).

A lot of uunet's customers are probably running little UNIX boxes with
vanilla UUCP and a stupid mailer.  They way uunet sets up a customer by
default, all they have to do is set their UUCP node name and mail flows.
This means minimal frustration all around, and it's a lot less annoying
than getting some vendor's random version of sendmail (with an even more
random sendmail.cf) working properly.

If you say you want real addresses, though, they seem happy to oblige.
The host 'intercon.com' is an example... It's even using a mild variation
on Karl's sendmail.cf, which is the most sensible one I've ever run across.

The fact that I used to work two cubicles away from him and overheard his
cursing at <expletive deleted>ed mail relays has nothing to do with it :-)...

--
Amanda Walker, InterCon Systems Corporation
--
"Go not to the elves for counsel, for they will say both no and yes."
	--J.R.R. Tolkien, The Lord of the Rings