Public bug reported:
Hi
I use mailman-2.1.14-6 on fedora 15
When I use english regex topics, all works good.
If I use russian regex, subscribers-members of a topic don't receive
e-mails. Bacause subject doesn't match with regex.
In source code(/usr/lib/mailman/Mailman/Handlers/Tagger.py) I found that
subject doesn't modified from MIME format.
If it english all seem good, but in my case I saw:
pattern is "<C8><D5><CA>"
line is "=?KOI8-R?Q?=C8=D5=CA?="
I create simple patch that use decode_header function from email module
** Affects: mailman
Importance: Undecided
Status: New
** Tags: charset header mailman topics
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/891676
Title:
topics don't work with national(russian) languages
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/891676/+subscriptions
Public bug reported:
(From a recent post to mailman-users(a)python.org)
I usually use the web interface for approving messages. But I
occasionally do it via Email. When I do, I get a response back that looks
like this:
The results of your email command are provided below. Attached is your
original message.
- Results:
Confirmation succeeded
- Unprocessed:
Approved: <admin password>
- Done.
---- CUT HERE -----------------------
To me at least, this suggests that the message has been rejected, not
approved, as the text says that the approval command was not processed.
I know this isn't the case because I see the message posted to the list,
but when I initially saw it, I had a panic as I thought I'd lost a message
for the list.
Is it possible to fix this so that the message is more clear about what
has happened? The "Confirmation succeeded" message is not very
explanatory, and seen in isolation doesn't really tell you anythying about
whether the message was approved or rejected.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: Confirmed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/889968
Title:
Response to email approval of held message is misleading
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/889968/+subscriptions
Public bug reported:
The code in Mailman/Gui/General.py for setting new_member_options
doesn't take into account the fact that there might be option bits other
than 'hide', 'ack', 'notmetoo' and 'nodupes' that are set, and it resets
them even if the four displayed options are unchanged. This also affects
bin/config_list which cannot set bits other than those 4 unless set via
mlist.new_member_options =.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: Confirmed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/865825
Title:
Undisplayed new_member_options bits are reset whenever the General
Options page is submitted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/865825/+subscriptions
Public bug reported:
The message:
#: cron/checkdbs:161
msgid ""
"From: %(sender)s on %(date)s\n"
"Subject: %(subject)s\n"
"Cause: %(reason)s"
is effectively untranslated in messages/eu/LC_MESSAGES/mailman.po.
Some keywords in the templates/eu/article.html template are translated
and shouldn't be.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: Confirmed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/836861
Title:
Errors in Basque i18n.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/836861/+subscriptions
Public bug reported:
If ARCHIVE_HTML_SANITIZER = 2 in mm_cfg.py, messages which are multipart
after content filtering will appear as the raw (undecoded) message body
in the plain format digest and in the archive.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/787790
Title:
Scrubber can return raw message body for multipart message
Public bug reported:
admindb.py displays held message excerpt but fails to get proper message charset, leading unreadable text excerpts especially for languages using multi-byte code.
Attached patch solves this problem by finding the first charset in multipart message, which is used in Decorate.py etc.
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/779751
Title:
admindb fail to find message charset
Public bug reported:
Utils.websafe() escapes characters like < and >. Recent change in this
function added 8bit characters like \xbc and \xbe as 'dangerous'
characters. This breaks Japanese text display because they appear as a
part of double-byte characters. Because these characters are only
'dangerous' for old browsers, I suggest reverting the change or at least
making configurable whether the site administrator apply changes or not.
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/774588
Title:
recent change in Utils.websafe() breaks Japanese (and other double-
byte language) texts
Public bug reported:
When accessed over https, Mailman should set the 'secure' cookie flag.
Please see the attached patch which implements that.
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/770377
Title:
Mailman should set the 'secure' cookie flag when accessed via https
*** This bug is a security vulnerability ***
Private security bug reported:
Current 2.1 admindb interface have no link (or button) to logout the administrator/moderator. An administrator can logout from mailman from admin interface but a moderator cannot logout without zapping the moderator cookie by browser's function (if it is provided) or terminating the browser. The admindb web page should have a convenient 'logout' link.
Another inconvenience in admin logout funciton is that if the site-wide admin is allowed by mm_cfg.ALLOW_SITE_ADMIN_COOKIES then the administrator cannot logout with visiting the 'Logout' link in the admin page.
These bugs are fixed by lp:~tkikuchi/mailman/logout-enforcement and the branch was requested to merge into 2.1 series.
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is a direct subscriber.
https://bugs.launchpad.net/bugs/769318
Title:
admindb should have 'logout' function
Public bug reported:
If a real name or comment in a From: or other sender header is RFC 2047
encoded and the decoding contains an unquoted comma or other special,
the Message methods get_sender() and get_senders() can return bogus
addresses leading to other issues.
A patch is attached.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/702516
Title:
RFC 2047 encoded From: header is not correctly parsed.