| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
because it is overwrapped in Mailman.Message.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
Both are introduced in Python2.3. UnicodeError catches both.
|
|
|
|
| |
Fall back to email address.
|
| |
|
|
|
|
| |
Use unicode concatnation in header+message+footer
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
'Release_2_1-maint'.
|