On Fri, 17 Jan 1997 David.Osborne@??? wrote:
> I'm don't fully understand the headers in the spool/input/*H files or shown by
> eximon. In this particular case, I'd like to understand why a sender address
> generated by Majordomo's "resend" script seems to have been rewritten... the
> headers shown by eximon are:
>
> Local sender: <majordom@???>
> Recipients:
> matrox-users-outgoing@???
>
> P Received: from majordom by nottingham.ac.uk with local (Exim 1.58 #10)
> id 0vkry8-0003gT-00; Thu, 16 Jan 1997 13:35:00 +0000
> I Message-Id: <199701161334.NAA32948@somehost>
> F From: <someuser@somehost>
> T To: <matrox-users@???>
> Subject: Re: Monster 3D 4 Sale
> Date: Wed, 15 Jan 1997 22:24:57 -0000
> MIME-Version: 1.0
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> * Sender: owner-matrox-users
> Precedence: bulk
> R Reply-To: matrox-users@???
> S Sender: Majordomo list manager <majordom@???>
>
>
> The Sender field prefixed by "*" is what Majordomo generated (it should be
> fully-qualified). Why is there another, prefixed by S? The sender should be
> the list-owner, who needs to know about delivery failures for addresses in
> their list, not majordom (which comes to me).
>
> Can I get exim to fully-qualify a Sender address with ${primary_hostname} ?
>
> David
>
>
>
Looks kinda like a trusted user problem. It seems that "majordom"
should be added to the list of trusted users (see docs), so that majordomo
can set the sender to anything it wants.
Tom
