Mailman-Users January 2015

mailman-users@python.org

35 participants
40 discussions

Add "sender's name/email" to BODY of mail as header?
by Mal 16 Feb '21

16 Feb '21

I want all mails sent to the list to come from the list's email address... But, in this case, if the user forgets to sign their name at the bottom of their mail body, effectively the mail to the list is anonymous...! Is there a way to add the user name (or email address) to the top of each mail so that the mails have the name of the sender, while the mail itself comes from the list address? I have looked high and low for an answer, but noone seems to have the solution. Thank you! Mal

9 14

Mailman CGI Error-Group mismatch error
by Wang, Mary Y 09 Sep '20

09 Sep '20

Hi, I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error? "Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Group mismatch error. Mailman expected the CGI wrapper script to be executed as group "nobody", but the system's web server executed the CGI script as group "apache". Try tweaking the web server to run the script as group "nobody", or re-run configure, providing the command line option `--with-cgi-gid=apache'." Thanks Mary

3 3

Mailman 2.1.18-1 not respecting add_virtualhost
by Chris Miller 03 Jul '15

03 Jul '15

Hello, we recently updated our (vhost patched) Mailman installation from 2.1.14 to 2.1.18-1 (https://launchpad.net/~msapiro) in order to workaround Yahoo's recent change to their SPF policy that this version addresses. Virtual mailing list hosting worked fine up until this upgrade. Here is an example of our mm_cfg.py : VIRTUAL_HOSTS.clear() DEFAULT_EMAIL_HOST = 'list.ourdomain.com' DEFAULT_URL_HOST = 'list.ourdomain.com' DEFAULT_URL_PATTERN = 'http://%s/mailman/' VIRTUAL_HOST_OVERVIEW = On add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost('list.customerdomain.com', 'customerdomain.com') If we change the default values above and run the below command, the available mailing lists move from the old default to the new. bin/withlist -l -a -r fix_url -- All add_virtualhost configuration lines are ignored. Since withlist is able to read the changes in our mm_cfg.py, this does not strike me as an issue with our configure options which were limited : ./configure --prefix=/usr/lib/mailman --with-var-prefix=/var/lib/mailman --with-cgi-gid=apache I am unaware of a method we can use to further debug this, such as a command that would effectively dump out Mailman's configuration options, thus validating if it is even reading the add_virtualhost configuration lines. -- Regards, Chris Chris Miller President - Rocket Scientist ScratchSpace Inc. (831) 621-7928 http://www.scratchspace.com

2 11

Announcing the new wiki.list.org
by Barry Warsaw 03 Mar '15

03 Mar '15

I am very happy to announce our new wiki! If you go to wiki.list.org you will see our shiny new Moin-based wiki. We are retiring the old Confluence-based wiki at the end of February. Until then, you can access it at old-wiki.list.org. Our very huge thanks go to Paul Boddie who did the amazing conversion work, almost single-handedly reverse engineering the Confluence dump through several iterations. Of course, our thanks also go to John Viega, owner of the list.org domain and Mailman's inventor for helping us get the DNS flipped over. Thanks too to everyone who gave feedback on the new wiki, contributed to the old wiki, and continue to help edit this important resource for the Mailman community. Our thanks also go to the Python Software Foundation and the PSF infrastructure team for providing us with the virtual machine hosting our new wiki. If you had write access to the old wiki and want it again for the new wiki, you will have to re-submit a request to mailman-cabal(a)python.org. Please be sure to register with wiki.list.org and provide us with your user name. With this conversion, I am happy to say that GNU Mailman is finally fully hosted on free software. While we appreciate the years of service donated to us by Atlassian and Contegix, it's important that we set an example by utilizing an entirely free software stack for our development and outreach. The wiki was our last remaining non-free bits. Let the gardening begin! Cheers, -Barry (On behalf of the GNU Mailman steering committee) P.S. We are working on the SSL certificate for the new wiki. Stay tuned.

3 3

Re: [Mailman-Users] Is there tool convert archived files/directories into a mbox file?
by Mark Sapiro 02 Mar '15

02 Mar '15

On 05/10/2013 06:35 AM, Xie, Wei wrote: > > Here we have one customer to request migrating all old archived files of > mailing list ‘kinejapan’ under directory > /usr/local/mailman/archives/private/kinejapan prior to 2009 (as attached > file) to Yale university. Yale university IT guys needs us to create a > mbox file for these old archived file to be easy for them to run > command ‘archdo migration. > > > > I check there is no file kinejapan.mbox under directory > /usr/local/mailman/archives/private/kinejapan.mbox to match these old > archived files as attached. This mailing list was maintained by our > pre-mailman admin, who passed away 2011, so I do not know why the mbox > file was missing. If ARCHIVE_TO_MBOX is set to 0 in mm_cfg.py, Mailman will not create/update LISTNAME.mbox/LISTNAME.mbox files. > Do you know whether there is a tool/method to convert these old archived > files/directories as attached into a mbox file? Lots of information is lost if there is no .mbox file. You can do as well as anything with cat /usr/local/mailman/archives/private/kinejapan/*.txt > kinejapan.mbox -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 9

Admin Requests Not Working
by Dennis Putnam 05 Feb '15

05 Feb '15

I'm on to the next layer of the onion for my migration. Now I have admin/moderator requests to handle. When I click the appropriate radio buttons and click the submit button, nothing happens. The page refreshes but the requests remain. TIA.

2 7

Moving lists with large archives to new server
by Andrew Hodgson 31 Jan '15

31 Jan '15

Hi, I am required by my host to change server hardware as the current hardware is out of support and needs replacing. I will be going from 32-Bit Debian Wheezy to 64-Bit Jessy when it is released, and will probably upgrade to Mailman 2.1.19 from 2.1.18-1 using my own custom made packages. All the configs for the system will be pushed via Puppet including ~/Mailman/mm_cfg.py, and ~/lists and ~/data can be copied over very quickly. My question revolves around the list archives. If I start Mailman up before they are copied across, it is likely there will be waiting messages and these will get archived to a new mbox file. I want to reduce downtime in moving the lists, but the mbox files are around 25GB, and there are a couple of lists which take the majority of that. I was going to index the messages once the mbox files are copied over, but what is the smartest way to get these moved without downing Mailman for too long? Thanks. Andrew.

2 1

Mailman 2.1.19 release
by Mark Sapiro 29 Jan '15

29 Jan '15

I am pleased to announce the first release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. There are also bug fixes. See the attached README for more details. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. I plan to release the final 2.1.19 release at the end of February, and it would be good to have as many i18n updates as possible by then. 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 http://mailman.sourceforge.net/ Mailman 2.1.19rc1 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

how to subscribe users of one list to another when they post
by Danil Smirnov 29 Jan '15

29 Jan '15

Hi Mark, Barry and others! Could you please advice whether it's possible to automate situation when users of particular list post to some sibling list which they are not member of: - to invite them - to subscribe them silently - to subscribe them with moderator approve Is it possible with 2.x/3.x version? Danil

2 1

Archiving problems
by Bill Christensen 28 Jan '15

28 Jan '15

Hi folks, I recently discovered that all my lists stopped archiving back in October. I have no clear idea as to what caused that, but I suspect that it may have occurred as part of some hardware and software upgrades I did around that time. I'm still stuck back at Mailman 2.1.13 because the port system I use hasn't updated in ages and I haven't had time to tackle it myself. I was able to bring most of the archives up to date manually, but one fairly active one with public archives is still only showing through October 2014. When I run that manually it shows that it's processing posts beyond the last one seen in the web-visible archives and updates the index for 1st quarter 2015, but still no visibility and the files in archive/public aren't updated. The files in archive/private *are* updated... How do I make the public archives reflect what's in private? Thanks.

3 10