| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Here is my major patch. It was postponed to 2.2 but since 2.2 is so late...
|
|
|
|
| |
[ 1026977 ] check attachment header by SpamDetect.py
|
| |
|
|
|
|
|
|
|
| |
[ 904850 ] Scrubber in regular delivery per list
[ 1027882 ] filter attachments by filename extensions
and a patch in mailman-dev mailing list
http://mail.python.org/pipermail/mailman-developers/2004-September/017246.html
|
|
|
|
|
|
|
|
|
| |
Closing [ 1003070 ] Decode original subject in post acknowledgement
by Soji IKEDA
Modified Files:
Tag: Release_2_1-maint
Mailman/Bouncer.py
Mailman/Handlers/Acknowledge.py
|
|
|
|
| |
Use unicode concatnation in header+message+footer
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modified Files:
Mailman/Handlers/Scrubber.py
Mailman/Defaults.py.in
Fixes some bugs:
charset problem where input/output charset are different
text file without charset makes trouble when merging into one text msg.
delete content-transfer encoding
use Utils.oneline() for i18n filename
use msg.walk() to collect parts
Introduce:
mm_cfg.SCRUBBER_DONT_USE_ATTACHMENT_FILENAME to prevent extremely long fn.
|
| |
|
| |
|
|
|
|
| |
munging Sender and Errors-To headers.
|
|
|
|
|
| |
subject header in the list's preferred character set and make sure it
is all on one line, when sent back to the original author.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
process(): Reworked the way we calculate the List-Id header in the
face of i18n descriptions which may need to be quoted (if ASCII and
containing RFC 2822 special chars).
What we do now is RFC 2047 encode just the description part, if there
is one, then use formataddr() to combine that with the email
address-like list identification.
|
|
|
|
|
|
|
|
|
| |
message is originally received and the time the digest is sent. If
the configuration changes by setting ARCHIVE_HTML_SANITIZER to 0, a
DiscardMessage exception can occur during the scrubbing. Catch this
error.
Closes SF #860135 with basic solution by Martin Pool.
|
|
|
|
|
| |
in case there are any special characters (in the RFC 2822) in the
description.
|
| |
|
|
|
|
| |
header_filter_rules.
|
|
|
|
|
|
| |
process(): When we encode the text, catch ValueError along with UnicodeError
and LookupError. The ValueError can be raised if the charset is the empty
string. Closes SF bug # 834486.
|
|
|
|
|
|
| |
process(): When we encode the text, catch ValueError along with UnicodeError
and LookupError. The ValueError can be raised if the charset is the empty
string. Closes SF bug # 834486.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
I18ners please double check (except Tokio). It's always so painful to
resolve conflicts here, I hope I got them right.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Ademar de Souza Reis Jr
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
header to the headers and footers parts as a hint to persnickety
clients (not mentioning Outlook here) that the text should be
displayed inline instead of as attachments.
It does no harm so even if it doesn't completely fix the problem it
sounds like a good idea.
|
| |
|
|
|
|
|
| |
system call) during the conn.sendmail() call. This just sets the
message up to retry later.
|
|
'Release_2_1-maint'.
|