Mailman 3 March 2012 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[Bug 965532] [NEW] Need a script to upgrade from MM2 to MM3
by Barry Warsaw Dec. 14, 2021

Dec. 14, 2021

Public bug reported: We need a script, documentation, or other procedure to help people migrate from Mailman 2 to Mailman 3. ** 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/965532 Title: Need a script to upgrade from MM2 to MM3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965532/+subscriptions

8 21

[Bug 544477] [NEW] setting localhost in postfix_lmtp breaks delivery
by Patrick Ben Koetter Sept. 27, 2020

Sept. 27, 2020

Public bug reported: Setting localhost in postfix_lmtp works against Postfix defaults and breaks delivery. Reason: The Postfix lmtp client only uses dns queries by default to search for hostnames. If the DNS server does not provide an answer for "localhost" delivery from the lmtp client to mailman fails. Solution: Provide "127.0.0.1" instead of "localhost". This does not require DNS and is even faster because it saves DNS lookups. Example: hey2(a)mailman.state-of-mind.de lmtp:[localhost.localdomain]:8024 ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 7

[Bug 883193] [NEW] Remove the X- prefix from some headers
by Barry Warsaw Jan. 15, 2019

Jan. 15, 2019

Public bug reported: MM3 still uses a lot of X- headers, but some of the X- prefixes can be removed. In general, we can just claim the Mailman- prefix for Mailman specific headers. Candidates include: Mailman-Rule-Hits Mailman-Rule-Misses Mailman-Version Mailman-Approved-At Mailman-LMTP-MailFrom (i.e. X-MailFrom) Mailman-Copy (or remove this header) Mailman-Content-Filter (from X-Content-Filtered-By) Also, fix the outdated comments about add-dup-header in avoid_duplicates.py and verp.py. Probably also get rid of X-List-Administrivia (and possibly reduced_list_headers). These seem unnecessary now. ** 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/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions

3 6

[Bug 701558] [NEW] Content filtering leaves a single sub-part in a multipart message.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: If the original message is multipart but not multipart/alternative and content filtering removes all but one part, the message is left as a multipart message with only the one sub-part instead of being recast as just the sub-part. This can cause msg_header and/or msg_footer to be added as separate parts to a text/plain message instead of being added to the text/plain body part. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Description changed: - If the original message in multipart but not multipart/alternative and + If the original message is multipart but not multipart/alternative and content filtering removes all but one part, the message is left as a multipart message with only the one sub-part instead of being recast as just the sub-part. This can cause msg_header and/or msg_footer to be added as separate - parts to a text/plain message instead if being added to the text/plain + parts to a text/plain message instead of being added to the text/plain body part. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/701558 Title: Content filtering leaves a single sub-part in a multipart message.

3 7

[Bug 576675] [NEW] Content filtering fails to collapse alternatives.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: Collapsing multipart/alternative parts to just the first alternative only works if the message itself is multipart/alternative, or the multipart/alternative part is at the first sub-level. For example, given this structure: multipart/mixed | multipart/related | | multipart/alternative | | | text/plain | | | text/html | | image/jpeg | application/msword The multipart/alternative part will not be collapsed. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- Content filtering fails to collapse alternatives. https://bugs.launchpad.net/bugs/576675 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 7

[Bug 757062] [NEW] Content filtering can remove the headers from a message/rfc822 part.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: If Content filtering accepts both message/rfc822 and multipart/alternative MIME parts, and a message/rfc822 part contains a message whose content type is multipart/alternative and collapse_alternatives is Yes, the headers of the message in the message/rfc822 part will be lost. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress ** 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/757062 Title: Content filtering can remove the headers from a message/rfc822 part.

3 12

[Bug 775294] [NEW] Set lifetime for input forms
by Tokio Kikuchi Sept. 5, 2016

Sept. 5, 2016

*** This bug is a security vulnerability *** Private security bug reported: We may have to set lifetime for input forms because of recent activities on cross-site request forgery (CSRF). The form lifetime is successfully deployed in frameworks like web.py or plone etc. Proposed branch lp:~tkikuchi/mailman/form-lifetime implement lifetime in admin, admindb, options and edithtml interfaces. Other forms like create and rmlist have confirmation by password thus are safe regarding CSRF. The form generation time is set by a hidden parameter whose value is calculated following the mailman cookie algorithm. The default lifetime is set 1 hour in Default.py thus configurable by a site administrator. If a password is set in request, authorization cookie is discarded so the password authentication is forced. Wget tricks to manage list in FAQ can be used as they are now. ** Affects: mailman Importance: Undecided Status: New ** Branch linked: lp:~tkikuchi/mailman/form-lifetime -- You received this bug notification because you are a member of Mailman Coders, which is a direct subscriber. https://bugs.launchpad.net/bugs/775294 Title: Set lifetime for input forms

2 5

[Bug 889829] [NEW] setup takes zope interface 3.5.1, but needs 3.8.0
by Harry Enke July 31, 2015

July 31, 2015

Public bug reported: separate installation of zope interface 3.8.0 fixes the issue, afterwards mailman 3.0.0.8a OS: Scientific Linux 6.1, Python 2.6.6 ** 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/889829 Title: setup takes zope interface 3.5.1, but needs 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889829/+subscriptions

3 7

[Bug 856004] [NEW] "OperationalError: database is locked" encountered under very light load while using REST API
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: I've seen this error twice while running integration tests (of our own application) that access Mailman 3 using the API. The load on Mailman is very light, as all requests made to the API are serial, never in parallel. Of course the various processing queues in MM3 are separate processes and could be doing work concurrently. The platform is Centos 6. Traceback (most recent call last): File "/usr/lib64/python2.6/wsgiref/handlers.py", line 93, in run self.result = application(self.environ, self.start_response) File "/home/sgoss/mailman_clone/src/mailman/rest/wsgiapp.py", line 63, in __call__ config.db.commit() File "/home/sgoss/mailman_clone/src/mailman/database/stock.py", line 70, in commit self.store.commit() File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/store.py", line 122, in commit self._connection.commit() File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 126, in commit self.raw_execute("COMMIT", _end=True) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/database.py", line 321, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/database.py", line 366, in _check_disconnect return function(*args, **kwargs) OperationalError: database is locked The backend here is SQLite, which falls over very quickly under concurrent load. If the goal here is to create a stable mailing list server, maybe SQLite is a poor default. ** 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/856004 Title: "OperationalError: database is locked" encountered under very light load while using REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/856004/+subscriptions

3 8

[Bug 827547] [NEW] KeyError in "virgin" runner.
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: Not sure what caused this error that showed up in mailman.log: Aug 16 10:54:50 2011 (31400) Uncaught runner exception: u'foo.example.com' Aug 16 10:54:50 2011 (31400) Traceback (most recent call last): File "/home/sgoss/mailman_clone/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/runners/virgin.py", line 37, in _dispose process(mlist, msg, msgdata, 'virgin') File "/home/sgoss/mailman_clone/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/pipeline/cook_headers.py", line 360, in process process(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/pipeline/cook_headers.py", line 202, in process listinfo = mlist.script_url('listinfo') File "/home/sgoss/mailman_clone/src/mailman/model/mailinglist.py", line 243, in script_url return urljoin(self.domain.base_url, target + '/' + self.fqdn_listname) File "/home/sgoss/mailman_clone/src/mailman/model/mailinglist.py", line 227, in domain return getUtility(IDomainManager)[self.mail_host] File "/home/sgoss/mailman_clone/src/mailman/model/domain.py", line 142, in __getitem__ raise KeyError(email_host) KeyError: u'foo.example.com' ** 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/827547 Title: KeyError in "virgin" runner. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/827547/+subscriptions

3 8

[Bug 956384] [NEW] Continuous integration and real-world testing
by Andrea Crotti May 23, 2015

May 23, 2015

Public bug reported: This is not a real bug, I would just like to start a discussion about what can be done to set up a continuos integration system. Is there any Jenkins server which can be used? Another thing which I was thinking is if we have some real tests on real systems with various MTA such as Postfix/Exim. I haven't tried it yet but it seems that http://vagrantup.com/ and puppet could really be very nice tools for the job. And we could then 1. fire up a VM 2. install the different MTAs 3. create some complicated mailing lists and check that everything works correctly Other ideas? ** 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/956384 Title: Continuous integration and real-world testing To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/956384/+subscriptions

3 4

[Bug 967954] [NEW] IMessageStore should be exposed as a top level REST resource
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: At the simplest, it should support GET on a Message-ID or X-Message-ID- Hash value and return the bytes of the stored message, or 404. ** 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/967954 Title: IMessageStore should be exposed as a top level REST resource To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967954/+subscriptions

2 3

[Bug 953531] [NEW] Add graphs of the overall architecture
by Andrea Crotti May 23, 2015

May 23, 2015

Public bug reported: Adding to the documentation some graphs in graphviz format. ** 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/953531 Title: Add graphs of the overall architecture To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953531/+subscriptions

4 5

[Bug 937154] [NEW] bin/disabled.py is nonfunctional
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: The bin/disabled.py script needs tests, documentation, and fixing in Mailman 2. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Tags: mailman3 ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Milestone: None => 3.0.0b1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/937154 Title: bin/disabled.py is nonfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/937154/+subscriptions

4 8

[Bug 889635] [NEW] Per-list configurable message headers for digests
by Joseph Fall May 23, 2015

May 23, 2015

Public bug reported: Digest messages are sent out with a partial set of headers for each message. The list of headers kept for each plain-text digested message is configured by the setting: PLAIN_DIGEST_KEEP_HEADERS = [ 'Message', 'Date', 'From', 'Subject', 'To', 'Cc', 'Message-ID', 'Keywords', 'Content-Type', ] My users are very perplexed and frustrated by the e-mail headers included in the digest - in particular, the Message-ID and Content-Type are meaningless, and the To header is repetitive. All this "noise" clutters up the content and makes the digest harder to read. Given that this is a plain-text digest, with the headers listed in the message body, I don't really see an RFC issue here? Yet they can only be configured using a list-wide override in mm_cfg.py I would be willing to work on this to allow a list admin to override the plain digest headers using the web interface, but want to hear from the development team if this is a patch they would be willing to consider before I invest the time. thanks. ** 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/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions

4 7

[Bug 885715] [NEW] Mailman should add a Received header
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: When the LMTP runner or any other injection vector receives a message, it should add a Received header to indicate the time at which Mailman got the message. Use case: there is a spam filter between the incoming MTA and Mailman, and the message sits in the spam filter for a while before its administrator accepts the message. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: 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/885715 Title: Mailman should add a Received header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/885715/+subscriptions

2 3

[Bug 869347] [NEW] bin/test script fails unless zope.testrunner is pip installed
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: I am running Mailman 3 in a virtualenv with most of its package dependencies installed through pip. In this particular configuration, if I run `buildout`, the test script that is created cannot seem to load zope.testrunner properly: $ bin/test -vv Traceback (most recent call last): File "bin/test", line 35, in <module> import zope.testrunner ImportError: No module named testrunner The workaround is to remove the eggs folder, pip install zope.testrunner, and then re-run buildout. ** 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/869347 Title: bin/test script fails unless zope.testrunner is pip installed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions

3 3

[Bug 837700] [NEW] Issues with users subscribed via their preferred address
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: You can subscribe an address to a mailing list, and you can subscribe a user to a mailing list, if the user has a preferred address. There are two problems with this. * You can actually end up getting doubly subscribed (i.e. same address with the same role). Normally, the subscription mechanism prevents you from subscribing the same address with the same role more than once, or the same user with the same role more than once. However, if you subscribe once by the address, and once by the user whose preferred address is that same address, the double subscription occurs. * The Member repr() doesn't distinguish between a member that's subscribed via explicit address, and one that's subscribed via preferred address. This means that the above will appear as a double address subscription, when it's really not. Are these substantial problems that need to be fixed? Almost certainly the second one does, but I haven't come up with an elegant repr() for the case of a user subscribed with their preferred address. ** Affects: mailman Importance: Low Status: Confirmed ** 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/837700 Title: Issues with users subscribed via their preferred address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/837700/+subscriptions

2 2

[Bug 793669] [NEW] feature request. change the 'list my other subscriptions' to also report if the other subscriptions are enabled or disabled
by Laura Creighton May 23, 2015

May 23, 2015

Public bug reported: I have a large number of subscriptions to mailing lists on python.org. Delivery is disabled on most of them. This is exactly how I want it -- I don't want to keep up with the day to day matters of the list, but I do want to be able to re-anable delivery and discuss things there should the need arise without having to create a new account. However, when I go on vacation, what I want to do is also disable a few high volume lists that I normally want to read every day. Thus what I would really like to see is which lists are currently enabled, so I can decide which one(s) if any I want to disable for the vacation. I don't want to disable the low-volume ones. Given that I am going to have to re-enable the lists I want to read when I get back one by one, I want the number of lists that get temporarily disabled to be as small as possible. And I want to be able to email me the short list of what they were so I can remember which ones to turn on again. Interestingly, the text of the message indicates a usability misunderstanding, and a grammatical error. The text reads: You can view a list of all the other mailing lists at python.org for which you are a member. Use this if you want to make the same membership option changes to this other subscriptions. It should be 'these other subscriptions'. And the people who want to make the same membership option changes to all the lists they are subscribed to on a site are precisely the users who don't need the feature. They can blindly go off and change things globally. If the number of lists they are subscribed to on that site is 1 -- i.e. they do not have any other subscriptions -- then saying to do things globally will do no harm. The reason you might want to look is to check because you might _not_ want to do things globally. And once you are dealing with that case, things you do not want to do globally, then of course you want to see the current settings that you have. But for my use case, all I care about is changing delivery status. All the other options I either never change, or want to change globally. I suspect that most people use mailing lists in this way, where the only thing they need to worry about is changes due to vacation, but I haven't conducted any polls to test this theory. This request sent to the tracker because the automated mail I recevied when some moderator refused to accept my mail to mailman-dev with this feature request, with the message 'why don't you just disable delivery globally and then reset them globally when you return' said that this was the place for feature requests and not the mailing list. Hope this request is clearer and explains why globally disabling is not what I want to do. Thank you ** 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/793669 Title: feature request. change the 'list my other subscriptions' to also report if the other subscriptions are enabled or disabled

4 9

[Bug 707295] [NEW] Membership Management Better Search Function
by arky May 23, 2015

May 23, 2015

Public bug reported: In Mailman Membership Management, I would like to option to filter search results by status viz (hide,nomail [reason], ack, not metoo, nodupes, digest, plain) ** 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/707295 Title: Membership Management Better Search Function

4 3

[Bug 514625] [NEW] Mailman 3 member functions should "guess" address membership
by Stephen Turnbull May 23, 2015

May 23, 2015

Public bug reported: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.domain.tld" is subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." ** Affects: mailman Importance: Undecided Status: New ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and - address>. [ ] Add <unknown> address as an alias for <member>." + address>. [ ] Add <unknown address> as an alias for <member>." ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against - the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is - subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same + the member database. For example, if "turnbull(a)sk.domain.tld" is + subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." -- Mailman 3 member functions should "guess" address membership https://bugs.launchpad.net/bugs/514625 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 5

[Bug 881320] [NEW] Mailman 3 translations
by Vincent Fretin May 23, 2015

May 23, 2015

Public bug reported: In mailman 3.0.0a8, the locales directory contains actually mailman 2 translations. The unsubscribe mail is not translated into French because the msgids are different between mailman2 and mailman3. Do you have a script to generate a pot file and sync the po files? I had to generate myself the French mo file from the po. It's maybe a good idea to include mo files in the sdist, or generate mo files at mailman startup. ** 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/881320 Title: Mailman 3 translations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881320/+subscriptions

4 5

[Bug 965520] [NEW] Improve installation documentation
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: This page: http://packages.python.org/mailman/src/mailman/docs/START.html describes how to install, configure, and start Mailman 3. It's a bit sparse and out-of-date. For example, it doesn't describe all the locations that mailman.cfg is search for. It also doesn't describe installing and running mm3 in a virtualenv. This would make a nice bite-sized bug for someone wanting to contribution to Mailman. ** Affects: mailman Importance: Undecided Status: New ** Tags: documentation easy mailman3 ** Tags removed: bite-size ** Tags added: easy -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/965520 Title: Improve installation documentation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965520/+subscriptions

6 12

[Bug 881316] [NEW] RuntimeError: maximum recursion depth exceeded while pickling an object
by Vincent Fretin May 23, 2015

May 23, 2015

Public bug reported: With mailman 3.0.0a8. I got the following traceback from a html mail with html signature+image from Outlook, Oct 14 09:21:31 2011 (17579) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/chains/hold.py", line 245, in _process nmsg.send(mlist, **dict(tomoderators=True)) File "/home/zope/mailman/src/mailman/email/message.py", line 198, in send self._enqueue(mlist, **_kws) File "/home/zope/mailman/src/mailman/email/message.py", line 216, in _enqueue virginq.enqueue(self, **str_keywords) File "/home/zope/mailman/src/mailman/core/switchboard.py", line 133, in enqueue msgsave = cPickle.dumps(_msg, protocol) RuntimeError: maximum recursion depth exceeded while pickling an object It's really an obscure issue for me. I resolved it by adding sys.setrecursionlimit(10000) in src/mailman/core/switchboard.py before msgsave = cPickle.dumps(_msg, protocol) line 134 and doing bin/mailman unshunt fixed the issue. By default sys.getrecursionlimit() returns 1000. If you want to have a test email to reproduce, I can ask my customer to send an email to a test mailing-list. ** 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/881316 Title: RuntimeError: maximum recursion depth exceeded while pickling an object To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881316/+subscriptions

4 6

[Bug 881312] [NEW] Properly decode payload
by Vincent Fretin May 23, 2015

May 23, 2015

Public bug reported: With mailman 3.0.0a8 in src/mailman/runners/command.py, there is an issue with body = part.get_payload(decode=True) if you send a mail to test-unsubscribe(a)example.com, with accents in the mail, in the signature for example, you get a body string encoded in iso-8859-1. When you try to concatenate iso-8859-1 string with unicode, this the case when the mail body with "Unprocessed:" and "Ignored:" is generated, you get a UnicodeDecodeError ascii. The code should be modified to correctly decode the mail body like it is done in src/mailman/pipeline/decorate.py mcset = msg.get_content_charset() or 'us-ascii' unicode(msg.get_payload(decode=True), mcset) There are similar issues in src/mailman/rules/administrivia.py with the line: if line == '': where it give you a warning because it compare an iso to an empty unicode. and in src/mailman/rules/approved.py where it simply crashes: Oct 18 17:54:41 2011 (18207) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 65, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/zope/mailman/src/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position 14: invalid continuation byte Currently, mailman is unusable for another language than English, like French. ** 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/881312 Title: Properly decode payload To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881312/+subscriptions

4 6

[Bug 826861] [NEW] doctests failing on Centos 6 due to "unprintable" error objects
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: On Centos 6 (64 bit), the following tests fail due to what looks like some kind of Python object printing quirk with the version that ships with RHEL 6 and derivatives: src/mailman/model/docs/membership.txt src/mailman/model/docs/users.txt The errors all look like this: File "/home/sgoss/mailman_clone/src/mailman/model/docs/membership.txt", line 296, in membership.txt Failed example: gwen_member.address = new_address Differences (ndiff with -expected +actual): Traceback (most recent call last): - ... - UnverifiedAddressError: gperson(a)example.com + File "/usr/lib64/python2.6/doctest.py", line 1248, in __run + compileflags, 1) in test.globs + File "<doctest membership.txt[68]>", line 1, in <module> + gwen_member.address = new_address + File "/home/sgoss/mailman_clone/src/mailman/model/member.py", line 116, in address + raise UnverifiedAddressError(new_address) + UnverifiedAddressError: <unprintable UnverifiedAddressError object> The system reports Python version 2.6.5. This error does not seem to occur with Python 2.7 on Ubuntu 11.04. One possibility is that for some reason when it comes to printing out those error objects, Python doesn't have a default encoding scheme for representing the embedded unicode strings in that particular context (email address in the above example). ** 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/826861 Title: doctests failing on Centos 6 due to "unprintable" error objects To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/826861/+subscriptions

3 7

[Bug 543618] [NEW] test breaks if existing mailman.cfg is found
by Patrick Ben Koetter March 24, 2015

March 24, 2015

Public bug reported: The test program reports an error if it detects an existing mailman.cfg: Failure in test test_current_working_directory (mailman.tests.test_configfile.TestConfigFileSearch) Traceback (most recent call last): File "/usr/lib/python2.6/unittest.py", line 279, in run testMethod() File "/root/mailman/src/mailman/tests/test_configfile.py", line 107, in test_current_working_directory self.assertEqual(found, config_file) File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: '/etc/mailman.cfg' != u'/tmp/tmpVfAIyB/home/alex/mailman/hacking/mailman.cfg' I believe it should not do this. It should either silently ignore the difference or use the test mailman.cfg or ... but not break. ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 967951] [NEW] The LMTP runner should reject messages with duplicate Message-IDs
by Barry Warsaw March 6, 2015

March 6, 2015

Public bug reported: Subject says it all. Mailman 3 requires unique Message-IDs for posts. ** Affects: mailman Importance: Undecided Status: New ** Tags: easy 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/967951 Title: The LMTP runner should reject messages with duplicate Message-IDs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967951/+subscriptions

6 8

[Bug 880613] [NEW] PostgreSQL constraints disabled
by Barry Warsaw Nov. 29, 2014

Nov. 29, 2014

Public bug reported: In src/mailman/database/sql/postgres.sql, several foreign key constraints have been commented out because otherwise the test suite, or other aspects do not work. This is probably because there are cases where Mailman violates these constraints, but SQLite3 (the default database) does not care. All disabled constraints are marked with XXX in the above file. Really, these should be fixed. ** Affects: mailman Importance: Medium Status: Confirmed ** 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/880613 Title: PostgreSQL constraints disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880613/+subscriptions

1 2

[Bug 518517] [NEW] Add the equivalent of postconf(1)
by Barry Warsaw April 22, 2014

April 22, 2014

Public bug reported: Postfix has a very handy command called postconf(1) which lets you dump all or one Postfix configuration variable. It would be very handy for Mailman 3 to have something similar. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Also affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

5 19

[Bug 869342] [NEW] bootstrap.py fails if buildout already installed in Python environment
by Stephen A. Goss April 15, 2014

April 15, 2014

Public bug reported: If zc.buildout is already installed (say it was pip installed) in Python environment, the bootstrap.py script fails without reasonable explanation: $ python bootstrap.py Traceback (most recent call last): File "bootstrap.py", line 255, in <module> import zc.buildout.buildout ImportError: No module named zc.buildout.buildout This is confusing because you can see that zc.buildout.buildout is available. $ python Python 2.6.5 (r265:79063, Jun 25 2011, 08:36:25) [GCC 4.4.4 20100726 (Red Hat 4.4.4-13)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import zc.buildout.buildout >>> It turns out that if zc.buildout is already available, bootstrap.py does not need to be run, but that is less than obvious to someone who is not intimately familiar with buildout. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: 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/869342 Title: bootstrap.py fails if buildout already installed in Python environment To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869342/+subscriptions

2 2

[Bug 821438] [NEW] REST and Client are missing membership_settings options
by benste March 15, 2014

March 15, 2014

Public bug reported: Using the Python bindings the following things are available at the moment: self_link: u'http://localhost:8001/3.0/members/2' role: u'member' user: u'http://localhost:8001/3.0/users/2' address': u'katie(a)example.com' fqdn_listname': u'testtwo(a)mail.example.com' For better user management the following options should be seen as wishlist: acknowledge_posts hide_address receive_list_copy receive_own_postings delivery_mode delivery_status in addition i requested _User.get_lists which is in https://bugs.launchpad.net/mailmanwebgsoc2011/+bug/821069 + what about users password ? users e-mails ... ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman.client Importance: Undecided Status: Confirmed ** Affects: mailmanwebgsoc2011 Importance: Wishlist Status: Triaged ** Tags: mailman3 ** Changed in: mailman.client Status: New => Confirmed ** Also affects: mailmanwebgsoc2011 Importance: Undecided Status: New ** Also affects: mailman Importance: Undecided Status: New ** Tags added: mailman3 ** Changed in: mailmanwebgsoc2011 Status: New => Triaged ** Changed in: mailmanwebgsoc2011 Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/821438 Title: REST and Client are missing membership_settings options To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/821438/+subscriptions

3 6

[Bug 802971] [NEW] Mailman Client doesn't _DOMAIN doesn't offer a list of lists
by benste March 15, 2014

March 15, 2014

Public bug reported: I'd suggest adding a functionalty which would need a domain as param, and return a list of mailing lists associated with this domain. This could be used to display a choice of all available domains on this web_host and allow simple deletition of all mailinglists on this domains in case a domain will ever be deleted. ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman.client Importance: Undecided Status: New ** Affects: mailmanwebgsoc2011 Importance: Wishlist Assignee: benste (benste) Status: Triaged ** Tags: mailman3 ** Also affects: mailman.client Importance: Undecided Status: New ** Also affects: mailman Importance: Undecided Status: New ** Tags added: 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/802971 Title: Mailman Client doesn't _DOMAIN doesn't offer a list of lists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions

5 9

[Bug 674352] [NEW] List Moderator Login should check for username
by arky March 12, 2014

March 12, 2014

Public bug reported: List Moderator logins currently prompt for list moderator password only. It would be good idea if prompt for username/password login as well. Mailman: 2.1.9 ** Affects: mailman Importance: Undecided Status: New -- List Moderator Login should check for username https://bugs.launchpad.net/bugs/674352 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 3

[Bug 725498] [NEW] expose message-id to templates
by Thijs Kinkhorst Aug. 5, 2013

Aug. 5, 2013

Public bug reported: As reported by Adrian von Bidder to Debian: Please consider this trivial patch, which exposees message-ids to the templates used for the email archive. See it in action on lists.debian.ch. (I don't think my modification to the templates should be in, but having te message-id exposed would mean I won't have to remember to patch mailman on every update...) (AFAICT mailman adds a Message-Id when an incoming email doesn't have one, so this should never be a problem.) ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/725498 Title: expose message-id to templates

4 7

[Bug 693134] [NEW] Uncaught bounce from Dovecot when Quota Exceeded
by JorSol June 20, 2013

June 20, 2013

Public bug reported: I have a Debian 5 (Lenny) server with Postfix - Dovecot and Mailman 2.1.11 and 1700+ users. The problem is when Dovecot returns the bounce message about "Quota exceeded", Mailman don't recognize the format: Your message to <user(a)domain.com> was automatically rejected: Quota exceeded It's suposed that Mailman recognize this type of message using the VERP feature, I have "recipient_delimiter = +" in Postfix but Mailman don't detect message coming from Dovecot. /var/log/mailman/bounce: Dec 21 10:58:08 2010 (3214) listnews: bounce message w/no discernable addresses: <dovecot-1292944464-47721-0@mail> Dec 21 10:58:08 2010 (3214) noticias: forwarding unrecognized, message-id: <dovecot-1292944464-47721-0@mail> ** Affects: mailman Importance: Undecided Status: New ** Tags: dovecot mailman postfix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded

4 13

[Bug 886296] [NEW] Improve DSN handling for google 'inactive' accounts
by Kevin Fenzi May 30, 2013

May 30, 2013

Public bug reported: The DSN bouncer handler can't seem to parse out when a bounce is generated due to an inactive google account. See attached bounce file for example. ** 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/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions

3 8

[Bug 949924] [NEW] UnicodeDecodeError when delivering message
by Antti Kaihola Sept. 8, 2012

Sept. 8, 2012

Public bug reported: I did a fresh install of Mailman 3.0.0a8 on a Debian Squeeze box, created a list, subscribed a few people and sent a message to the list. The message didn't come through, and var/logs/mailman.log has: Mar 08 13:21:08 2012 (23645) Uncaught runner exception: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) Traceback (most recent call last): File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/mailman/lib/python2.6/site-packages/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/mailman/lib/python2.6/site-packages/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) SHUNTING: 1331212867.805197+9daec32c73ac20978b856348ada1a60fd97a364c The message did contain an u'\xe4' in both the subject and the body. I sent the message using Thunderbird 10.0.2 on Linux Mint 12. ** 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/949924 Title: UnicodeDecodeError when delivering message To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/949924/+subscriptions

5 11

[Bug 967238] [NEW] Expose IMailingList.archive and .archive_private in the REST API
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: Exposing read and write of these attributes would allow Postorius to provide the list owners with some control over archiving for individual lists. This would work as a patch to src/mailman/rest/configuration.py and should be pretty easy to add. ** Affects: mailman Importance: Medium Status: Triaged ** Tags: easy 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/967238 Title: Expose IMailingList.archive and .archive_private in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967238/+subscriptions

2 6

[Bug 953497] [NEW] Unused variable in loop
by Andrea Crotti Sept. 8, 2012

Sept. 8, 2012

Public bug reported: in mailman/src/mailman/config/config.py the property header_matches for match in matches: yield (matches.header, matches.pattern, matches.chain) has a probable typo in the loop, and the variablel looping over is not used. ** 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/953497 Title: Unused variable in loop To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953497/+subscriptions

2 5

[Bug 963612] [NEW] ArchiveRunner has Pipermail artifacts
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: When the original message has a Date header, ArchiveRunner._dispose() will check to see if the date should be trusted or clobbered. This code still references the out of date [archiver.pipermail]clobber_date_policy value. The config var needs to be moved or renamed and the functionality re-implemented (and tested!). For now, I'm going to disable this bit of code but it should be re-addressed for beta2. ** Affects: mailman Importance: Medium Status: Confirmed ** 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/963612 Title: ArchiveRunner has Pipermail artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/963612/+subscriptions

1 2

[Bug 967409] [NEW] NewsRunner needs to be ported to Mailman 3
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: In src/mailman/runners/news.py, prepare_message() is ported to mm3 and tested, however ArchiveRunner is not. We also need some unittests, and this probably means that we'll pull in mock as a test dependency. It beats requiring a real NNTP server. ** Affects: mailman Importance: Undecided Status: Triaged ** 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/967409 Title: NewsRunner needs to be ported to Mailman 3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967409/+subscriptions

1 3

[Bug 887610] [NEW] RFC 1153 digests should not work around VM bug
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: In RFC1153Digester.finish(), we have this comment: # This is not strictly conformant RFC 1153. The trailer is only # supposed to contain two lines, i.e. the "End of ... Digest" line # and the row of asterisks. If this screws up MUAs, the solution # is to add the footer as the last message in the RFC 1153 digest. # I just hate the way that VM does that and I think it's confusing # to users, so don't do it unless there's a clamor. It is bogus that Mailman works around VM this way, so the code should be fixed to fully conform to RFC 1153. While this bug report is specifically targeted to Mailman 3, it also affects MM2.1, but I'll let Mark decide the priority of that bugtask. ** Affects: mailman Importance: Medium Status: Triaged ** 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/887610 Title: RFC 1153 digests should not work around VM bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/887610/+subscriptions

3 8

[Bug 899344] [NEW] Ability to set nomail on initial subscription
by Josh Triplett Sept. 4, 2012

Sept. 4, 2012

Public bug reported: I frequently find myself subscribing to a list for the sole purpose of ensuring I can post to that list, since it only allows posting from members. I often read those (high-volume) lists via the archives only, as well as threads that CC me. Thus, I want to set the nomail flag. Often I end up doing so for multiple subscriptions to the same list with a few different email addresses. Currently, the process for doing that looks something like this: Type in my name and email address, hit subscribe, wait for confirmation mail, confirm subscription, wait for subscription confirmation mail, go back to web form, copy/paste password, log in, check nomail, delete the handful of unwanted emails that arrived in the meantime. Repeat for every list I want to subscribe to, and every email address I want to post from. I'd like to have a way to set the "nomail" flag right from the subscription form. That would simplify the process significantly; I'd still have to confirm the subscription, but I wouldn't need to bother logging in and setting the flag, and I wouldn't receive unwanted emails from high-volume lists. ** 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/899344 Title: Ability to set nomail on initial subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/899344/+subscriptions

2 2

[Bug 736849] [NEW] Sender header change to improve Outlook
by Joseph Brennan Aug. 31, 2012

Aug. 31, 2012

Public bug reported: FAQ 2.3 describes problems with Outlook's ugly display of Sender "on behalf of" From, giving the example as "From listname- bounces(a)mailman.server.com On behalf of fred(a)poster.domain.com". But Outlook prefers to show the real name and hide the Internet address, when a real name is present. Most commonly the From would be "From: Fred Example <fred(a)poster.domain.com>" and as a result Outlook would display "From listname-bounces(a)mailman.server.com On behalf of Fred Example". If Mailman wrote the Sender header with a real name Outlook would show the name there too. For example, if the list name (local part) were inserted, thus "Sender: listname <listname-bounces(a)mailman.server.com>", then Outlook would display "From listname on behalf of Fred Example" which is much better in appearance and still complies with using a Sender header. RFC 2822 allows Sender to contain a real name. sender = "Sender:" mailbox CRLF mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr ** 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/736849 Title: Sender header change to improve Outlook

3 7

[Bug 815444] [NEW] typo in german invite.txt 'einzutragenn'
by Thijs Kinkhorst June 16, 2012

June 16, 2012

Public bug reported: There is a misspelled word in the german translation file of the invitation text. Fix: sed -i 's/einzutragenn/einzutragen/' /usr/share/mailman/de/invite.txt ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #627429 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627429 ** Also affects: mailman (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627429 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/815444 Title: typo in german invite.txt 'einzutragenn' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/815444/+subscriptions

3 4

[Bug 500955] [NEW] Templates for AST use inconsistent DOCTYPE
by Matt Selsky June 15, 2012

June 15, 2012

Public bug reported: Most of the templates use a DOCTYPE of HTML 4.01 Transitional, but the AST templates use HTML 3.2. The patch updates the DOCTYPES for the AST templates. ** Affects: mailman Importance: Undecided Status: New -- Templates for AST use inconsistent DOCTYPE https://bugs.launchpad.net/bugs/500955 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 500952] [NEW] Extra escape characters in DOCTYPE
by Matt Selsky June 15, 2012

June 15, 2012

Public bug reported: The DOCTYPE header for 2 files in the sk templates contain extra escape characters around the quote marks. ** Affects: mailman Importance: Undecided Status: New -- Extra escape characters in DOCTYPE https://bugs.launchpad.net/bugs/500952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 770581] [NEW] The list admin or moderator password can be compromised by sending in an Approved: header
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If posting to a list is secured by requiring an Approved: or X-Approved: header for a post to be accepted without moderation, the list admin or moderator password can be compromised by sending it in the headers of an email message. There should be a 'poster' password for this purpose only so the consequences of compromise would be less severe. ** Affects: mailman Importance: Wishlist 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/770581 Title: The list admin or moderator password can be compromised by sending in an Approved: header

1 2

[Bug 637652] [NEW] mailman should respect LDFLAGS
by Hanno Böck June 15, 2012

June 15, 2012

Public bug reported: mailman Makefile should respect the LDFLAGS variable. See attached patch. ** Affects: mailman Importance: Undecided Status: New -- mailman should respect LDFLAGS https://bugs.launchpad.net/bugs/637652 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 966565] [NEW] Web UI crashes on list with 'removed' language.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If a list's preferred_language or depending on context a user's language selection has been removed from the LC_DESCRIPTIONS table, the web UI can crash. ** 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/966565 Title: Web UI crashes on list with 'removed' language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/966565/+subscriptions

2 6

[Bug 964190] [NEW] Trailing slash is stripped from List-Archive: URL
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: In creating the List-Archive: header, CookHeaders.py strips a trailing slash from the URL returned by mlist.GetBaseArchiveURL(). It has always (in 2.1) done this, but it is wrong. Consider a list's archive TOC page which has entries like the following: <tr> <td>March 2012:</td> <td> <A href="2012-March/thread.html">[ Thread ]</a> <A href="2012-March/subject.html">[ Subject ]</a> <A href="2012-March/author.html">[ Author ]</a> <A href="2012-March/date.html">[ Date ]</a> </td> <td><A href="2012-March.txt">[ Text 766 KB ]</a></td> </tr> If the base archive URL is http://www.example.com/private/listname/ and one goes to that URL, the relative hrefs all work fine, but if one goes to http://www.example.com/private/listname instead, those relative hrefs become relative to private/ instead of private/listname/, and one gets 'no such list: 2012-march' errors (or 404 errors in the case of public 'pipermail' URLs). ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) 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/964190 Title: Trailing slash is stripped from List-Archive: URL To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/964190/+subscriptions

2 3

[Bug 919479] [NEW] incorrect example in List Administration Manual 2.1
by Chip Davis June 15, 2012

June 15, 2012

Public bug reported: In the "GNU Mailman - List Administration Manual Release 2.1", under: 2 The List Configuration Pages + 2.1 The General Options Category + 2.1.1 General list personality + real_name "The real name can differ from the posting name by case only. For example, if the posting name is mylist, the real name can be Posting." Suggest: The real name can differ from the posting name by case only. For example, if the posting name is mylist, the real name can be MyList. ** Affects: mailman Importance: Undecided Status: New ** Tags: doc -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/919479 Title: incorrect example in List Administration Manual 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/919479/+subscriptions

4 7

[Bug 901957] [NEW] Mailman.Mailbox.Mailbox.AppendMessage method can add null bytes to mailbox.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The Mailman.Mailbox.Mailbox.AppendMessage method has an invalid seek to position the file to the end of the mailbox. It contains . # Seek to the last char of the mailbox . self.fp.seek(1, 2) This actually should be self.fp.seek(0, 2). There is no actual ill effect in Mailman itself from this bug as Mailman always opens mailbox files to be written to in 'a+' mode and seeks before writes are ignored for files opened in append mode, but if someone creates a process which opens a file in 'w+' mode and then uses the Mailman.Mailbox.Mailbox.AppendMessage method to add messages to it, each added message's UnixFrom is preceded by a null byte. ** Affects: mailman Importance: Low 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/901957 Title: Mailman.Mailbox.Mailbox.AppendMessage method can add null bytes to mailbox. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/901957/+subscriptions

1 2

[Bug 897103] [NEW] Crash when moderating messages with empty sender address
by Bernd Wurst June 15, 2012

June 15, 2012

Public bug reported: A message in the moderation queue has had an empty sender address ("From: foobar <>"). This leads to the folowing traceback: admin(9230): [----- Mailman Version: 2.1.14 -----] admin(9230): [----- Traceback ------] admin(9230): Traceback (most recent call last): admin(9230): File "/home/.internal/mailman/scripts/driver", line 112, in run_main admin(9230): main() admin(9230): File "/home/.internal/mailman/Mailman/Cgi/admindb.py", line 167, in main admin(9230): process_form(mlist, doc, cgidata) admin(9230): File "/home/.internal/mailman/Mailman/Cgi/admindb.py", line 718, in process_form admin(9230): if id not in senderactions[sender]['message_ids']: admin(9230): KeyError: 'message_ids' ** 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/897103 Title: Crash when moderating messages with empty sender address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/897103/+subscriptions

2 2

[Bug 893290] [NEW] "Re:" matching not liberal enough
by Ignacy Gawędzki June 15, 2012

June 15, 2012

Public bug reported: In Handlers/CookHeaders.py, the regex to match a "Re" line is not liberal enough. French MUAs often use a "Re :" tag, with a space before the colon. I suggest that instead of '((RE|AW|SV|VS)(\[\d+\])?:\s*)+', it should be '((RE|AW|SV|VS)\s*(\[\d+\])?\s*:\s*)+'. ** 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/893290 Title: "Re:" matching not liberal enough To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/893290/+subscriptions

2 2

[Bug 873821] [NEW] cron/checkdbs doesn't report unsubscribe requests
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The daily "nn LISTNAME moderator requests" mail counts unsubscribe requests in the total, but doesn't list them. ** Affects: mailman Importance: Low 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/873821 Title: cron/checkdbs doesn't report unsubscribe requests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/873821/+subscriptions

1 2

[Bug 862683] [NEW] List caching in the qrunners can cause the processes to grow unduly large.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The qrunners implement a cache of list objects to save reloading the list from the file system when not necessary. This cache is implemented via a weakref dictionary which is intended to free cached objects when they are no longer referenced. However, there is a self reference in the default MemberAdaptor (OldStyleMemberships) that prevents cached list objects from ever being freed. Thus, the qrunners grow until they have a cached copy of every list. This can be quite large in an installation with many lists and/or multiple large lists. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) 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/862683 Title: List caching in the qrunners can cause the processes to grow unduly large. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/862683/+subscriptions

1 2

[Bug 833134] [NEW] The password scheme for bin/export.py is case sensitive.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The help for bin/export.py says the PASSWORD_SCHEME option is case insensitive, but it isn't. ** Affects: mailman Importance: Low 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/833134 Title: The password scheme for bin/export.py is case sensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/833134/+subscriptions

1 2

[Bug 761232] [NEW] Warnings when setting a list with digest members digestable=No or with non-digest members nondigestable=No do not identify affected members.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: It would be good to identify the affected members in the warning. ** 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/761232 Title: Warnings when setting a list with digest members digestable=No or with non-digest members nondigestable=No do not identify affected members.

1 2

[Bug 745432] [NEW] Email address with leading or trailing space is not accepted by web subscribe.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If an address is entered on the web listinfo subscribe form with a leading or trailing space, it is rejected with the message "The email address you supplied is not valid. (E.g. it must contain an '@'.)". This is confusing to the user who looks at the address and sees it does contain an '@' and appears valid. Leading and trailing whitespace should be stripped from the address entry. ** 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/745432 Title: Email address with leading or trailing space is not accepted by web subscribe.

1 2

[Bug 739524] [NEW] Administrivia 'who' matches too much
by Joseph Brennan June 15, 2012

June 15, 2012

Public bug reported: Mailman/Utils.py has: 'who': (0, 2), This matches subject and start-of-line with many ordinary-language sentences or headings like 'who are you?' or 'Who is affected:'. I suggest dialing it back to (0, 1) which would have far fewer false positives, or even (0, 0) as it once was. ** 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/739524 Title: Administrivia 'who' matches too much

2 4

[Bug 721015] [NEW] Typo in cron/gate_news usage() definition.
by Mark Sapiro June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

*** 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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 June 15, 2012

June 15, 2012

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 778088] [NEW] User can set a password with trailing whitespace which prevents login.
by Mark Sapiro May 19, 2012

May 19, 2012

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 May 19, 2012

May 19, 2012

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

[Bug 925559] [NEW] Mailman Masterrunner keeps locks after force
by benste April 7, 2012

April 7, 2012

Public bug reported: I've existed Mailman just closing my terminal which didn't stop it properly. Since a8 I'm getting a message to use --force to start it which doesn't delete the locks directory hence doesn't start it. benste@benste-vpc-sb1c5e:~/Projects/Mailman/mailman-3.0.0a8$ bin/mailman start --force usage: mailman [-h] [-v] [-C CONFIG] {help,aliases,create,import21,info,inject,lists,members,qfile,remove,reopen,restart,start,status,stop,unshunt,version,withlist} ... mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force. Deleting all files in ./locks enables me to start it again. ** 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/925559 Title: Mailman Masterrunner keeps locks after force To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/925559/+subscriptions

2 3

[Bug 776122] [NEW] Bootstrap phase of setup fails
by Richard Wackerbarth April 7, 2012

April 7, 2012

Public bug reported: When attempting to build MM3 from source, the buildout phase of the bootstrap fails. The code cannot recognize the version number of the MM source. This is because the regular expression in setup.py is looking for the version to be enclosed by ", but the version.py file uses '. ** Affects: mailman Importance: Undecided Status: New ** Tags: mm3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/776122 Title: Bootstrap phase of setup fails

3 2

[Bug 883158] [NEW] Remove X-BeenThere headers
by Barry Warsaw April 7, 2012

April 7, 2012

Public bug reported: MM3 uses List-Post headers to detect mail loops now, so X-BeenThere can be removed entirely. It makes no sense to detect the MM2 legacy X-BeenThere header in MM3. Most examples currently are in the test suite, however the cook_header.py handler still sets it, and this should be removed. ** 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/883158 Title: Remove X-BeenThere headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883158/+subscriptions

1 2

[Bug 881699] [NEW] pipermail archiver renders the file location of HTML template, not the template itself
by Stephen A. Goss April 7, 2012

April 7, 2012

Public bug reported: To reproduce, enable pipermail archiver and send an email to one of your mailing lists. In the archive folder for your mailing list there will be some generated HTML files and folders. Take a look at index.html, it will contain the absolute file path of the template it should have rendered, unless I'm confused about how the archives are supposed to work: /home/phoenix/mailman_clone/src/mailman/templates/en/archtocnombox.html One of the month archive folders might have an index.html that looks like this: /home/phoenix/mailman_clone/src/mailman/templates/en/archidxhead.html  /home/phoenix/mailman_clone/src/mailman/templates/en/archidxentry.html /home/phoenix/mailman_clone/src/mailman/templates/en/archidxfoot.html ** 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/881699 Title: pipermail archiver renders the file location of HTML template, not the template itself To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881699/+subscriptions

2 2

[Bug 880990] [NEW] Broken archiver: pipermail: TypeError: decoding Unicode is not supported
by Stephen A. Goss April 7, 2012

April 7, 2012

Public bug reported: I enabled the pipermail archiver in the cfg and sent a single email through a list to see how well it works. Found this error in mailman.log: Oct 23 20:54:47 2011 (3824) Broken archiver: pipermail Traceback (most recent call last): File "/home/phoenix/mailman_clone/src/mailman/runners/archive.py", line 87, in _dispose archiver.archive_message(mlist, msg) File "/home/phoenix/mailman_clone/src/mailman/archiving/pipermail.py", line 123, in archive_message h.processUnixMailbox(path) File "/home/phoenix/mailman_clone/src/mailman/Archiver/pipermail.py", line 572, in processUnixMailbox self.add_article(a) File "/home/phoenix/mailman_clone/src/mailman/Archiver/pipermail.py", line 604, in add_article temp = self.format_article(article) File "/home/phoenix/mailman_clone/src/mailman/Archiver/HyperArch.py", line 1198, in format_article self.__processbody_URLquote(lines) File "/home/phoenix/mailman_clone/src/mailman/Archiver/HyperArch.py", line 1096, in __processbody_URLquote atmark = unicode(atmark, self.lang.charset, 'replace') TypeError: decoding Unicode is not supported ** 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/880990 Title: Broken archiver: pipermail: TypeError: decoding Unicode is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880990/+subscriptions

2 2

[Bug 782474] [NEW] Re-design the mailman favicon
by Tokio Kikuchi April 7, 2012

April 7, 2012

Public bug reported: The new mailman logo is very nice and cool. But, the reduced favicon (mm-icon.png) looks rather shabby because of its limited size and resolution. I redesigned the favicon by emphasizing the feature of crescent like lines. I also make it a 'true' windows icon format so you can put it on your desk top and make a link to your mailman site. ** 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/782474 Title: Re-design the mailman favicon

2 4

[Bug 954084] [NEW] Enhancement suggestions.
by Michael Tiernan April 7, 2012

April 7, 2012

Public bug reported: While trying to dig through the archives of multiple lists belonging to LOPSA, I realized that the archive interface might be made more useful if it had a set of indexes available. I think three really..... 1) A simple subject line index from a given moment in time forward and not simply doing it on a monthly basis. Take the "[Thread][Subject][Author]" options that are given for each month archived and make them either yearly or just "forever". My search for a specific conversation is: + Click on the "[Subject]" link for January. + scroll down the list looking for something that might be waht I want. + Hit back key, go to february and repeat. Over and over and over and over. + Repeat this whole process for the past three years. 2) Anyone remember the old "permuted index" in the old AT&T SysV manuals? http://en.wikipedia.org/wiki/Permuted_index Doing this on just the subject lines would make searching *MUCH* easier. 3) Lastly, using the more current view of this sort of thing, a 'keyword cloud' might make it more accessible too. Thanks for everyone's time and effort! -- << MCT >> Michael C Tiernan. Is God a performance artist? http://www.linkedin.com/in/mtiernan ** 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/954084 Title: Enhancement suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/954084/+subscriptions

3 4

[Bug 954718] [NEW] Make sphinx-build work correctly
by Andrea Crotti April 6, 2012

April 6, 2012

Public bug reported: There is an issue running sphinx-build now, because this function in conf.py def index_html(): import errno cwd = os.getcwd() try: os.chdir('build/sphinx/html') os.symlink('README.html', 'index.html') print 'index.html -> README.html' except OSError as error: if error.errno != errno.EEXIST: raise finally: os.chdir(cwd) tries to chdir to a directory which doesn't exist yet. Fixing this process should also make the doc building on readthedocs. ** 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/954718 Title: Make sphinx-build work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/954718/+subscriptions

2 2

[Bug 600780] [NEW] Login function needed in rest-client
by Anna April 6, 2012

April 6, 2012

Public bug reported: For a good, working Mailman 3.0 UI we have to handle the passwords for each user (needed when they subscribe/unsubscribe/want to access their settings page but also for the admins and listowners). Hence, we need to implement the possibility to check for passwords in the rest-client (I believe these are saved in the user table in the core DB) and/or a login function. We should probably use https for the psw authentication. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Login function needed in rest-client https://bugs.launchpad.net/bugs/600780 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 953707] [NEW] -C does not support relative paths
by Andrea Crotti April 6, 2012

April 6, 2012

Public bug reported: The option -C in mailman commands only support absolute paths ** 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/953707 Title: -C does not support relative paths To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953707/+subscriptions

3 3

[Bug 949926] [NEW] Add IPython support in "mailman withlist"
by Antti Kaihola April 6, 2012

April 6, 2012

Public bug reported: IPython is a convenient Python shell with useful interactive features like code completion, introspection and easy docstring viewing. It would be useful to have "mailman withlist" use it when possible. I'm attaching a quick-and-dirty patch to enable IPython if available. ** 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/949926 Title: Add IPython support in "mailman withlist" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/949926/+subscriptions

3 8

[Bug 788309] [NEW] Site configuration customization unnecessarily stored in tree
by Richard Wackerbarth April 6, 2012

April 6, 2012

Public bug reported: The i18n templates for site customization are specified to be in <template_dir>/site/ etc., a part of the tree, rather than being placed in <var_dir> (outside the tree) Solution, move them to <var_dir>/templates/site/ ** 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/788309 Title: Site configuration customization unnecessarily stored in tree

2 5

[Bug 685261] [NEW] emailed command in subject header is ignored
by Mark Sapiro April 6, 2012

April 6, 2012

Public bug reported: For example, a held message notification to the list owner/moderator contains an attached message/rfc822 part with subject "confirm <token>" and this message can be replied to with or without an "Approved: <password>" header/first body line to accept or discard the held message. The code allows for an MUA possibly inserting 'Re:' or some l10n equivalent in the subject making it "Re: confirm <token>", but if the l10n equivalent contains a non-ascii character, the entire command is ignored and the message continues to be held. ** 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/685261 Title: emailed command in subject header is ignored

2 6

[Bug 890675] [NEW] test_moderation fails on approved_at date comparison
by blacktav April 6, 2012

April 6, 2012

Public bug reported: Tests fail with Failure in test test_accepted_message_gets_posted (mailman.app.tests.test_moderation.TestModeration) Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 318, in run testMethod() File "/home/devel/mailman/src/mailman/app/tests/test_moderation.py", line 83, in test_accepted_message_gets_posted 'Mon, 01 Aug 2005 07:49:23 -') File "/usr/lib64/python2.7/unittest/case.py", line 494, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib64/python2.7/unittest/case.py", line 487, in _baseAssertEqual raise self.failureException(msg) AssertionError: 'Mon, 01 Aug 2005 07:49:23 +' != u'Mon, 01 Aug 2005 07:49:23 -' which seems to include remnants of UTC offset in its comparison perhaps it should be mailman/src/mailman/app/tests/test_moderation.py: line 82 self.assertEqual(message['x-mailman-approved-at'][:-5], 'Mon, 01 Aug 2005 07:49:23 ') ** 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/890675 Title: test_moderation fails on approved_at date comparison To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/890675/+subscriptions

3 7

[Bug 876774] [NEW] AttributeError: 'MailingList' object has no attribute 'bounce_processing'
by Vincent Fretin April 6, 2012

April 6, 2012

Public bug reported: With mailman 3.0.0a8 Oct 17 12:06:34 2011 (15436) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/bounce.py", line 46, in _dispose if not mlist.bounce_processing: AttributeError: 'MailingList' object has no attribute 'bounce_processing' It seems that bounce_processing is defined in src/mailman/styles/default.py The style are applied at mailing-list creation, but bounce_processing attribute is not persisted, the src/mailman/database/mailman.sql file doesn't define it. ** 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/876774 Title: AttributeError: 'MailingList' object has no attribute 'bounce_processing' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/876774/+subscriptions

2 3

[Bug 874929] [NEW] Missing aliases in postfix_lmtp file when using more than one mailing-list
by Vincent Fretin April 6, 2012

April 6, 2012

Public bug reported: With mailman 3.0.0a8. When I create a first mailing-list, I get in var/data/postfix_lmtp cpoi(a)example.com lmtp:[127.0.0.1]:8024 cpoi-bounces(a)example.com lmtp:[127.0.0.1]:8024 cpoi-confirm(a)example.com lmtp:[127.0.0.1]:8024 cpoi-join(a)example.com lmtp:[127.0.0.1]:8024 cpoi-leave(a)example.com lmtp:[127.0.0.1]:8024 cpoi-owner(a)example.com lmtp:[127.0.0.1]:8024 cpoi-request(a)example.com lmtp:[127.0.0.1]:8024 cpoi-subscribe(a)example.com lmtp:[127.0.0.1]:8024 cpoi-unsubscribe(a)example.com lmtp:[127.0.0.1]:8024 Then if I create a second mailing-list, I get: cpoi(a)example.com lmtp:[127.0.0.1]:8024 test(a)example.com lmtp:[127.0.0.1]:8024 test-bounces(a)example.com lmtp:[127.0.0.1]:8024 test-confirm(a)example.com lmtp:[127.0.0.1]:8024 test-join(a)example.com lmtp:[127.0.0.1]:8024 test-leave(a)example.com lmtp:[127.0.0.1]:8024 test-owner(a)example.com lmtp:[127.0.0.1]:8024 test-request(a)example.com lmtp:[127.0.0.1]:8024 test-subscribe(a)example.com lmtp:[127.0.0.1]:8024 test-unsubscribe(a)example.com lmtp:[127.0.0.1]:8024 I lost all aliases of the first mailing-list. I attached a patch for the src/mailman/mta/postfix.py file. ** 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/874929 Title: Missing aliases in postfix_lmtp file when using more than one mailing- list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/874929/+subscriptions

2 4

[Bug 869317] [NEW] Mailman startup script missing --force option.
by Stephen A. Goss April 6, 2012

April 6, 2012

Public bug reported: I rebooted the VM that mailman was running on, when I tried to start mailman up after the reboot, i got this output: $ mailman -C /etc/mailman.cfg start usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force. Running with the --force option didn't work: $ mailman --force -C /etc/mailman.cfg start usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: unrecognized arguments: --force ** 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/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions

3 7

[Bug 808821] [NEW] Probe messages should not sent Precedence header
by Barry Warsaw April 6, 2012

April 6, 2012

Public bug reported: Probe messages (sent after an address has been disabled due to bounces) should not set Precedence. This is because they actually are not bulk or list traffic. It's possible that where list traffic might be bouncing, a non-Precedence containing probe message could have a better chance of getting through. One thing to think about though is vacation programs, which (if well-behaved) will not respond to Precedence messages. Thus, if a person's address were bouncing, and they had a vacation program on, these would respond to probe messages. This might be significant if we were to score probe bounces higher (i.e. as signs to permanently disable or delete the address). ** 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/808821 Title: Probe messages should not sent Precedence header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/808821/+subscriptions

2 4

[Bug 872391] [NEW] KeyError: u'outgoing' in runner
by Stephen A. Goss April 6, 2012

April 6, 2012

Public bug reported: Found this in my mailman.log. It may have happened around the time I was attempting to send a message through a mailing list and the SMTP receiver (fakemail.py in this case) died, so there were some failures to deliver. Oct 07 16:14:47 2011 (12057) Uncaught runner exception: u'outgoing' Oct 07 16:14:47 2011 (12057) Traceback (most recent call last): File "/home/phoenix/mailman_clone/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/phoenix/mailman_clone/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/phoenix/mailman_clone/src/mailman/runners/retry.py", line 40, in _dispose config.switchboards['outgoing'].enqueue(msg, msgdata) KeyError: u'outgoing' ** 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/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions

2 6

[Bug 954252] [NEW] Simplify the version fetching
by Andrea Crotti April 6, 2012

April 6, 2012

Public bug reported: The version.py can be safely executed with execfile to extract the version number, instead of using regular expressions. ** 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/954252 Title: Simplify the version fetching To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/954252/+subscriptions

2 3

[Bug 867459] [NEW] REST API: Implement a simple way to check user credentials
by Florian Fuchs April 6, 2012

April 6, 2012

Public bug reported: Currently there is no way to check a user's credentials via the REST API. While there were discussions on implementing a middleware "hook" to implement complex authentication logic, there should also be a simple way to check if a given combination of a user's credentials (user name and password) matches the one stored in mailman's internal db. A good way to do this (as discussed on IRC a while ago) could be to implement a SQL stored procedure-like behavior in the REST API. Meaning: A client sends a uname/pwd-combination to a specific URL resource and receives a plain True or False (1 or 0?) if the combination matches. This way, no password string is sent out via the API. Things to discuss or consider: 1.) How is the password stored in MMs internal db? (plaintext or hashed? if hashed, which algorithm is used?) 2.) (How) should the pwd be encrypted when sent to the API (depends on 1.)? 3.) Should this API resource be limited to requests from localhost and/or via SSL? ** 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/867459 Title: REST API: Implement a simple way to check user credentials To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867459/+subscriptions

2 5

[Bug 860159] [NEW] Mailman 3.0 support for Postgres
by Stephen A. Goss April 6, 2012

April 6, 2012

Public bug reported: Currently, the MM3 source is SQLite specific, but only in the schema and database creation code, otherwise, it uses Storm which (mostly) supports Postgres. ** 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/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions

5 14

[Merge] lp:~syst3mw0rm/mailman/bug-890675 into lp:mailman
by Aamir Khan April 5, 2012

April 5, 2012

Aamir Khan has proposed merging lp:~syst3mw0rm/mailman/bug-890675 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~syst3mw0rm/mailman/bug-890675/+merge/93669 -- https://code.launchpad.net/~syst3mw0rm/mailman/bug-890675/+merge/93669 Your team Mailman Coders is requested to review the proposed merge of lp:~syst3mw0rm/mailman/bug-890675 into lp:mailman.

3 2

[Merge] lp:~crodjer/postorius/postorius into lp:postorius
by Rohan Jain April 5, 2012

April 5, 2012

Rohan Jain has proposed merging lp:~crodjer/postorius/postorius into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~crodjer/postorius/postorius/+merge/99881 These let the Web UI work with django 1.4 by handling changes which were there in 1.2 but are dropped from 1.4. They also do not break anything and should work fine with django 1.2/1.3 -- https://code.launchpad.net/~crodjer/postorius/postorius/+merge/99881 Your team Mailman Coders is requested to review the proposed merge of lp:~crodjer/postorius/postorius into lp:postorius.

4 5

[Bug 778688] [NEW] Invalid entry in owner roster causes infinite loop
by Richard Wackerbarth April 3, 2012

April 3, 2012

Public bug reported: If there is an error in the owners roster, a message sent to that roster bounces to the same list generating another (longer) bounce message which also bounces to the same roster, ad nausium. ** 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/778688 Title: Invalid entry in owner roster causes infinite loop

2 1

[Merge] lp:~crodjer/mailman.client/mailman.client into lp:mailman.client
by Rohan Jain March 29, 2012

March 29, 2012

Rohan Jain has proposed merging lp:~crodjer/mailman.client/mailman.client into lp:mailman.client. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~crodjer/mailman.client/mailman.client/+merge/99… These changes fix the web ui to work with django 1.4. They don't break anything and still should work with 1.2. Only the features which were deprecated in earlier versions and removed in 1.4 are changed. -- The attached diff has been truncated due to its size. https://code.launchpad.net/~crodjer/mailman.client/mailman.client/+merge/99… Your team Mailman Coders is requested to review the proposed merge of lp:~crodjer/mailman.client/mailman.client into lp:mailman.client.

1 0

[Bug 558193] Re: admin.py unicode error patch (shouldn't these all be fixed?)
by Mark Sapiro March 29, 2012

March 29, 2012

This bug report seems, at least currently, invalid. Email addresses in Mailman must be us-ascii. This has been strictly enforced since Mailman 2.1.6. Prior to that, control characters [\000-\037\177] could get through and prior to 2.1.2, high-bit characters [\200-\377] could get through, but no longer. Further, contrary to the assertion that non-ascii email addresses are valid, I don't thing they are, at least in an SMTP environment and Mailman send via SMTP. RFCs 821, 2821 and 5321 all say "Commands and replies are composed of characters from the ASCII character set". Presumably, this applies to "RCPT TO <forward-path>". In addition, both RFC 2821 and 5321 say in section 4.1.2 Command Argument Syntax "Systems MUST NOT define mailboxes in such a way as to require the use in SMTP of non-ASCII characters (octets with the high order bit set to one) or ASCII "control characters" (decimal value 0-31 and 127)." RFC 821 doesn't say exactly that, but the BNF grammer in its section 4.1.2. COMMAND SYNTAX is even stricter. Further, according to RFCs 822, 2822 and 5322, headers in messages must be ascii, and RFC 2047 which specifies a way to encode non-ascii in headers is clear that email addresses can't be so encoded. Finally, comments in the original Debian bug <http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=315358> report from which this derives recognize that this is an issue of invalid list data being migrated from Mailman 2.0. I hope by this late date, that is no longer an issue. ** Bug watch added: Debian Bug tracker #315358 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315358 ** Changed in: mailman Status: New => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558193 Title: admin.py unicode error patch (shouldn't these all be fixed?) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558193/+subscriptions

1 0

[Bug 266263] Re: NNTP gatewaying trashes Message-IDs
by Barry Warsaw March 28, 2012

March 28, 2012

** Changed in: mailman/2.1 Milestone: None => 2.1-stable ** Changed in: mailman/3.0 Milestone: 2.1-stable => None -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266263 Title: NNTP gatewaying trashes Message-IDs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266263/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Bernard March 28, 2012

March 28, 2012

** Changed in: mailman/2.1 Status: Fix Committed => Confirmed ** Changed in: mailman/3.0 Status: New => 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

2 1

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Mark Sapiro March 28, 2012

March 28, 2012

** Changed in: mailman/2.1 Status: Confirmed => Fix Committed ** Changed in: mailman/3.0 Status: Confirmed => 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 265835] Re: held message notice options
by Mark Sapiro March 28, 2012

March 28, 2012

** Changed in: mailman Status: Confirmed => 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/265835 Title: held message notice options To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265835/+subscriptions

1 0

[Bug 265835] Re: held message notice options
by Bernard March 28, 2012

March 28, 2012

** Changed in: mailman Status: Fix Committed => 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/265835 Title: held message notice options To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265835/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Mark Sapiro March 28, 2012

March 28, 2012

** Changed in: mailman/2.1 Status: In Progress => Fix Committed ** Changed in: mailman/3.0 Status: In Progress => 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

Re: [Question #191915]: unsubscription from conversations in Mailman
by Barry Warsaw March 28, 2012

March 28, 2012

Question #191915 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/191915 Status: Open => Answered Barry Warsaw proposed the following answer: On Mar 28, 2012, at 08:35 AM, Bhavya PH wrote: >New question #191915 on mailman in Ubuntu: >https://answers.launchpad.net/ubuntu/+source/mailman/+question/191915 > >I have looked through the release notes of Mailman3.0 and can find >documentation only on a user subscribing, unsubscribing to mailing lists >using REST ful API, but I am a little confused about how users are >unsubscribed from conversations ? Can someone point me to that part of the >documentation? This feature does not yet exist in Mailman 3. -Barry -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0

[Question #191915]: unsubscription from conversations in Mailman
by Bhavya PH March 28, 2012

March 28, 2012

New question #191915 on mailman in Ubuntu: https://answers.launchpad.net/ubuntu/+source/mailman/+question/191915 I have looked through the release notes of Mailman3.0 and can find documentation only on a user subscribing, unsubscribing to mailing lists using REST ful API, but I am a little confused about how users are unsubscribed from conversations ? Can someone point me to that part of the documentation? -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

2 1

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Bernard March 28, 2012

March 28, 2012

** Changed in: mailman/3.0 Status: Confirmed => In Progress ** Changed in: mailman/2.1 Status: New => 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Bernard March 28, 2012

March 28, 2012

** Changed in: mailman/2.1 Status: Fix Committed => 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Mark Sapiro March 27, 2012

March 27, 2012

** Also affects: mailman/3.0 Importance: High Assignee: Mark Sapiro (msapiro) Status: In Progress ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Changed in: mailman/2.1 Importance: Undecided => Medium ** Changed in: mailman/2.1 Status: New => Fix Committed ** Changed in: mailman/2.1 Milestone: None => 2.1.15 ** Changed in: mailman/2.1 Assignee: (unassigned) => Mark Sapiro (msapiro) ** Changed in: mailman/3.0 Importance: High => Medium ** Changed in: mailman/3.0 Status: In Progress => Confirmed ** Changed in: mailman/3.0 Milestone: 2.1.15 => None ** Changed in: mailman/3.0 Assignee: Mark Sapiro (msapiro) => (unassigned) ** Tags removed: x-un-subscribing ** Tags added: 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Barry Warsaw March 27, 2012

March 27, 2012

Mark, is there a MM3 task lurking in here too? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 266074] Re: bug in 2.1.5 - can't unsubscribe (with danish lang selected)
by Mark Sapiro March 27, 2012

March 27, 2012

** Changed in: mailman Status: Fix Committed => 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/266074 Title: bug in 2.1.5 - can't unsubscribe (with danish lang selected) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266074/+subscriptions

1 0

[Bug 266122] Re: HTML archive generation failed if language set to Finnish
by Mark Sapiro March 27, 2012

March 27, 2012

** Changed in: mailman Status: New => 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/266122 Title: HTML archive generation failed if language set to Finnish To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266122/+subscriptions

1 0

[Bug 266074] Re: bug in 2.1.5 - can't unsubscribe (with danish lang selected)
by Mark Sapiro March 27, 2012

March 27, 2012

** Changed in: mailman Status: New => 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/266074 Title: bug in 2.1.5 - can't unsubscribe (with danish lang selected) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266074/+subscriptions

1 0

[Bug 266045] Re: SMTP error code 550 not seen as bounce
by Mark Sapiro March 27, 2012

March 27, 2012

This has nothing to do with the 550 per se. What it has to do with is heuristic bounce recognitions ability to recognize these (non-standard?) DSNs. There have been many changes to bounce recognition since 2004, but it is not possible to say whether these specific bounces would be recognized without seeing all the message headers and MIME sub-part headers if any. ** Changed in: mailman Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266045 Title: SMTP error code 550 not seen as bounce To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266045/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Mark Sapiro March 27, 2012

March 27, 2012

I am testing an implementation that would include an Auto-Submitted: auto-generated header in invitations and in subscription confirmations from web subscribes and from email subscribes from a 'different' address. For email subscribes from 'this' address the header included is Auto-Submitted: auto-replied. ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: 2.1-stable => 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/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 265831] Re: Autoreplies confirm subscription invitations
by Lukáš Lánský March 27, 2012

March 27, 2012

Please note that RFC 3834 says: "Automatic responses SHOULD NOT be issued in response to any message which contains an Auto-Submitted header field (see below), where that field has any value other than "no"." I think that system messages from Mailman are in scope of this header semantics (with the value "auto-generated") and we would solve the problem if we implement this. Do you agree? I would gladly implement it. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265831 Title: Autoreplies confirm subscription invitations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265831/+subscriptions

1 0

[Bug 266054] Re: Focus form entry onload in admlogin.html
by Mark Sapiro March 25, 2012

March 25, 2012

Also patched templates/ar/admlogin.html and the templates/ast/ and templates/el/ private.html and admlogin.html templates not included in the patch in comment #4. ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: 2.1-stable => 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/266054 Title: Focus form entry onload in admlogin.html To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266054/+subscriptions

1 0

[Bug 266684] Re: Archive URL in Email
by Barry Warsaw March 23, 2012

March 23, 2012

** Changed in: mailman Milestone: 3.0.0b1 => postponed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266684 Title: Archive URL in Email To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266684/+subscriptions

1 0

[Branch ~mailman-coders/mailman.client/trunk] Rev 28: added information on held messages
by noreply＠launchpad.net March 23, 2012

March 23, 2012

------------------------------------------------------------ revno: 28 committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Sat 2012-03-24 00:24:28 +0100 message: added information on held messages modified: mailman/client/__init__.py mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Bug 265898] Re: mail commands
by Mark Sapiro March 23, 2012

March 23, 2012

This bug was fixed in Mailman 2.1.4. ** Changed in: mailman 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/265898 Title: mail commands To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265898/+subscriptions

1 0

[Bug 265898] Re: mail commands
by Bernard March 23, 2012

March 23, 2012

** Changed in: mailman Status: New => 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/265898 Title: mail commands To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265898/+subscriptions

1 0

[Bug 266684] Re: Archive URL in Email
by Bernard March 23, 2012

March 23, 2012

** Changed in: mailman Status: New => Incomplete ** Changed in: mailman Status: Incomplete => 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/266684 Title: Archive URL in Email To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266684/+subscriptions

1 0

[Branch ~mailman-coders/mailman.client/trunk] Rev 27: Attempting to get user.preferences working. it's not actually working yet
by noreply＠launchpad.net March 23, 2012

March 23, 2012

------------------------------------------------------------ revno: 27 committer: Terri Oda <terri(a)zone12.com> branch nick: mailman.client timestamp: Thu 2012-03-22 23:04:34 -0600 message: Attempting to get user.preferences working. it's not actually working yet but this might serve as a starting point. modified: mailman/client/_client.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Bug 266684] Re: Archive URL in Email
by Barry Warsaw March 22, 2012

March 22, 2012

** Tags added: mailman3 ** Changed in: mailman Milestone: None => 3.0.0b1 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266684 Title: Archive URL in Email To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266684/+subscriptions

1 0

[Branch ~mailman-coders/mailman.client/trunk] Rev 26: added moderation
by noreply＠launchpad.net March 22, 2012

March 22, 2012

------------------------------------------------------------ revno: 26 committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Thu 2012-03-22 21:37:39 +0100 message: added moderation modified: mailman/client/_client.py mailman/client/docs/using.txt setup.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Bug 956889] [NEW] Get the public URL from a mail
by Andrea Crotti March 20, 2012

March 20, 2012

Public bug reported: This is more a feature request than a bug. Often when I'm reading mails from mailing lists I would like to get easily the url from the web page-archives, which is useful to show the thread to other people that are not on the list. Is there a way to do this already? If not I think there are two options at least: 1. create a way in the API to retrieve the url in the archives from the mail ID 2. add an customisable option where the user can ask to get the public URL attached to every email he receives. The second seems easier to implement though, any ideas? ** 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/956889 Title: Get the public URL from a mail To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/956889/+subscriptions

4 3

[Merge] lp:~andrea-crotti-0/mailman/test_doc into lp:mailman
by Andrea Crotti March 19, 2012

March 19, 2012

Andrea Crotti has proposed merging lp:~andrea-crotti-0/mailman/test_doc into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~andrea-crotti-0/mailman/test_doc/+merge/98295 Added some doc from the Testing instructions in the e-mail. This is far from perfect but I don't know much about it yet, so please give me some feedback about how it should be structured and what I should add.. -- https://code.launchpad.net/~andrea-crotti-0/mailman/test_doc/+merge/98295 Your team Mailman Coders is requested to review the proposed merge of lp:~andrea-crotti-0/mailman/test_doc into lp:mailman.

1 0

[Bug 266054] Re: Focus form entry onload in admlogin.html
by Thijs Kinkhorst March 18, 2012

March 18, 2012

This issue has been reported a number of times already with different patches along the same principle. Here's another one, this one has been included in the Debian/Ubuntu packages for years now. ** Patch added: "patch as used in Debian package" https://bugs.launchpad.net/mailman/+bug/266054/+attachment/2890992/+files/9… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266054 Title: Focus form entry onload in admlogin.html To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266054/+subscriptions

1 0

[Bug 558285] Re: [PATCH] Focus first textbox at the admin login page
by Thijs Kinkhorst March 18, 2012

March 18, 2012

*** This bug is a duplicate of bug 266054 *** https://bugs.launchpad.net/bugs/266054 ** This bug has been marked a duplicate of bug 266054 Focus form entry onload in admlogin.html -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558285 Title: [PATCH] Focus first textbox at the admin login page To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558285/+subscriptions

1 0

[Bug 558233] Re: Focus password field on admin login page load
by Thijs Kinkhorst March 18, 2012

March 18, 2012

*** This bug is a duplicate of bug 266054 *** https://bugs.launchpad.net/bugs/266054 ** This bug has been marked a duplicate of bug 266054 Focus form entry onload in admlogin.html -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558233 Title: Focus password field on admin login page load To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558233/+subscriptions

1 0

[Merge] lp:~stephen-xemacs/mailman/sprint-2012-overview into lp:mailman
by Stephen Turnbull March 17, 2012

March 17, 2012

Stephen Turnbull has proposed merging lp:~stephen-xemacs/mailman/sprint-2012-overview into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~stephen-xemacs/mailman/sprint-2012-overview/+me… Andrea Crotti's work making python setup.py build_sphinx work, plus my "Overview" document. This branch contains and supersedes lp:~andrea-crotti-o/mailman/conf_py. To build the docs on my Mac OS X/Macports system I used $ python2.6 bootstrap.py # get python 2.6 from MacPorts $ bin/buildout $ python2.6 setup.py build_sphinx The output ends up in src/mailman/docs/build/sphinx/html/README.html. No promises for other platforms. :-p New files in src/mailman/docs: 8-miles-high.rst # ReST file containing notes from Mailman sprint at PyCon 2012 chains.png # used by 8-miles-high: pipeline.png # from Barry Warsaw's Mailman presentation msg-flow.png # replaced by in-line graphviz code (will be removed) Other changes to (1) fix build, and (2) integrate 8-miles-high into README.rst. -- https://code.launchpad.net/~stephen-xemacs/mailman/sprint-2012-overview/+me… Your team Mailman Coders is requested to review the proposed merge of lp:~stephen-xemacs/mailman/sprint-2012-overview into lp:mailman.

2 1

[Bug 950542] [NEW] newlist --emailhost does not create virtual aliases in virtual-mailman
by Chris Miller March 16, 2012

March 16, 2012

Public bug reported: Version mailman-2.1.14 With the virtual URL and domain already configured in mm_cfg.py (below), running newlist with --emailhost and --urlhost does not populate the virtual-mailman specific aliases. Adding the list via a browser using the virtual URL results in the expected behavior. It would seem that the browser based method is doing something differently. mm_cfg.py MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com'] add_virtualhost('lists.example.com', 'example.com') ** Affects: mailman Importance: Undecided Status: New ** Tags: virtual-mailman -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/950542 Title: newlist --emailhost does not create virtual aliases in virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/950542/+subscriptions

2 3

[Branch ~mailman-coders/mailman.client/trunk] Rev 25: return list of held messages
by noreply＠launchpad.net March 15, 2012

March 15, 2012

------------------------------------------------------------ revno: 25 committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Thu 2012-03-15 15:34:01 -0700 message: return list of held messages modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Merge] lp:~mdaniel-k/mailmanweb/acceptable_aliases into lp:mailmanweb
by Daniel Mizyrycki March 15, 2012

March 15, 2012

Daniel Mizyrycki has proposed merging lp:~mdaniel-k/mailmanweb/acceptable_aliases into lp:mailmanweb. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~mdaniel-k/mailmanweb/acceptable_aliases/+merge/… Properly display acceptable aliases -- https://code.launchpad.net/~mdaniel-k/mailmanweb/acceptable_aliases/+merge/… Your team Mailman Coders is requested to review the proposed merge of lp:~mdaniel-k/mailmanweb/acceptable_aliases into lp:mailmanweb.

1 0

[Merge] lp:~andrea-crotti-0/mailman/py_interactive into lp:mailman
by Andrea Crotti March 15, 2012

March 15, 2012

Andrea Crotti has proposed merging lp:~andrea-crotti-0/mailman/py_interactive into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #949926 in GNU Mailman: "Add IPython support in "mailman withlist"" https://bugs.launchpad.net/mailman/+bug/949926 For more details, see: https://code.launchpad.net/~andrea-crotti-0/mailman/py_interactive/+merge/9… There is a tiny change from the version already merged, because now sys.ps1 is set correctly even if readline/rlcompleter fail.. Not sure what's the best way to proceed but I guess that reproposing to merge after the commit should be the right way. -- https://code.launchpad.net/~andrea-crotti-0/mailman/py_interactive/+merge/9… Your team Mailman Coders is requested to review the proposed merge of lp:~andrea-crotti-0/mailman/py_interactive into lp:mailman.

1 0

[Branch ~mailman-coders/mailman.client/trunk] Rev 24: * fixed real_name key lookup for mass-subscribed members (no real_name)
by noreply＠launchpad.net March 15, 2012

March 15, 2012

------------------------------------------------------------ revno: 24 committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Thu 2012-03-15 11:30:54 -0700 message: * fixed real_name key lookup for mass-subscribed members (no real_name) * added method for held messages modified: mailman/client/_client.py mailman/client/docs/using.txt mailman/client/tests/test_docs.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Merge] lp:~toshio/mailman/py2.6 into lp:mailman
by Toshio Kuratomi March 15, 2012

March 15, 2012

Toshio Kuratomi has proposed merging lp:~toshio/mailman/py2.6 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~toshio/mailman/py2.6/+merge/97707 Fix unittest to take into account incompatibile output between python2.6 and python2.7 logging module -- https://code.launchpad.net/~toshio/mailman/py2.6/+merge/97707 Your team Mailman Coders is requested to review the proposed merge of lp:~toshio/mailman/py2.6 into lp:mailman.

2 2

[Merge] lp:~toshio/mailman/count into lp:mailman
by Toshio Kuratomi March 15, 2012

March 15, 2012

Toshio Kuratomi has proposed merging lp:~toshio/mailman/count into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~toshio/mailman/count/+merge/97576 Expose the volume and count of members per mailing list in the rest api. -- https://code.launchpad.net/~toshio/mailman/count/+merge/97576 Your team Mailman Coders is requested to review the proposed merge of lp:~toshio/mailman/count into lp:mailman.

1 0

[Merge] lp:~mdaniel-k/mailmanweb/dependency into lp:mailmanweb
by Daniel Mizyrycki March 15, 2012

March 15, 2012

Daniel Mizyrycki has proposed merging lp:~mdaniel-k/mailmanweb/dependency into lp:mailmanweb. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~mdaniel-k/mailmanweb/dependency/+merge/97553 This changeset adds a needed dependency for mailmanweb -- https://code.launchpad.net/~mdaniel-k/mailmanweb/dependency/+merge/97553 Your team Mailman Coders is requested to review the proposed merge of lp:~mdaniel-k/mailmanweb/dependency into lp:mailmanweb.

1 0

[Merge] lp:~toshio/mailman/maildir into lp:mailman
by Toshio Kuratomi March 15, 2012

March 15, 2012

Toshio Kuratomi has proposed merging lp:~toshio/mailman/maildir into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~toshio/mailman/maildir/+merge/97542 Merge a fix for potential unicode issues while we're thinking of it. -- https://code.launchpad.net/~toshio/mailman/maildir/+merge/97542 Your team Mailman Coders is requested to review the proposed merge of lp:~toshio/mailman/maildir into lp:mailman.

1 0

[Merge] lp:~andrea-crotti-0/mailman/conf_py into lp:mailman
by Andrea Crotti March 14, 2012

March 14, 2012

Andrea Crotti has proposed merging lp:~andrea-crotti-0/mailman/conf_py into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #954718 in GNU Mailman: "Make sphinx-build work correctly" https://bugs.launchpad.net/mailman/+bug/954718 For more details, see: https://code.launchpad.net/~andrea-crotti-0/mailman/conf_py/+merge/97343 -- https://code.launchpad.net/~andrea-crotti-0/mailman/conf_py/+merge/97343 Your team Mailman Coders is requested to review the proposed merge of lp:~andrea-crotti-0/mailman/conf_py into lp:mailman.

1 0

[Merge] lp:~andrea-crotti-0/mailman/version into lp:mailman
by Andrea Crotti March 13, 2012

March 13, 2012

Andrea Crotti has proposed merging lp:~andrea-crotti-0/mailman/version into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~andrea-crotti-0/mailman/version/+merge/97258 -- https://code.launchpad.net/~andrea-crotti-0/mailman/version/+merge/97258 Your team Mailman Coders is requested to review the proposed merge of lp:~andrea-crotti-0/mailman/version into lp:mailman.

1 0

[Merge] lp:~toshio/mailman/maildir into lp:mailman
by Toshio Kuratomi March 13, 2012

March 13, 2012

Toshio Kuratomi has proposed merging lp:~toshio/mailman/maildir into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~toshio/mailman/maildir/+merge/97142 Change the prototype archiver to save to maildir. Add an archive_dir config path -- https://code.launchpad.net/~toshio/mailman/maildir/+merge/97142 Your team Mailman Coders is requested to review the proposed merge of lp:~toshio/mailman/maildir into lp:mailman.

1 0

[Merge] lp:~andrea-crotti-0/mailman/abspath into lp:mailman
by Andrea Crotti March 13, 2012

March 13, 2012

Andrea Crotti has proposed merging lp:~andrea-crotti-0/mailman/abspath into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #953707 in GNU Mailman: "-C does not support relative paths" https://bugs.launchpad.net/mailman/+bug/953707 For more details, see: https://code.launchpad.net/~andrea-crotti-0/mailman/abspath/+merge/97141 -- https://code.launchpad.net/~andrea-crotti-0/mailman/abspath/+merge/97141 Your team Mailman Coders is requested to review the proposed merge of lp:~andrea-crotti-0/mailman/abspath into lp:mailman.

1 0

[Merge] lp:~andrea-crotti-0/mailman/py_interactive into lp:mailman
by Andrea Crotti March 13, 2012

March 13, 2012

Andrea Crotti has proposed merging lp:~andrea-crotti-0/mailman/py_interactive into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #949926 in GNU Mailman: "Add IPython support in "mailman withlist"" https://bugs.launchpad.net/mailman/+bug/949926 For more details, see: https://code.launchpad.net/~andrea-crotti-0/mailman/py_interactive/+merge/9… -- https://code.launchpad.net/~andrea-crotti-0/mailman/py_interactive/+merge/9… Your team Mailman Coders is requested to review the proposed merge of lp:~andrea-crotti-0/mailman/py_interactive into lp:mailman.

1 0

[Bug 266390] Re: Storing of passwords
by Mark Sapiro March 6, 2012

March 6, 2012

*** This bug is a duplicate of bug 265179 *** https://bugs.launchpad.net/bugs/265179 ** This bug has been marked a duplicate of bug 265179 Security hole: passwords mailed in clear -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266390 Title: Storing of passwords To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266390/+subscriptions

1 0

[Merge] lp:~xtaran/mailman/mailman-improvements into lp:mailman/2.1
by Axel Beckert March 1, 2012

March 1, 2012

Axel Beckert has proposed merging lp:~xtaran/mailman/mailman-improvements into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~xtaran/mailman/mailman-improvements/+merge/95448 Add two options named -m (--moderated) and -M (--non-moderated) to list_members to list either only moderated list members or only non-moderated list members. -- https://code.launchpad.net/~xtaran/mailman/mailman-improvements/+merge/95448 Your team Mailman Coders is requested to review the proposed merge of lp:~xtaran/mailman/mailman-improvements into lp:mailman/2.1.

1 0