Mailman 3 January 2015 - Mailman-coders

[Bug 1414156] [NEW] Switch to $strings (i.e. `string.Template` instances) for all i18n substitutions
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: Switch to $strings (i.e. `string.Template` instances) for all i18n substitutions. We should be able to mechanically update all existing translations. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414156 Title: Switch to $strings (i.e. `string.Template` instances) for all i18n substitutions To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414156/+subscriptions

2 2

[Bug 1414155] [NEW] Language variants (e.g. en_UK)
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: Mailman should support language variants (e.g. en_UK). From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414155 Title: Language variants (e.g. en_UK) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414155/+subscriptions

2 2

[Bug 1414154] [NEW] switch to external translation system
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: Finish the transition to an externally managed translation system. This is necessary for the Mailman 3.0 release. Right now someone has to send new translations to Mark and he has to do a new release with new catalogs; see http://wiki.mailman.psf.io/DEV/Internationalization and http://wiki.mailman.psf.io/DEV/i18nhowto for more info. We have some notes at http://wiki.mailman.psf.io/DEV/Managing%20Translations about what we want in the future. It must be free software (this is why we cannot use Transifex). The workflow Barry would love: a developer can develop their software, marking all strings for localisation. Someone can take the trunk branch and run a tool to extract all the strings and provide Mailman developers with GNU gettext catalogs, or make them available in a branch, or on the web, so Mailman maintainers can check them out. There exists enough distributed machinery that we should be able to do this in a disconnected way. (From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series.) ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414154 Title: switch to external translation system To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414154/+subscriptions

5 6

[Bug 1414151] [NEW] Rosters should not be public by default
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: Rosters should not be public by default. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414151 Title: Rosters should not be public by default To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414151/+subscriptions

2 1

[Bug 1414149] [NEW] option to allow verified nonmembers to post to a list
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: Add an option to allow ''verified'' non-members to post to the list. A verified non-member is someone who posts to the list and responds in the affirmative to a confirmation message. A verified member can post in the future (think Gmane http://www.gmane.org ). From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. May be a duplicate of bug 558029. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414149 Title: option to allow verified nonmembers to post to a list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414149/+subscriptions

2 1

[Bug 1414147] [NEW] juggling for recipients in headers
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: Strip nodup recipients from both the `To` and `Cc` headers, and juggle recipient headers so that the list address is always in the `To` field. This might address the other major complaint against no-reply-to- munging, recipient proliferation. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414147 Title: juggling for recipients in headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414147/+subscriptions

2 1

[Bug 1414143] [NEW] Use subprocess module instead of things like os.popen()
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: In src/mailman/handlers/mime_delete.py we have: cmd = os.popen(config.HTML_TO_PLAIN_TEXT_COMMAND .... We should use the subprocess module instead http://www.python.org/doc/current/lib/module-subprocess.html in cases like this. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414143 Title: Use subprocess module instead of things like os.popen() To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414143/+subscriptions

2 1

[Bug 1414141] [NEW] Convert the last of the string exceptions in Errors.py to class exceptions
by Sumana Harihareswara 23 May '15

23 May '15

Public bug reported: From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414141 Title: Convert the last of the string exceptions in Errors.py to class exceptions To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414141/+subscriptions

2 1

[Bug 1351312] [NEW] Message acceptance options not working
by John Naggets 23 May '15

23 May '15

Public bug reported: I am testing the two following list config parameters: default_nonmember_action default_member_action and actually the following options do not work: Reject (with notification) and Discard (no notification) It looks like currently only the hold for moderator and accept options are working. Is it possible that these two are not ready yet in the beta4 version of mailman? Furthermore the approval mail to the moderator contains in its body as reason XXX: Reason: XXX I guess this also needs adapting. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1351312 Title: Message acceptance options not working To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1351312/+subscriptions

2 1

[Bug 1333902] [NEW] Mailman 3.0 goes awry when handling messages in an unexpected format
by NotTheEvilOne 23 May '15

23 May '15

Public bug reported: Hi, This bug report is little bit inaccurate. I had the following situation. I sent a message to Mailman 3 from mutt. I think that this message had no unixfrom header in "email.message.Message". The log file showed an exception thrown at "mailman/cure/runner.py". The exception "AttributeError: class MIMEMultipart has no attribute 'sender'" was caused because "_process_one_file()" of "runner.py" accesses "mailman.email.message.Message.sender" without any validation. The loaded, pickled file contained a "MIMEMultipart" object, the other one a "email.message.Message" as far as I can remember. I have attached a patch that ensures that "runner.py" is handling the expected Mailman "Message" instance but I think this was not the root of the problem. Hope it helps anyway. Best regards and keep up the good work on Mailman 3 ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Patch added: "Ensure runner.py handles a Mailman "Message" instance" https://bugs.launchpad.net/bugs/1333902/+attachment/4138396/+files/0003-mai… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1333902 Title: Mailman 3.0 goes awry when handling messages in an unexpected format To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1333902/+subscriptions

2 1