Mailman 3 May 2012 - Mailman-coders

[Bug 721015] [NEW] Typo in cron/gate_news usage() definition.
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: The usage function defined in cron/gate_news defines its first argument as 'status' but then refers to it as 'code'. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/721015 Title: Typo in cron/gate_news usage() definition.

1 1

[Bug 705715] [NEW] @listname entries in *_these_nonmembers are case sensitive.
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: The listname in @listname entries in *_these_nonmembers should be lower- cased before attempting to instantiate the list. ** Affects: mailman Importance: Low 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/705715 Title: @listname entries in *_these_nonmembers are case sensitive.

1 3

[Bug 700528] [NEW] bin/rmlist does not remove the heldmsg-LISTNAME-* files for the list.
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: bin/rmlist LISTNAME should remove any data/heldmsg-LISTNAME-* files. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Triaged ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/700528 Title: bin/rmlist does not remove the heldmsg-LISTNAME-* files for the list.

1 2

[Bug 697161] [NEW] Bug in mm-handler-2.1.10 regarding lists named xxx-admin
by Sebastian Hagedorn 15 Jun '12

15 Jun '12

Public bug reported: We're running Mailman 2.1.14 and have recently begun using mm- handler-2.1.10 from the contrib directory as MTA for sendmail. Everything appeared to work fine, but after a few months we were alerted by one of our users that no mail was delivered anymore to one of his lists. The list's name is mathematica-admin. It turns out that mm- handler strips the -admin part and tries to deliver the mail to a list named mathematica, which does not exist. We had a small number of other lists with the same problem. I've created a patch that fixes it and another small issue (a variable is passed to a subroutine, but a global variable is actually used there). ** 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/697161 Title: Bug in mm-handler-2.1.10 regarding lists named xxx-admin

2 3

[Bug 666181] [NEW] wrong From field in subscription notification to admin
by Ilya Belyy 15 Jun '12

15 Jun '12

Public bug reported: Steps to reproduce: Create two mail lists ml01 (hosted on domain dom.1) and ml02 (hosted on domain dom.2) Add user to ml01 $ add_members -a y -r - ml01 lkjhlkhlkh(a)wefqwefqwef.com Subscribed: lkjhlkhlkh(a)wefqwefqwef.com Notification email to the admin of ml01 will look as following: Subject: Ml01 subscription notification From: mailman(a)dom.2 To: mladmin00(a)dom.1 Message-ID: <mailman.1.1287993063.7501.ml01(a)dom.1> Date: Mon, 25 Oct 2010 14:51:03 +0700 Subscribed: lkjhlkhlkh(a)wefqwefqwef.com Apparently, host name of the mail list is not considered when composing the notification message. I've checked 2.1.9 and 2.1.14 - both have the same bug ** Affects: mailman Importance: Undecided Status: New -- wrong From field in subscription notification to admin https://bugs.launchpad.net/bugs/666181 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 966531] [NEW] OutgoingRunner consumes 100% cpu
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: If OutgoingRunner's attempt to connect to the outgoing SMTP server results in socket.error, OutgoingRunner requeues the message and continues processing without delay resulting in continuously looping over the queue until the socket.error is somehow resolved. ** 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/966531 Title: OutgoingRunner consumes 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/966531/+subscriptions

2 9

[Bug 910440] [NEW] Admindb interface can crash with a UnicodeDecodeError when displaying held message contents.
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: The fix for bug #629738 decodes base64 and quoted-printable message bodies for display in the admindb held message display. If the decoded message body contains characters not representable in the character set of the list's preferred language, an uncaught UnicodeDecodeError can result when formatting the message for web display. ** 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/910440 Title: Admindb interface can crash with a UnicodeDecodeError when displaying held message contents. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/910440/+subscriptions

1 2

[Bug 891676] [NEW] topics don't work with national(russian) languages
by Roman Sokolkov 15 Jun '12

15 Jun '12

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

3 8

[Bug 889968] [NEW] Response to email approval of held message is misleading
by Mark Sapiro 15 Jun '12

15 Jun '12

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

1 2

[Bug 865825] [NEW] Undisplayed new_member_options bits are reset whenever the General Options page is submitted.
by Mark Sapiro 15 Jun '12

15 Jun '12

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

1 2

[Bug 836861] [NEW] Errors in Basque i18n.
by Mark Sapiro 15 Jun '12

15 Jun '12

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

1 2

[Bug 787790] [NEW] Scrubber can return raw message body for multipart message
by Mark Sapiro 15 Jun '12

15 Jun '12

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

2 6

[Bug 779751] [NEW] admindb fail to find message charset
by Tokio Kikuchi 15 Jun '12

15 Jun '12

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

2 6

[Bug 774588] [NEW] recent change in Utils.websafe() breaks Japanese (and other double-byte language) texts
by Tokio Kikuchi 15 Jun '12

15 Jun '12

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

2 3

[Bug 770377] [NEW] Mailman should set the 'secure' cookie flag when accessed via https
by Ward Vandewege 15 Jun '12

15 Jun '12

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

2 3

[Bug 769318] [NEW] admindb should have 'logout' function
by Tokio Kikuchi 15 Jun '12

15 Jun '12

*** 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

2 2

[Bug 702516] [NEW] RFC 2047 encoded From: header is not correctly parsed.
by Mark Sapiro 15 Jun '12

15 Jun '12

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.

2 4

[Bug 677115] [NEW] Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded.
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: A list moderator receives a held message notification and attempts to approve the message by replying to the third part (second attachment) and including an Approved: <password> line as the first line of the reply. If the moderator's MUA base64 encodes the reply for i18n or other reasons, the Approved: line is not found and the message is discarded. ** Affects: mailman Importance: Undecided Status: New -- Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded. https://bugs.launchpad.net/bugs/677115 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 670988] [NEW] Missing format character in Spanish translation
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: The Spanish (es) translation of the bin/check_perms message "%(path)s bad group (has: %(groupname)s, expected %(MAILMAN_GROUP)s)" is missing the 's' in '%(path)s'. This prevents check_perms from reporting/fixing group errors and any other problems not found before the first group error. ** Affects: mailman Importance: Undecided Status: New -- Missing format character in Spanish translation https://bugs.launchpad.net/bugs/670988 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 1004213] [NEW] "list my other subscriptions" does not
by Ross Boylan 26 May '12

26 May '12

Public bug reported: Summary: "list my other subscriptions" fails to list all my subscriptions at mail.kde.org, and obeys no consistent rule I can discern. There is a secondary issue: the word "other" is misleading, as the list includes the list from which one clicks that button. I suggest changing it to "list my subscriptions" or "list all my subscriptions at this site." This was at mail.kde.org, running MM 2.1.14. The site administrator says the code has not been customized locally; I couldn't get info on the exact OS or package. A mail failure on my end caused several days of bounced emails and I wanted to check that my subscriptions were OK at mail.kde.org. Through ross(a)biostat.ucsf.edu I subscribe to kde, kdepim-users, and kde-linux, The first list checked (kde-linux? maybe kde) looked OK (mail delivery was enabled) and so I clicked on "list my other subscriptions". This showed 2 of the 3 subs, not kdepim-users. I went to kdepim-user's general interface and asked to list subscribers. It accepted my edress and password, and showed my edress among the subscribers. When I checked my info for kdepim-users it again seemed to show my subscription as active. I noticed I had misspelled my name, and corrected it. I suspected that the name misspelling accounted for the fact kdkepim-users did not show up in my list of subscriptions. Note that all 3 lists show up in the site's master list of mailman lists; they are in the same domain. >From kdepim-users I then clicked "list my other subscriptions". Again I saw only 2, but a different 2: kde was missing. When I logged into that list my subscription again looked fine. I clicked on list other subs, and this time got a list that had only kde on it (note that the first list of subscriptions I saw had kde and kde-linux, but not kdepim). This disproved my theory that it would only show 2, as well as my theory about the name misspelling mattering. All accounts have the same password. I suspect this is just a cosmetic problem, but am not sure. I used Konqueror 3.5.9 on KDE 3.5.10 under Debian Lenny. I know; I'm living in the past. I discussed this with site admin; he had no ideas about what could be causing this behavior. Thanks for your work on mailman! ** 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/1004213 Title: "list my other subscriptions" does not To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1004213/+subscriptions

2 3

[Bug 1004052] [NEW] missing confirmation messages on many actions
by Jeff Marshall 25 May '12

25 May '12

Public bug reported: Postorius doesn't seem to have confirmation messages after changing a setting or adding a subscriber. It leaves me uncertain whether my change or subscriber addition went through. ** Affects: postorius Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004052 Title: missing confirmation messages on many actions To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004052/+subscriptions

2 1

[Bug 1001978] [NEW] Request - add date to subscription/unsubscription requests on admin page
by Dean Suhr 20 May '12

20 May '12

Public bug reported: It would be very helpful for administrators to see when the various request on the list management page came in. Please add a data column for subscription and unsubscription requests. ** Affects: mailman Importance: Undecided Status: New ** Tags: admin date request -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1001978 Title: Request - add date to subscription/unsubscription requests on admin page To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1001978/+subscriptions

1 0

[Bug 426979] Re: Mistakes in mailman strings.
by Thijs Kinkhorst 20 May '12

20 May '12

2.1.14 ** Changed in: mailman (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/426979 Title: Mistakes in mailman strings. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/426979/+subscriptions

1 0

[Bug 778088] [NEW] User can set a password with trailing whitespace which prevents login.
by Mark Sapiro 19 May '12

19 May '12

Public bug reported: Both the subscribe CGI and the user options CGI allow setting a password with trailing whitespace, but options login strips the trailing whitespace before validating. Thus, the user can't log in to the options page. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/778088 Title: User can set a password with trailing whitespace which prevents login.

1 1

[Bug 714424] [NEW] Held message user notification should be from -owner, not -bounces
by Mark Sapiro 19 May '12

19 May '12

Public bug reported: If respond_to_post_requests is Yes the notice to the poster of a held post is From: the listname-bounces address. It should be from the listname-owner address. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/714424 Title: Held message user notification should be from -owner, not -bounces

1 1