Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!gatech!rayssd!gmp
From: gmp@rayssd.UUCP
Newsgroups: comp.mail.headers
Subject: Re: overuse of Received: headers
Message-ID: <843@rayssd.RAY.COM>
Date: Fri, 10-Apr-87 16:12:58 EST
Article-I.D.: rayssd.843
Posted: Fri Apr 10 16:12:58 1987
Date-Received: Sat, 11-Apr-87 18:52:39 EST
References: <1676@lsuc.UUCP> <323@dcl-csvax.comp.lancs.ac.uk> <834@rayssd.RAY.COM> <43258@beno.seismo.CSS.GOV>
Sender: gmp@rayssd.RAY.COM (Gregory M. Paris @ Raytheon Company, Portsmouth RI)
Reply-To: gmp@rayssd.RAY.COM (Gregory M. Paris)
Organization: Raytheon Company, Portsmouth RI
Lines: 27
Keywords: sticky flag bug for -oM
Summary: Rick's solution doesn't work for 4.2BSD sendmail

In article <43258@beno.seismo.CSS.GOV> rick@seismo.CSS.GOV (Rick Adams) writes:
> The simplest way to do it is to modify rmail.c. Here is a diff -c from
> the 4.3 bsd rmail.c. to what we are running.
> 
> ---rick

If you decide to modify your 4.2 BSD rmail in a similar manner, beware
that it will probably not work.  The line below from Rick's patch
is what aggravates an apparent bug in 4.2's sendmail.

>  		(void) sprintf(cmd, "exec %s -em -i -oMrUUCP -oMs%s.%s -f%s",

The two -oM options don't work; the second one is ignored.  To fix this,
you could get rid of the -oMrUUCP, since (at least in my configuration)
it wasn't used anyway, or if you have source, you could modify sendmail's
main.c where it calls setoption for the -o flag.  The line should
look like what follows.

		setoption(p[2], &p[3], FALSE, p[2] == 'M' ? FALSE : TRUE);

This change prevents the sticky flag from being set when setting a macro
value from the command line.  I made this change and all works fine.

-- 
Greg Paris ............................. gmp@rayssd.RAY.COM (a UUCP domain)
{cci632,cbosgd,gatech,ihnp4,linus,mirror,necntc,uiucdcs,umcp-cs}!rayssd!gmp
................. People like you should not be allowed to start any fires.