| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
would insert an extra space between the prefix and the subject.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
header to go to the options login page instead of the
listinfo page.
options.py - Changed to only issue the "No address given" error if coming
from the page itself so we don't get the error when linking
from another page or the List-Unsubscribe: header.
- Changed to remember the user's language selection when
redisplaying the page after an error.
|
|
|
|
| |
comprehension where appropriate.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
| |
from the posts from mailling list for gatewaying to nntp.
|
| |
|
|
|
|
| |
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:".
|
|
|
|
| |
Here is my major patch. It was postponed to 2.2 but since 2.2 is so late...
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
in case there are any special characters (in the RFC 2822) in the
description.
|
| |
|
| |
|
| |
|
|
'Release_2_1-maint'.
|