Mailman 3 May 2010 - Mailman-coders

[Bug 582525] [NEW] Add sieve rules to route messages properly to IMAP server
by Barry Warsaw Sept. 20, 2010

Sept. 20, 2010

Public bug reported: When a message from Mailman gets routed to an IMAP server (e.g. for archiving or administration), we need a sieve rule to do proper routing. E.g. for dovecot. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Add sieve rules to route messages properly to IMAP server https://bugs.launchpad.net/bugs/582525 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 582524] [NEW] Use IMAP CREATE to add folders to IMAP archiver on list creation
by Barry Warsaw Sept. 20, 2010

Sept. 20, 2010

Public bug reported: For every mailing list we expose to IMAP, we'll want to create a few folders. Hook in the IMAP folder creation to the list creation hooks. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Use IMAP CREATE to add folders to IMAP archiver on list creation https://bugs.launchpad.net/bugs/582524 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 582522] [NEW] Implement archive delivery via LMTP
by Barry Warsaw Sept. 20, 2010

Sept. 20, 2010

Public bug reported: Dovecot beta supports delivery via LMTP. Mailman 3 should implement a generic archive delivery implementation that delivers via LMTP. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => High -- Implement archive delivery via LMTP https://bugs.launchpad.net/bugs/582522 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 543627] [NEW] mailman command does not initialize directory structure on first run
by Patrick Ben Koetter Sept. 20, 2010

Sept. 20, 2010

Public bug reported: Contrary to "src/mailman/docs/START.txt" which says Run the ``bin/mailman info`` command to see which configuration file Mailman will use, and where it will put its database file. The first time you run this, Mailman will also create any necessary run-time directories and log files. neither the mailman command alone nor running it with option "info" creates the initial directory structure. If you go with the default settings in mailman.cfg you probably won't notice because you are within the correct directory structure. But if you set "var_dir: /opt/mailman" in e.g. /etc/mailman.cfg things break. I believe fixing this would also fix ticket #543620. ** Affects: mailman Importance: Undecided Status: New -- mailman command does not initialize directory structure on first run https://bugs.launchpad.net/bugs/543627 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2

[Bug 497968] [NEW] Need a 'no-daemonize' option for '/bin/mailman start'
by Steve Burling June 19, 2010

June 19, 2010

Public bug reported: The version of Mailman distributed with Apple's Mac OS X Server has a hacked up mailmanctl, primarily to support not daemonizing in the launchd environment. (I think). Their hack is ugly, and it'd be nice if it was made unnecessary. ** Affects: mailman Importance: Undecided Status: New -- Need a 'no-daemonize' option for '/bin/mailman start' https://bugs.launchpad.net/bugs/497968 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 266375] Re: mailman corrupts RFC2047-encoded headers
by A.M. Kuchling May 21, 2010

May 21, 2010

One possible fix is to parse the subject header's content by turning it into a Header object. This seems to work for simply sending a message through, but I don't know if every use of the Subject header in Mailman works correctly if the value is a Header object instead of a string. It does seem like a bug in the underlying email package, though; I've filed http://bugs.python.org/issue8769 in the Python bug tracker. ** Bug watch added: Python Roundup #8769 http://bugs.python.org/issue8769 ** Attachment added: "Possible fix" http://launchpadlibrarian.net/48871021/rfc2047-patch.txt -- mailman corrupts RFC2047-encoded headers https://bugs.launchpad.net/bugs/266375 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 582911] [NEW] Umbrella flag should be per subscriber not per list
by Axel Beckert May 19, 2010

May 19, 2010

Public bug reported: Currently a list can be either an umbrella list or not, but a list which has normal and other lists as subscriber is currently not possible or an administrative problem. IMHO making the umbrella flag (as previously the moderated flag) per subscribe instead of per list, this would allow to make lists with mixed types of subscribers. This would probably also make the following helpful automatisms possible or at least easier: Mailman sould recognize mailing lists on the same server when they are subscribed to another list and set the umbrella flag for that subscriber automatically. Mailman should automatically add the umbrella list's aliases as well as non-members which are allowed to post to the appropriate fields of the subscriber-lists on the same server. I suspect at least 90% of all subscriber-lists are configured that way. ** Affects: mailman Importance: Undecided Status: New ** Tags: umbrella -- Umbrella flag should be per subscriber not per list https://bugs.launchpad.net/bugs/582911 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 1

[Bug 266821] Re: privacy hole in password reminder
by Mark Sapiro May 19, 2010

May 19, 2010

We know that plain text emailed passwords are a bad idea. This will be fixed in MM 3. For MM 2.1, as a list member, you can turn off the periodic reminder for any list of which you are a member. As a list owner, you can turn off all periodic reminders from your lists. As a site admin, you can turn off all periodic reminders from the site. That leaves only the "request an immediate reminder and intercept the email" attack as a vulnerability. The list subscribe form says: You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. *Do not use a valuable password* as it will occasionally be emailed back to you in cleartext. which implies that such a password, even if it is not an autogenerated one, is less likely to work in other contexts. ** Changed in: mailman Importance: Medium => High ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => mailman-2.2-3.0 -- privacy hole in password reminder https://bugs.launchpad.net/bugs/266821 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 266821] Re: privacy hole in password reminder
by Mats Ahlgren May 19, 2010

May 19, 2010

The following major security issues also exist: - If an email account is compromised, an attacker (or even an automated virus) can easily gather all passwords. This would *NOT* happen if no reminders were sent, nor would it happen if the classic "answer the security questions to receive a password reset form" strategy were used. - Additionally, once the attacker has the dozens of passwords one might use for various mailman lists, the attack can attempt to use those passwords on other websites or computer systems (e.g. SSH) in automated attacks. The most basic attack would merely use the password, but more sophisticated attacks can use the passwords as seeds in an automated cracker. > Mark Sapiro: "Are you aware of an attack that would enable this?" - As the original poster wrote: the password reminders are in plaintext. As far as I know, aren't all email messages sent in plaintext that thus absolutely trivial to eavesdrop on? All the attack would need is a compromised relay on the internet, which I hear is getting more common these days. Just run one of the many network-traffic-monitoring programs and listen for the string "password". -- privacy hole in password reminder https://bugs.launchpad.net/bugs/266821 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 581518] [NEW] list_members --fullnames kills umlauts in names
by Jakob Unterwurzacher May 17, 2010

May 17, 2010

Public bug reported: Running list_members --fullnames testlist should output this, as seen correctly in the web interface: Jürgen <...(a)gmx.de> Actually, it outputs: J?rgen <...(a)gmx.de> with the umlaut ü replaced by a question mark. ** Affects: mailman Importance: Undecided Status: New ** Description changed: Running - list_members --fullnames testlist + list_members --fullnames testlist should output this, as seen correctly in the web interface: - Jürgen <...(a)gmx.de> + Jürgen <...(a)gmx.de> Actually, it outputs: - J?rgen <...(a)gmx.de> - with the umlaut ü removed. + J?rgen <...(a)gmx.de> + with the umlaut ü replaced by a question mark. -- list_members --fullnames kills umlauts in names https://bugs.launchpad.net/bugs/581518 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 4