Mailman 3 September 2010 - Mailman-Users

deleting mailman subscriber when spaces are in the address
by ljacobs Sept. 21, 2010

Sept. 21, 2010

I have a member who somehow got entered as "info(a)nesa.edu see notes re" (without the quotes) and I cannot delete that member via the usual commands or web interface. Can this be done using some mailman or python commands? Thanks.

2 1

weird messages..
by Khalil Abbas Sept. 21, 2010

Sept. 21, 2010

Hi, I recently started to recieve messages from listname-bounces@mydomain like this: _____________________________________ The results of your email command are provided below. Attached is your original message. - Results: Ignoring non-text/plain MIME parts - Unprocessed: This is an automatically generated Delivery Status Notification THIS IS A WARNING MESSAGE ONLY. Delivery to the following recipient has been delayed: SOMEMEAILADDRESS@DOMAIN Message will be retried for 2 more day(s) - Done. _____________________________________ I haven't changed ny settings in my list and never recieved such messages as above for years! is there something I should worry about like someone trying to mess around with my lists or something ? please advise..

2 3

RELEASED: Mailman 3.0 alpha 6
by Barry Warsaw Sept. 20, 2010

Sept. 20, 2010

I happy (and somewhat relieved :) to announce the release of the sixth alpha for Mailman 3.0. There is much new coolness that you will want to explore. The biggest change is that the administrative REST API has been greatly improved and is now reasonably well fleshed out. You can create and delete domains and mailing lists, subscribe and unsubscribe members, and reconfigure your mailing lists through the REST API. The documentation has specific examples of how to do it. This means that you can actually start to try to integrate Mailman with your web sites. The big push between now and the first beta will be to complete the import of Mailman 2.1 data, and integrate it with the UI work done by Anna and Florian for the GSoC. The tarball can be downloaded from Launchpad or the Cheeseshop: https://edge.launchpad.net/mailman http://pypi.python.org/pypi/mailman/3.0.0a6 The full documentation is also available online: http://packages.python.org/mailman/docs/README.html See below for the changes since alpha 5. Please note that Mailman 3 is not yet ready for production, although we'd love it if you test it and provide feedback! Enjoy, -Barry 3.0 alpha 6 -- "Cut to the Chase" ================================= (2010-09-20) Commands -------- * The functionality of 'bin/list_members' has been moved to 'bin/mailman members'. * 'bin/mailman info' -v/--verbose output displays the file system layout paths Mailman is currently configured to use. Configuration ------------- * You can now configure the paths Mailman uses for queue files, lock files, data files, etc. via the configuration file. Define a file system 'layout' and then select that layout in the [mailman] section. Default layouts include 'local' for putting everything in /var/tmp/mailman, 'dev' for local development, and 'fhs' for Filesystem Hierarchy Standard 2.3 (LP #490144). * Queue file directories now live in $var_dir/queues. REST ---- * lazr.restful has been replaced by restish as the REST publishing technology used by Mailman. * New REST API for getting all the members of a roster for a specific mailing list. * New REST API for getting and setting a mailing list's configuration. GET and PUT are supported to retrieve the current configuration, and set all the list's writable attributes in one request. PATCH is supported to partially update a mailing list's configuration. Individual options can be set and retrieved by using subpaths. * Subscribing an already subscribed member via REST now returns a 409 HTTP error. LP: #552917 * Fixed a bug when deleting a list via the REST API. LP: #601899 Architecture ------------ * X-BeenThere header is removed. * Mailman no longer touches the Sender or Errors-To headers. * Chain actions can now fire Zope events in their _process() implementations. * Environment variable $MAILMAN_VAR_DIR can be used to control the var/ directory for Mailman's runtime files. New environment variable $MAILMAN_UNDER_MASTER_CONTROL is used instead of the qrunner's --subproc/-s option. Miscellaneous ------------- * Allow X-Approved and X-Approve headers, equivalent to Approved and Approve. LP: #557750 * Various test failure fixes. LP: #543618, LP: #544477 * List-Post header is retained in MIME digest messages. LP: #526143 * Importing from a Mailman 2.1.x list is partially supported.

1 0

Mailman 2.1.14 released.
by Mark Sapiro Sept. 20, 2010

Sept. 20, 2010

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am happy to announce the final release of GNU Mailman 2.1.14. Mailman 2.1.14 is mainly a bug fix release, but it contains one security fix as previously announced at <http://mail.python.org/pipermail/mailman-announce/2010-September/000151.html> and one new feature. It differs from the previously released 2.1.14rc1 only in wording clarifications and typo corrections in a few messages. This new feature controls the addition/replacement of the Sender: header in outgoing mail. This allows a list owner to set include_sender_header on the list's General Options page in the admin GUI. The default for this setting is Yes which preserves the prior behavior of removing any pre-existing Sender: and setting it to the list's -bounces address. Setting this to No stops Mailman from adding or modifying the Sender: at all. Additionally, there is a new Defaults.py/mm_cfg.py setting ALLOW_SENDER_OVERRIDES which defaults to Yes but which can be set to No to remove the include_sender_header setting from General Options, and thus preserve the prior behavior completely. Python 2.4 is the minimum supported, but Python 2.5.or 2.6 is recommended. See the changelog at <https://launchpad.net/mailman/2.1/2.1.14> for more details. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see: http://www.list.org http://www.gnu.org/software/mailman Mailman 2.1.14 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ - -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFMl7bXVVuXXpU7hpMRAtKyAJ4hnS08i71tx9nx1iG9wkGI9FalggCgqjnF 3CvTQeW7TOY76+u/KBNBGuM= =we0d -----END PGP SIGNATURE-----

1 0

Re: [Mailman-Users] Can't change settings in Web Interface
by Oliver Schad Sept. 20, 2010

Sept. 20, 2010

Am Monday 20 September 2010 schrieb mir Néstor Díaz Valencia: > Who is serving mailman web interface? apache2? Yes. > Have you checked web server logs? Yes. If I post something, I get a HTTP 302. The redirect points to the site, where you come from. No error nowhere. > Have you checked web interface HTML code? (It's ctrl+u in most > browsers) > > Fore example, in general Options web page in my setup I can read this: > <FORM action="http://somedomain.com/admin/mailman/general" > method="POST" I checked this already. And I can see the POST in the web server log. > Can it be that your mailman forms are sending information to the old > url? I don't think so. I've made a dump of the traffic, too. I see the complete form: POST /cgi-bin/mailman/admin/club/members?letter=d HTTP/1.1 Host: xxx.com [Header with Form] HTTP/1.1 302 Found [...] Location: xxx.com/cgi-bin/mailman/admin/club/members?letter=d Is there a way to split the whole action into two parts. The apache gets now the requests, the CGIs collect the information from the form and call something. Can I call this something manually as the apache user to test where the problem is and how can I do this? Regards Oli

2 3

Re: [Mailman-Users] Can't change settings in Web Interface
by Oliver Schad Sept. 20, 2010

Sept. 20, 2010

Am Monday 20 September 2010 schrieb mir Mark Sapiro: > On 9/19/2010 1:37 PM, Oliver Schad wrote: > > Hi all, > > > > I've migrated an existing mailman list from one system to another > > with a complete different linux distribution. > > > > I changed the domain also and everything works fine. But the Web- > > doesn't accept changes. I found no error message anywhere. The Web > > Interface shows all information, I can log in. But I can't make any > > change. Commandline tools works fine too. > > Is this the case for new lists too? Did you run fix_url on the migrated > lists? Yes, I did. The URL inside mails from the lists are ok. > > This looks like a permission problem I thought so I checked the > > permissions manually and with the script "check_perms". It fixed some > > permissions and doesn't like symlinks like in debian what I'm using, > > so it only checks the permissions of the symlink itselfs not the > > target. > > But it fixes the target and then continues to complain about the > symlink, so there should actually be no problem. Ok, sounds a little bit strange. > > I've checked the targets manually and everything seems to be ok. > > > > I need a way to debug this problem, any ideas? > > See the FAQ at <http://wiki.list.org/x/ioA9>. I can't see a difference to what I did. I added "VIRTUAL_HOSTS.clear() " to /etc/mailman/mm_cfg.py and restartet Mailman but I can't see a difference. Is there no (easy) way to follow the request inside so I can debug step by step? Regards Oli

1 0

Re: [Mailman-Users] Reply to sender and list
by Mark Sapiro Sept. 20, 2010

Sept. 20, 2010

>The last chance is to patch the sources, modifying the Header Cooker, I >already tried, but is unclear how it works and I just obtained a mess ;) The attached patch to CookHeaders.py will do what you want. With the patch, if the list's first_strip_reply_to is No and the original post does not contain a Reply-To:, Mailman will add a Reply-To: with the address from the From: header (or the Sender: header if there is no From:). So with the patch if you set first_strip_reply_to to No and also set reply_goes_to_list to This list, the delivered posts will have Reply-To: containing both the list address and either the From: address or the original Reply-To: address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Can't change settings in Web Interface
by Oliver Schad Sept. 20, 2010

Sept. 20, 2010

Hi all, I've migrated an existing mailman list from one system to another with a complete different linux distribution. I changed the domain also and everything works fine. But the Web- doesn't accept changes. I found no error message anywhere. The Web Interface shows all information, I can log in. But I can't make any change. Commandline tools works fine too. This looks like a permission problem I thought so I checked the permissions manually and with the script "check_perms". It fixed some permissions and doesn't like symlinks like in debian what I'm using, so it only checks the permissions of the symlink itselfs not the target. I've checked the targets manually and everything seems to be ok. I need a way to debug this problem, any ideas? Regards Oli

3 2

Mailman automatically unsubscribe user without permission
by eagseek Sept. 19, 2010

Sept. 19, 2010

Hello everyone, We have a mailman mailing list system. Everything works fine except for one mainling list. For this mailing list, whenever a new user is added to the member list, that user will receive two welcome emails with two different passwords first. And you can search and find that user in the members list under the mailing list administration page. Then after a few minutes, the user will receive two emails saying "You are unsubscribed from the mailing list blah". At this point search for that user in the members list under the mailing list administration page, no result is returned. This means this user is automatically deleted from the members list by the mailman. Can anyone tell me why this could happen?? I really need urgent help on that. Thank you very much! -- View this message in context: http://old.nabble.com/Mailman-automatically-unsubscribe-user-without-permis… Sent from the Mailman - Users mailing list archive at Nabble.com.

2 1

disable a mailing list
by Stoyan Angelov Sept. 19, 2010

Sept. 19, 2010

hello all, i want to temporary disable one of my mailing lists while keeping the archives available. i run mailman 2.1.12 with sendmail. i was thinking about doing the following: . remove the appropriate aliases from /path/to/aliases (redirecting the <mailling-list>-owner of the affected list to some real address) . move the /path/to/mailman/lists/<disabled-list> directory to a temporary location is this the proper way to disable a list? is there anything else that needs to be done? greetings, Stoyan

3 5