Mailman 3 December 2011 - Mailman-coders

[Bug 881699] [NEW] pipermail archiver renders the file location of HTML template, not the template itself
by Stephen A. Goss 07 Apr '12

07 Apr '12

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 07 Apr '12

07 Apr '12

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 07 Apr '12

07 Apr '12

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 600780] [NEW] Login function needed in rest-client
by Anna 06 Apr '12

06 Apr '12

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 788309] [NEW] Site configuration customization unnecessarily stored in tree
by Richard Wackerbarth 06 Apr '12

06 Apr '12

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 06 Apr '12

06 Apr '12

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 06 Apr '12

06 Apr '12

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 06 Apr '12

06 Apr '12

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 06 Apr '12

06 Apr '12

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 06 Apr '12

06 Apr '12

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