Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 5/3/83; site stc-a.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!ukc!stc-a!andrew
From: andrew@stc-a.UUCP (Andrew Macpherson)
Newsgroups: net.mail
Subject: Re: Yet another Sendmail problem
Message-ID: <200@stc-a.UUCP>
Date: Thu, 18-Apr-85 05:00:43 EST
Article-I.D.: stc-a.200
Posted: Thu Apr 18 05:00:43 1985
Date-Received: Sat, 20-Apr-85 09:05:12 EST
References: <535@spp2.UUCP> <749@ihnp4.UUCP>
Organization: STC Telecommunications, London.
Lines: 34

> From: gjm@ihnp4.UUCP (Gary J. Murakami)
> Message-ID: <749@ihnp4.UUCP>

> Sendmail couples the "UGLY UUCP From" lines and the RFC "From:" line;
> this causes dificulty since it is difficult to rewrite "From" while
> leaving "From:" intact.  However, my tests show that at worst, the line
> may read "From: ihnp4!site!person", and any other munging is probably
> being done at your local site.

This coupling can be avoided!  It is caused by $g being expanded/ripped
apart to form the "UGLY UUCP From" line, but..  4.2 rmail can accept
UGLY UUCP lines, or ``Bang Notation'' From-space lines.  If you are
trying to stick to RFC822 for the From: part of the headder by using
the "suucp" mailer (u@h), scrap the 'U' flag in the mailer definition,
and redefine the 'l' macro:

DlFrom $w!$f  $d

$w is your hostname, $d the date and $f is the string passed in as the
-f argument to sendmail by rmail, which will always be ``Bang Format''
so you build up the return path in the From-space line while leaving
the domain based addresses inviolate.

_G_r_e_a_t_ _i_s_n_'_t_ _i_t_?

BTW my SYSV neighbours havn't complained (yet), so I assume that their
rmail behaves simmilarly.

If anyone's experiance proves this wrong, please let me know (I expect
an empty mailbox...)
-- 
Regards,
	Andrew Macpherson.	<andrew@stc.UUCP>
	{creed, idec, root44, stl, ukc}!stc!andrew