Mailman 3 May 2011 - Mailman-coders

[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 778688] [NEW] Invalid entry in owner roster causes infinite loop
by Richard Wackerbarth 03 Apr '12

03 Apr '12

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

[Bug 778687] [NEW] Invalid roster upon initial list creation
by Richard Wackerbarth 25 Sep '11

25 Sep '11

Public bug reported: GNU Mailman 3.0.0a7+ (Where's My Thing?) -- bzr=7005 When executing bin/mailman create -domain=True example(a)throwaway.domain, the example-owner get populated with an entry INSERT INTO "address" VALUES(1,'main=true','main=True','',NULL,'2005-08-01 07:49:23',1,2); The roster should be empty. ** 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/778687 Title: Invalid roster upon initial list creation

2 4

[Bug 770328] [NEW] REST qrunner sometimes does not exit after tests exception
by Barry Warsaw 25 Sep '11

25 Sep '11

Public bug reported: When the test suite gets an exception in the REST qrunner, it sometimes prevents the qrunner from exiting. The symptom of this is that the next time you try to run the test suite, you'll get an Address In Use error early on. This is because the test suite will try to start a new REST qrunner, which wants to bind to port 9001, but that's already in use by the "zombie" qrunner. The workaround is fairly simple. Just kill -HUP the zombie from the shell. Once it exits, the port gets freed up and the test suite will work again. ** 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/770328 Title: REST qrunner sometimes does not exit after tests exception

1 4

[Bug 787599] [NEW] host_name ancient name for mail_host
by benste 25 Sep '11

25 Sep '11

Public bug reported: please update the settings and core to support "mail_host" instead of "host_name" which is confusing in comparision to "web_host" The same thing needs to be done in the REST Api to support this change ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailmanweb Importance: Medium Status: Confirmed ** Also affects: mailmanweb Importance: Undecided Status: New ** Changed in: mailman Status: New => Opinion ** Changed in: mailmanweb Status: New => Opinion -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/787599 Title: host_name ancient name for mail_host

2 4

[Bug 772135] [NEW] The bounce qrunner needs to be enabled
by Barry Warsaw 25 Sep '11

25 Sep '11

Public bug reported: The Mailman 3 bounce qrunner isn't really enabled. It needs to be hooked up to scan_message() and tested. ** 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/772135 Title: The bounce qrunner needs to be enabled

1 2

[Merge] lp:~flo-fuchs/mailman.client/settings into lp:mailman.client
by Florian Fuchs 20 Jun '11

20 Jun '11

Florian Fuchs has proposed merging lp:~flo-fuchs/mailman.client/settings into lp:mailman.client. Requested reviews: Barry Warsaw (barry) For more details, see: https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088 Hi, I have added methods to delete mailing lists as well as a _Settings class to read and write list settings. Please feel free to make any changes you want (...and, of course, tell me if you feel this should be done completely differently... ;-) Cheers Florian -- https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088 Your team Mailman Coders is subscribed to branch lp:mailman.client.

3 7

[Bug 667252] [NEW] Mailman 3 Branch, install fails with --prefix specified
by Simon Fraser 13 Jun '11

13 Jun '11

Public bug reported: When trying to install mailman outside the Python tree, I get the following error: (I've replaced my home directory with $HOME in the below text) $ whoami srf $ /software/bin/python-2.6.3 setup.py install --prefix=~srf/mailman-install running install Checking .pth file support in /$HOME/mailman-install/lib/python2.6/site-packages/ error: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 2] No such file or directory: '/$HOME/mailman- install/lib/python2.6/site-packages/test-easy-install-20075.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /$HOME/mailman-install/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option). ** Affects: mailman Importance: Undecided Status: New -- Mailman 3 Branch, install fails with --prefix specified https://bugs.launchpad.net/bugs/667252 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 266263] Re: NNTP gatewaying trashes Message-IDs
by Ike 30 May '11

30 May '11

I solved this problem in another way. Someone wrote for me the SynFU- script: https://github.com/Shirk/SynFU It is a very good script for synchronizing mails between mailing lists and a newsserver. I'm using it on a system with more than 200 mailing lists and up to 1000 postings a day. -- 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

1 0

[Bug 266263] Re: NNTP gatewaying trashes Message-IDs
by Joshua Cranmer 30 May '11

30 May '11

Here is my proposal for what to do: 1. Find all known mailing lists in the to/cc headers, and simultaneously crosspost to those newsgroups 2. Only rewrite a message ID if the news server has one on the server that does not represent this message. This means that all of the problems with message IDs should be limited to people who put the mailing lists in BCCs, or people who are sending to mailing lists on multiple servers that inject into NNTP in different places. I do not yet have a patch for either yet. -- 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

1 0