Path: utzoo!attcan!uunet!husc6!mailrus!ukma!cwjcc!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon S. Allbery)
Newsgroups: comp.mail.uucp
Subject: Re: active rerouting
Message-ID: <12659@ncoast.UUCP>
Date: 6 Oct 88 23:53:32 GMT
References: <4740@b-tech.UUCP> <4747@b-tech.UUCP> <4748@b-tech.UUCP> <6581@chinet.UUCP> <2105@edsews.EDS.COM> <12604@ncoast.UUCP> <290@hal.UUCP>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.mail.uucp
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 27

As quoted from <290@hal.UUCP> by ane@hal.UUCP (Aydin "Bif" Edguer):
+---------------
| Yes.  But the proper way to do this is to send to hal!bar.COM!foo.
| WHENEVER POSSIBLE, use non-ambiguous paths (only "!"'s or "@"'s, not both).
| I promise to correct the problem if it does not attempt delivery to foo@bar.com
| when given the path hal!bar.com!foo. (note: I make no guarantees it will
| actually get there)
+---------------

You will understand that we stopped using this when hal (or was it mandrill?)
had a broken sendmail.cf that converted a path that on ncoast was something
like "hal!baz.bar.com!foo" into something resembling "baz!foo!bar.com@decvax".
(Actually, what was going on was even weirder, but I don't remember it exactly;
we switched en masse to mailing through necntc after that.)  I can spread the
word that it works now, but that wasn't the first time that people here have
had problems sending mail through the CWRU mail system; it is to be hoped
that it was the last, but "once burned...".

(Note:  I have restored our sendmail to using "@" "properly", with the
restoration of our pathalias database to [partial] functionality.)

++Brandon
-- 
Brandon S. Allbery, uunet!marque!ncoast!allbery			DELPHI: ALLBERY
	  For comp.sources.misc send mail to <backbone>!sources-misc
comp.sources.misc is moving off ncoast -- please do NOT send submissions direct
	  "So many articles, so little time...."  -- The Line-Eater