Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share It With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

ADVERTISEMENT
ADVERTISEMENT

Links 1 through 7 of 7 by @nm tagged Messaging/Envelopes

'Mail headers such as To:, Cc:, Bcc: are IRRELEVANT for routing and delivery of the mail. Mail routing will only look at the ENVELOPE - there is no difference from snail mail here.'

Share It With Others!

'have procmail at the provider insert the special header information that's recognized by the downstream procmail for local routing. That would, however, mean the dropbox would get one copy of the mail for every downstream recipient rather than one copy f

Share It With Others!

Share It With Others!

"envelope sender" == "envelope from" == "bounce address" == "2821 from" == "821 from" == "MAIL FROM"

Share It With Others!

direct link to the #envelopeLinks section, whcih lists lots of links about the "original envelope" recipient and sender addresses

Share It With Others!

'The issue is that MUAs and MUA-level filters like SpamAssassin cannot reliably determine the envelope sender (note; not recipient) at intermediate steps along the Received chain. Some forwarding use cases, like mailing lists, fetchmail, or SRS-compliant

Share It With Others!

'(Learn from "fetchmail"'s mistakes.) Moreover: Your proposed parsing method is too simplistic and highly flawed; and many MTAs do not add envelope recipient information into "Received:" headers for privacy reasons.'

Share It With Others!

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT