Mailman 3 October 2011 - Mailman-coders

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

April 6, 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 … [View More]

2 4

[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 … [View More]

3 4

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

April 5, 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/… [View More]

2 5

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

April 5, 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 … [View More]

2 6

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

April 5, 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/… [View More]

2 3

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

April 5, 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.… [View More]

2 4

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

April 5, 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 … [View More]

3 7

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

April 5, 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 … [View More]

2 4

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

April 5, 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.… [View More]

2 6

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

April 5, 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.… [View More]

2 5