Mailman 3 June 2011 - Mailman-coders

[Bug 283751] Re: feature request: fetch archived emails
by Nikodemus Siivola 14 Jun '11

14 Jun '11

Me type good again. "Out of place", even. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/283751 Title: feature request: fetch archived emails To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions

1 0

[Bug 283751] Re: feature request: fetch archived emails
by Nikodemus Siivola 14 Jun '11

14 Jun '11

Out of date architecturally, maybe, but from usage perspective it's a very clear fit. While I'm not at all knowledgeable on mailman internals, isn't it mailman that writes the mbox file? I don't see how things like: resend last 10 mails resend last 3 days resend date 2011-06-11 resend dates 2011-06-10 - 2011-06-12 resend id 0C620D08-D620-4331-88C8-B4E98A3384AC(a)NFSNet.org resend ids 0C620D08-D620-4331-88C8-B4E98A3384AC(a)NFSNet.org - <another- id> would require more than trivial parsing or secondary indexing of the mbox. It's also mailman who does sending of mail, not the archiver, right? :) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/283751 Title: feature request: fetch archived emails To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions

1 0

[Bug 796836] [NEW] Valid set commands are never detected as administrivia.
by Mark Sapiro 13 Jun '11

13 Jun '11

Public bug reported: The is_administrivia function in Mailman/Utils.py requires a 'set' command to have exactly three arguments and further requires that the second argument be 'on' or 'off' in order to be detected as administrivia. This means that none of the following valid commands are detected. set help set show [address=<address>] set authenticate <password> [address=<address>] set<keyword> on set <keyword> off set digest plain set digest mime Unless the command is set authenticate <password> address=<address> and the password is 'on' or 'off', however a line such as set that off topic would be detected as administrivia even though it is not. Clearly the intent was to require two arguments, not three, but even this would not detect things like set help or set digest plain The obvious fix is to require between one and two (or maybe three) arguments and to not require the second argument to be 'on' or 'off', but this may wind up giving too many false positives. This bug has existed since the format of the set command was changed in Mailman 2.1, and I'm not aware of any complaints about 'set' not being caught as administrivia, so I'm reluctant to 'rock the boat' too much. Does anyone have an opinion on this? ** 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/796836 Title: Valid set commands are never detected as administrivia. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/796836/+subscriptions

1 0

[Bug 283751] Re: feature request: fetch archived emails
by Nikodemus Siivola 13 Jun '11

13 Jun '11

s/possible with all clients/not possible with all clients/ obviously... -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/283751 Title: feature request: fetch archived emails To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions

1 0

[Bug 283751] Re: feature request: fetch archived emails
by Nikodemus Siivola 13 Jun '11

13 Jun '11

I miss this semi-regularly -- maybe a few times a year. For some reason an email goes astray or doesn't arrive (doesn't matter if I binned it by accident or if my mailhost was down or whatever), or I want to reply to a message from before my subscription. Then I always pine for the bad old days of majordomo when I could send a request for /specific/ old mails, and lo! there they would be -- and everything archives nicely and conversations remain threaded. Getting the list archives isn't always possible -- not every list makes the mbox available (eg. SourceForge uses mailman and doesn't give mbox files to hoi polloi) -- and reply munging is tedious, and possible with all clients. Please, please, please consider this. This is my only major beef with 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/283751 Title: feature request: fetch archived emails To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions

1 0

[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 266771] Re: Web interface to sync_members
by Tokio Kikuchi 10 Jun '11

10 Jun '11

I know this is an old request and many of the users don't look like in need of this. But, I recently get a request from a list administrator for syncing members and wanted to implement the sync_members function in the web interface. The idea is to add a 'synchronize' flag in admin/members/add form and synchronize the member list with this file rather than simply adding the member. There is no radio buttons for unsubscribe notifications and they are taken from 'send welcome message' and 'admin notification' buttons. The sync operation is done with uploaded file only. If there is no file, then the synchronize flag is ignored. ** Attachment added: "Add synchronize function in mass subscription web ui" https://bugs.launchpad.net/mailman/+bug/266771/+attachment/2163103/+files/s… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266771 Title: Web interface to sync_members To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266771/+subscriptions

1 0

Mailman-coders June 2011