| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
charset="quoted-printable" parameter, quopri_encode can be
called at t = t.encode(charset, 'replace') which throws
an AssertionError. See log message for r. 8213. Caught this.
- Malformed RFC 2047 encoded filename= parameter can have
a null byte or other garbage in the extension. Cleaned this.
- A message with a message/delivery-status part returns
None for the part's payload. Checked for a payload before
attempting unicode/encode.
|
|
|
| |
before looking for/deleting the Approve(d): line.
|
|
|
|
|
|
| |
but it looks like thare is a buggy MUA or spammer who declairs like so:
Content-Type: text/plain; charset=base64
:-(
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The email address which forms a part of the various CGI data keys
in the admin membership list is now urllib.quote()ed. This allows
changing options for and unsubbing an address which contains a
double-quote character.
- CGI/admindb.py
Added additional test to not display "Database Updated ..." when
coming from the login page.
- CGI/roster.py, HTMLFormatter.py
Changed to show hidden members when authorization is site or list's
admin or moterator password. Patch 1587651.
- Defaults.py.in, Handlers/Cleanse_DKIM.py
Added a new REMOVE_DKIM_HEADERS Defaults.py/mm_cfg.py setting (default
= No) to control removing dkim/domainkey signatures from posts and
mail to -owner.
- Handlers/Decorate.py, Handlers/Scrubber.py
Changed to preserve format=flowed and delsp=yes in the Content-Type:
of the body when adding header/footer and when scrubbing attachments
and to remove trailing spaces from the header/footer lines so they
won't be flowed. Bug 1495122.
Fixed a scrubber issue where the i18n translated 'next part' separator
can be garbled if the list charset is different from the message.
- Queue/Runner.py. Queue/Switchboard.py
Now that we have .bak queue entries for recovery, it is no longer the
case that an unparseable message is lost. In this case, and in case
of other exceptions when dequeueing, I added a preservation feature
to move the .bak file to qfiles/shunt as a .psv file and write an
appropriate log entry. It is also possible for an attempt to shunt
a message to fail. One example that occurred in practice (bug 1656289)
was caused by a huge message that threw a MemoryError in processing and
then threw another MemoryError in the attempt to pickle the message for
the shunt queue. In this case as well, I log and attempt to preserve
the original queue entry by renaming.
|
| |
|
|
|
|
|
|
|
| |
yet ready to work from the trunk). Also, get rid of all the obsolete
.cvsignore directories, they're no longer needed.
Almost ready for 2.1.9rc1!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- In SecurityManager.py, fix the parsecookie() code to work with Python 2.5
generated cookie text. The latter was changed to be more RFC compliant so
it does not output trailing semicolons for each line of cookie text. This
broke the splitting rules, so now first split on newlines, then on ';\s*'.
This should work across all Python versions.
- In Python 2.5, exceptions are new-style, and thus are no longer of
ClassType. The instantiation type test in hold_for_approval() was too
naive. This one is fixed differently here than in the MM trunk because in
Python 2.1, 'type' isn't a type, it's a function and so can't be used as the
second argument to isinstance() directly.
- Raising strings generates deprecation warnings in Python 2.5. Switch the
one weird use of this in Utils.py to use a class exception. Don't call it
"quick exit" though because it's probably not.
|
|
|
|
|
|
|
|
| |
outside the character set of the list's language.
- Utils.py Fixed a security hole which allowed a crafted URI to inject
bogus apparent messages into the error log, possibly inducing an admin to
visit a phishing site.
|
|
|
|
| |
when payload is None.
|
|
|
|
| |
comprehension where appropriate.
|
| |
|
|
|
|
| |
because it is overwrapped in Mailman.Message.
|
| |
|
|
|
|
| |
new handler to be included in both GLOBAL_PIPELINE and OWNER_PIPELINE.
|
|
|
|
| |
filter if X-List-Administrivia header is forged.
|
| |
|
| |
|
|
|
|
|
| |
The keyword 'reduced_list_headers' is taken from CookHeaders.py and looks
like it is, reviewing Message.py.
|
|
|
|
| |
even if it has X-List-Administrivia header ( mostly -owner notification ).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Subject manipulation should be done in unicode string mode.
|
|
|
|
|
| |
Only check in Release_2_1-maint branch because 2.2 will require
higher version of python.
|
| |
|
|
|
|
|
|
| |
I've tested the example by Mark Sapiro:
http://mail.python.org/pipermail/mailman-developers/2005-November/018395.html
both with and without 'Content-Transfer-Encoding' but may need more test.
|
|
|
|
| |
users of MS Outlook and Apple Mail.
|
| |
|
|
|
|
| |
to mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and mm_cfg.USE_ENVELOPE_SENDER = Yes
|
| |
|
| |
|
|
|
|
| |
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.
|