<<< Date Index >>>     <<< Thread Index >>>

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-----