| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
and epilogues in the calculation of messages sizes.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
multipart/alternative message after content filtering.
|
| |
|
|
|
|
| |
Temporary work around to ignore such case.
|
| |
|
|
|
|
|
|
|
|
|
| |
Although the RFC2231 bug example in the tracker has been solved in
mailman-2.1.6, there may be more cases where ToDigest.send_digests() can
block regular delivery. I put the send_digests() calling part in try -
except clause and leave a message in the error log if something happened
in send_digests(). Daily call of cron/senddigests will notify more details
to the site administrator.
|
|
|
|
|
|
|
|
|
|
| |
it is possible for a message to be "not is_multipart()" but to have a None
payload. I know of at least one situation where this can happen: you have a
Content-Type: multipart/* but there is nothing but two blank lines between the
first boundary and the end boundary. Under email 3, you get a string payload
but under email 2.5 you get None.
Because there's nothing in such parts, they should be safe to ignore.
|
|
|
|
|
| |
be escaped for it is the insert directive. It was my trial and error
in the comments in previous version. Well, I didn't think of '++' ...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
prefix_subject() in CookHeaders.py
When calling re.sub() to substitute the subject prefix, you have to escape
the pattern, otherwise prefixes like [C++] cause "multiple repeat"
exceptions in re.
Also, whitespace normalization and copyright years updates.
|
|
|
|
| |
Both are introduced in Python2.3. UnicodeError catches both.
|
|
|
|
| |
trying to call None.splitlines().
|
|
|
|
| |
Fall back to email address.
|
|
|
|
| |
(should have went out an intermediate code) :-<
|
|
|
|
| |
Log anonymize record in 'post' for admin's inspection convenience.
|
|
|
|
| |
from the posts from mailling list for gatewaying to nntp.
|
| |
|
|
|
|
|
|
|
| |
Instead of re-use, a new variable 'nonmember_rejection_notice' was
introduced. For compatibility with my patch for subject numbering,
'data_version' was raised by 3. Sorry for the leap but I want MY user
to get smooth update. (TK)
|
| |
|
|
|
|
| |
with some code clean up. Also, include SV (danish/swedish) Re: like pattern.
|
|
|
|
|
| |
Now the default behavior of prefixing is "Re: [prefix] subject".
Variations like "Re[2]:" and German style "AW:" is now replaced by "Re:".
|
|
|
|
| |
Update copyright years for files changes in 2005. Whitespace normalization.
|
| |
|
|
|
|
| |
Thanks Thomas for raising my attention.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
960551 Bug: Plain digest with mixed charsets
995029 Patch against Mailman 2.1.5 release fixes bug #913397
|
| |
|
| |
|
|
|
|
| |
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.
|