Mailman-Users December 2013

mailman-users@python.org

41 participants
44 discussions

Add "sender's name/email" to BODY of mail as header?

by Mal

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

2 weeks

Mailman CGI Error-Group mismatch error

by Wang, Mary Y

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

5 months, 3 weeks

Re: [Mailman-Users] Is there tool convert archived files/directories into a mbox file?

by Mark Sapiro

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

6 years

Making a Mailman legacy archive searchable?

by David Roth

Is there anything open-source to make a Mailman legacy archive searchable? What would be useful is a way for visitors to a website to be able to search the Mailman archives using a keyword and have it display those mail messages. I'm also thinking of having a tag cloud made up of the most commonly used words from the given Mailman archive. So when one of those tag cloud words is clicked on it lists as an index those messages. Any suggestions? Thanks! David Roth

6 years, 9 months

MM-2.1.15: Small bug regarding the "request forgery check"

by Ralf Hildebrandt

Today I check the subscribers list ("Membership Management... Section") on one of our lists and called up the legend using "Click here to include the legend for this table." After clicking on that link, the page did indeed display the legend, but the page now starts with: Error: The form lifetime has expired. (request forgery check) -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebrandt(a)charite.de Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

6 years, 9 months

accessing relay mailman server from its own network

by Anne Wainwright

Hello, My mailing lists run on a relay server installed as per FAQ 4.88 Accessing the web interface across the internet works fine but accessing while on the host network is not so fine. Instead of the DSL (dyndns) address I use the server name or IP address and all goes fine unless I query the mailing list addresses. Then i am returned to login again and so on ad infinitum. Same if I try to list them. I note that when I mouse-over the menu options the browser bottom line shows the server name (or IP) address that I have used. When I mouse-over the 0-9A-Z membership listing then the DSL forwarding address shows. FAQ 4.29 would indicate that I could change the DEFAULT_URL_HOST setting for existing lists using fix_url.py - in this case perhaps to the IP address? I suppose that would foul up admin access from across the internet but as that is only me we could live with that. Before fools rush in where angels fear to tread - is this the way to go? Maybe there is a route to have the best of both worlds (easy access from the internet and the local network) many thanks in advance anotheranne

6 years, 10 months

Reconfiguring Mailman with different with-cgi-gid

by Jon 1234

Dear all I used the following when setting up Mailman 2.14: ./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=www --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python To upgrade PHP from 5.2 to 5.3 the website hosts have to enable suexec (I don't quite understand this but bear with me!) which breaks Mailman, I think because it runs as a different user to before. Can I reconfigure Mailman using this? ./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=users --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python This is the with-cgi-gid setting that the hosting people suggest, but I would be grateful for confirmation from someone on this expert list. What else would I need to do? Thanks very much in anticipation. Jon

6 years, 10 months

cgi 404

by thufir

I get a 404: thufir@dur:~$ thufir@dur:~$ mail -f Maildir/ "/home/thufir/Maildir/": 3 messages > 1 thufir(a)dur.bouncem 15/581 test Mon, 30 Dec 2013 19:15:31 -0800 2 thufir(a)dur.bouncem 15/581 test Mon, 30 Dec 2013 19:18:16 -0800 3 mailman-owner@dur. 57/2198 Your new mailing list: mailman ? q Held 3 messages in /home/thufir/Maildir/ thufir@dur:~$ thufir@dur:~$ ll /etc/apache2/sites-enabled/mailman lrwxrwxrwx 1 root root 24 Dec 30 20:06 /etc/apache2/sites-enabled/mailman -> /etc/mailman/apache.conf thufir@dur:~$ thufir@dur:~$ even though dovecot-postfix seems to be working well with mailman, so far as I can tell. The fine manual says: "*Problem:* All Mailman web pages give a 404 File not found error. *Solution:* Your web server has not been set up properly for handling Mailman's CGI programs. Make sure you have: configured the web server to give permissions to $prefix/cgi-bin" Isn't there a different URL I can use instead? I seem to recall something along these lines. thanks, Thufir

7 years, 2 months

Folding whitespace

by Joseph Brennan

Happy New Year (almost)! Archives show me that this topic went around a while back but I did not find a complete answer. It's not really a Mailman bug, but a Mailman choice between correct options. When the Subject is folded into more than 1 line, Mailman inserts whitespace in the form of a TAB character, at the start of the continuation lines. Outlook, when unfolding, removes the CR LF but leaves whatever whitespace is there, in this case a TAB, so people tell me it looks ugly. Microsoft, Microsoft... I noticed that in Mailman/Handlers/CookHeaders.py, we go out of our way to change email.header's continuation_ws from the default of one space to be one tab. Both are correct, since the standard just says whitespace, but if we used one space it would trick Outlook into doing the right thing. Why the tab? CookHeaders.py gets pretty hairy so I feel like I'm missing something. Joseph Brennan Columbia University Information Technology

7 years, 2 months

Re: [Mailman-Users] Error from Cron about Mailman on Debian

by Mark Sapiro

On 12/21/2013 12:29 AM, EyeLand wrote: > 1) I receive error > bin/check_perms -f > -bash: bin/check_perms: No such file or directory This refers to Mailman's bin/ directory, probably /usr/lib/mailman/bin/check_perms. > 2) folder not exists > /var/lib/mailman/archives/private/mailman/attachments > > 3) on email I receive error from cron: > > Cron <list@vps1> [ -x /usr/lib/mailman/cron/senddigests ] && > /usr/lib/mailman/cron/senddigests > List: mailman: problem processing /var/lib/mailman/lists/mailman/digest.mbox: > [Errno 13] Permission denied: > '/var/lib/mailman/archives/private/mailman/attachments/20131216' Digest processing for the 'mailman' list is attempting to create the directory /var/lib/mailman/archives/private/mailman/attachments/20131216 into which it will store scrubbed attachments. The process will create the intermediate directories as needed. If /var/lib/mailman/archives/private/mailman/attachments doesn't exist it's because the process didn't have sufficient permission to create it. check_perms -f run as root should fix this. Otherwise, check permissions as below. >> Run Mailman's >> >> bin/check_perms -f >> >> as root. This should fix the problem. If not, all the directories >> >> /var/lib/mailman >> /var/lib/mailman/archives >> /var/lib/mailman/archives/private/mailman/ >> /var/lib/mailman/archives/private/mailman/attachments >> >> should have mode 2775 (drwxrwsr-x) and group equal Mailman's group >> (probably 'list' on Debian, and /var/lib/mailman/archives/private should >> have the same group and either the mode should be 2770 (drwxrws---) and >> the owner should be the web server user (probably www-data) or the mode >> should be 2771 (drwxrws--x). See the Warning: box at >> <http://www.list.org/mailman-install/node9.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months