Mailman 3 October 2013 - Mailman-Users

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

17 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

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

Making a Mailman legacy archive searchable?
by David Roth 23 May '14

23 May '14

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

7 8

MM-2.1.15: Small bug regarding the "request forgery check"
by Ralf Hildebrandt 12 May '14

12 May '14

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

4 7

accessing relay mailman server from its own network
by Anne Wainwright 04 May '14

04 May '14

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

2 13

Mailman 2.1.16 release.
by Mark Sapiro 23 Nov '13

23 Nov '13

FYI, I will be releasing 2.1.16rc1 in a few days with a target of a final release in early September. I believe the release will be very solid and stable. The main purpose of the candidate release is to expose any i18n changes so that translators can submit any updates and get them in the final release. There are a few new features, contributed programs, i18n changes and bug fixes, all of which will be announced when the candidate is released. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 10

issue with QMailToaster Mailman implementation
by Fabian Santiago 01 Nov '13

01 Nov '13

Hello all, I've integrated Mailman with my QMT using the wiki instructions provided online by the qmail toaster folks. It all seems to function well except for one thing; when I send email to 'mailman-owner(a)lists.photoblogverona.com', I receive back a failure notice stating: Hi. This is the qmail-send program at mail.photoblogverona.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <postmaster(a)lists.photoblogverona.com>: This message is looping: it already has my Delivered-To line. (#5.4.6) Where should I be looking or what to look at? Thanks. My actual email domain is photoblogverona.com. the lists sub domain was setup as part of the mailman integration. Could this have something to do with it? I've also emailed the people involved with QMT but figured I would also ask here as well. thanks for your help in advance. -- Fabian S.

2 1

2.1.15 cPanel issue
by Malcolm Austen 01 Nov '13

01 Nov '13

Yes, I know you can't support cPanel installations but you may have some ideas that will be useful when I finally resort to sending in a support request that may get nothing better than a 'delete & recreate' response :-( I think my cPanel provider has just upgraded to MM 2.1.15 and I have found that I have a problem ... I had changed the list-info and user-options pages and now, not only do those pages result in 'Bug in Mailman version 2.1.15' displays, so do my attempts to edit them through the admin interface. I have noticed that a cPanel backup logs 4 sets (I have 4 lists) of permission failures for my lists suggesting that the pages I have changed no longer have the right permissions. I seem not to have file level access to the mailman hierarchy, so I guess I need advice as to what permissions I need to ask them to manually set on which files or folders. I'd like to make my request specific enough to avoid having the lists reset and the archives and/or membership lists discarded. Thanks for any advice, Malcolm. -- Using Opera's mail client: http://www.opera.com/mail/

3 4

Automatic update of list members while making it possible to (un)subscribe manually
by Henrik Rasmussen 24 Oct '13

24 Oct '13

Before I start making my own script, I was wondering whether the feature I need is already available. I run Mailman version: 2.1.5. I have two types of Mailman lists * some of which members are allowed to subscribe or unsubscribe as desired (though some list administrators still need to approve subscriptions) * and some lists, which members of a certain group must be subscribed to, as long as they are part of the group. The group-members e-mail addresses are extracted from the group and pushed to the list using " add_members -wn -r /tmp/group_members.lst mailman-list". Likewise are those, no longer part of the group, removed from the list using "remove_members -n -N -f /tmp/group_exmembers.lst mailman-list". Now I want to combine those features, having lists that are updated automatically using above method, but at the same time making sure that group members, who have manually opted-out from the mailinglist, won't be subscribed to the mailinglist automatically again, and also making sure that people, who are not part of the group, have the ability to opt-in to the mailinglist without being removed by automatic procedure. Is there a neat way of accomplish this already? Henrik Rasmussen

3 2

Mailman-Users October 2013