Excellent, thank you very much Kyle.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kyle Wheeler Sent: 17 April 2008 02:52 PM To: mutt-users@mutt.org Subject: Re: Return-Path problem -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, April 17 at 12:41 PM, quoth Dirk Moolman: > just did. The manual says: > > 3.291. use_envelope_from > > Type: boolean > Default: no > > "When set, mutt will set the envelope sender of the message. If > ``$envelope_from_address'' is set, it will be used as the sender > address. If not, mutt will attempt to derive the sender from the "From:" > header." > > > I am still trying to understand the terminology being used. What does > "envelope" mean here - is this the header of the mail as seen in other > mail programs, like Outlook ? Not quite. Every email message has an "envelope" sender and an "envelope" recipient that, much like regular snail mail, doesn't necessarily have anything to do with the actual contents of the email. For example, when you BCC someone, their address is included in the envelope list of recipients, but their address should never appear in the actual email's headers. When email is sent from one machine to another, first the sender's address must be sent (this is called the "envelope sender"), then the list of recipients must be sent (the "envelope recipients"), then the content of the message, including all headers. The contents of the headers or of the message doesn't have to have anything to do with the sender or recipient addresses that is sent before the message (i.e. as part of the envelope). > Question 2: does this only work because I have my From: adres set > in the muttrc as well ? If by "this", you mean "use_envelope_from makes the envelope sender the same as your from header" then the answer is yes. ~Kyle - -- Those who will not reason, are bigots, those who cannot, are fools, and those who dare not, are slaves. -- George Gordon Noel Byron -----BEGIN PGP SIGNATURE----- Comment: Thank you for using encryption! iD8DBQFIB0gNBkIOoMqOI14RAs+DAJ9GpTYkW46Yt7yV2rec15yj7OC95wCfeQBZ lIQfLHYtUcrBq2BrcANfnm4= =tL8r -----END PGP SIGNATURE----- *** Disclaimer *** The information contained in this e-mail is confidential and legally privileged and is intended solely for the addressee and to others who have the authority to receive it. Access to this e-mail by anyone else is unauthorized and as such, any disclosure, copying, distribution or any action taken or omitted in reliance on it is unlawful. If you have received this e-mail in error, please notify the sender immediately. The views expressed in this e-mail are the views of the individual sender and should in no way be construed as the views of the Company. The Company is not liable to ensure that outgoing e-mails are virus-free. The Company is not liable, should information or data, for whatever reason, be corrupted or fail to reach its intended addressee. The Company is not liable for any loss or damage of whatsoever nature and howsoever arising resulting from the opening or the use of the information in this e-mail, including its attachments and links. The sender of this e-mail is subject to and bound by the terms and conditions of Company’s Electronic Communications Usage Policy.
