🚀 go-pugleaf

According to jmiller@andy.bgsu.edu (Jim Miller):
>   The mail is getting punted as it should, EXCEPT for the address
>that is contained in the rmail command.  The headers in the actual mail
>message are OK (I have looked at them in the uucp spool directory).
>However, the command on the uucp job has the address re-written into an
>idiotic Bang-ized RFC822 format:
>

This is the only thing that MMDF can do.  The interface to mail
via uucp is well defined.  rmail is guaranteed to take bang
addresses (old rmails only take one recipient on the command
line).

>If I send mail to "jmiller@andy.bgsu.edu" the job gets queued as:
>
>bgsuvaxN2a99  08/06-00:56  S  bgsuvax  mmdf 281 D.wendy65e49fe
>              08/06-00:56  S  bgsuvax  mmdf  rmail andy.bgsu.edu!jmiller 
>
>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".

No, it _is_ what you intended.  a.b.c!user and user@a.b.c are
exactly the same address, in different notation.  IF bgsuvax's
rmail can't handle a bang on the command line, then its rmail
is BROKEN.

>
>If I understand things correctly, the uucp channel program is doing this.
>In my mmdftailor file, I have tried "ap=822" and "ap=same", trying
>to get the channel to leave the address alone.  

The 'ap' parameter only affects the headers.  The uucp channel
is performing protocol conversion, translating an RFC 822
address into the correct format for the UUCP network.  A
(hypothetical) decnet channel would turn 'user@node' into
'node:user' before passing it along.