🚀 go-pugleaf

In article <BsJq4z.686@andy.bgsu.edu> jmiller@andy.bgsu.edu (Jim Miller) writes:
>However, the command on the uucp job has the address re-written into an
>idiotic Bang-ized RFC822 format:

Of course it is.  "rmail" is a UUCP MTA, and is not guaranteed to have
any concept of @-style RFC-822 addressing.  If you want to be at all
compatible with the outside world, you will only hand rmail addresses
that it is guaranteed to handle.  Some mailers (i.e., smail3 and
sendmail) allow you to configure this, but you had best be very
careful that you verify correct behavior before you turn this on.

The address passed to the "rmail" command is the envelope address,
anyway, and can be (and should be!) modified as necessary on each hop
of the route to ensure correct delivery.  There's no reason for the
user to ever see that address.

>Obviously "andy.bgsu.edu!jmiller" is NOT what I intended.  bgsuvax
>handles "rmail abc@d.e.f" just fine, but doesn't like the bang-ized
>format of "d.e.f!abc".

If bgsuvax's rmail doesn't accept "rmail d.e.f!abc", but does accept
"abc@d.e.f", then they should fix their MTA.  RFC-976 clearly states
that the former format ("bang domain" format) is the preferred method
for envelope-to addresses between UUCP hosts.

-- 
Marc Unangst                | Real men don't make backups.  Real men never
mju@mudos.ann-arbor.mi.us   | accidentally delete files that they're going
<backbone>!sharkey!mudos!mju| to need later.