| Commit message (Collapse) | Author | Files | Lines |
|
mitigate Outlook et al 'on behalf of' displays. Bug #736849.
|
|
which confuses Outlook (formerly known as FAQ 2.3). See also <http://mail.python.org/pipermail/mailman-developers/2006-July/019040.html>. Bug #266824.
|
|
In addition, Mailman no longer escapes From_ lines in the body of
messages sent to regular list members, although MTA's may do it anyway.
This is to avoid breaking signatures per Bug #265967. Changes include
- Message.py, added a Generator class to avoid header folding and an
as_string() method wirth a mangle_from_ argument.
- Mailbox.py, uses new Message.Generator class.
- SMTPDirect.py, uses as_string(mangle_from_=False) to flatten message.
- Scrubber.py, removed unused ScrubberGenerator class.
|
|
normalization, removal of tabs, copyright year updates to changed files,
docstring and comment fixes, and usage of True/False. I also made a pass
through the NEWS file.
One import was reordered, and after this commit I will move the mmdsr.readme
file to README.mmdsr.
From my perspective, after that we're ready to go.
I will port these changes forward to the trunk.
|
|
|
|
and mm_cfg.USE_ENVELOPE_SENDER = Yes
|
|
|
|
|
|
munging Sender and Errors-To headers.
|
|
|
|
|
|
|
|
described here:
http://mail.python.org/pipermail/mailman-developers/2003-November/016119.html
The issue is that if we get an SMTPResponseException with a permanent
error code, we don't want to add all the recipients to the failures
dict, otherwise they'll all score a bounce. That's not appropriate
because the message is being rejected by the local smtpd for reasons
having to do with the content of the message, not because there's some
delivery problem to the recipient.
Log all problems now to logs/smtp-failure.
|
|
|
|
|
|
|
|
system call) during the conn.sendmail() call. This just sets the
message up to retry later.
|