Mailman 3 June 2016 - Mailman-Users

Using cronjob to remove and add members to a mailing list
by Jerry Barnabee 10 Aug '22

10 Aug '22

I want to be able to run a cronjob on my server that uses a php script to add new users and/or remove users from a mailing list. Not having any luck finding any simple examples. My thought is that the php script would get email addresses from a database (which I can do) and then feed them to a mailman command line to either add or remove a user. The cronjob is entered via Cpanel. Have several cronjobs that modify databases but have never tried something that would actually execute a unix command. Thanks, Pineyscripter

3 3

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 10 Sep '20

10 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

changing domains on Mailman implementation
by Keith Seyffarth 20 Sep '18

20 Sep '18

Is there an efficient way to change the domain name that mailman is affiliated with? I have two mailing lists that were created for an organization before that organization had their own domain. At the time the organization was sure they did not want their own domain and would not be getting a domain. Since then, they have chosen to get a domain and set up a web site. I would like to move their mailing lists onto their domain. It looks like the process for this is: 1) get the list of subscribers 2) delete the mailing list from the one domain (losing the archives) 3) create the mailing list on the new domain 4) subscribe the list of subscribers This process doesn't seem too difficult, but I would prefer to keep the archives, if possible. Both domains are on the same server, running CentOS7 and PLESK 12.5, if that makes a difference. Thanks, Keith

2 2

mailman not respecting /etc/postfix/transport ???
by Steve Wehr 11 Sep '16

11 Sep '16

I have about 100 mailing lists all using the domain name tunedinweb.com. All the commands to subscribe, etc, come to something(a)tunedinweb.com which come to my server and are processed by mailman. But I also have real email boxes @tunedinweb.com. Those are hosted off my server. So in order to make both mailman and my email work I have postfix configured with tunedinweb.com listed in the mydomains file, but have setup a transport file to tell postfix to redirect any email for something(a)tunedinweb.com to the server where that email is hosted. With lines in transport that look like this: steve(a)tunedinweb.com smtp:mx.emailsrvr.com stevew(a)tunedinweb.com smtp:mx.emailsrvr.com This is all working fine. The issue is that my email address steve(a)tunedinweb.com is also a member of several mailing lists. When mailman tries to send to steve(a)tunedinweb.com I see this error message in the postfix log /var/log/maillog: Jun 6 17:02:08 166941-web1 postfix/smtpd[25836]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 <steve(a)tunedinweb.com>: Recipient address rejected: User unknown in local recipient table; from=<tunedin-temp-bounces+steve=tunedinweb.com(a)tunedinweb.com> to=<steve(a)tunedinweb.com> proto=ESMTP helo=<166941-web1.tunedinweb.com> So it seems that mailman is not respecting the /etc/postfix transport file settings. I want mailman to send mail for those addresses specified in the transport file to the server where that email is hosted. I must be missing something. Can someone explain what is going wrong. Thanks again for your help. _____________________ Steve Wehr Tunedin Web Design <http://www.tunedinweb.com/> 845-246-9643

2 11

Not able to access Mailman web interface
by Jewel Brueggeman-Makda 30 Jun '16

30 Jun '16

I am trying to setup a new instance of Mailman 2.1.22 on RedHat 7.2 using Apache 2.4. The plan is to move mailman from an old server to the new one. For the moment I am just trying to get it setup. Apache's home page is fine but as soon as I try to go to webserver/mailman/listinfo I get the generic "Bug in Mailman" error page. There is nothing in the mailman logs to help me. The httpd logs only point to a cgi error. One example of the lines in the logs are: [cgi:error] [pid 20032] [client 198.256.23.205.54:12345\ AH01215: \tHTTP_ACCEPT_ENCODING: gzip, deflate Below is what I have in my httpd.comf file: <Directory "/var/www"> AllowOverride None Require all granted </Directory> <Directory "/var/www/html"> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> <Directory "/usr/local/mailman/cgi-bin/"> AllowOverride None Options None Require all granted </Directory> Alias /pipermail/ /usr/local/mailman/archives/public/ ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ I have ran bin/check_perms -f and things look good. I will show my permissions just in case I am missing something. drwxrwsr-x. 4 root mailman 33 Jun 28 14:45 archives drwxrwsr-x. 2 root mailman 4096 Jun 29 09:31 bin drwxrwsr-x. 2 root mailman 4096 Jun 29 09:30 cgi-bin drwxrwsr-x. 2 root mailman 4096 Jun 29 09:30 cron drwxrwsr-x. 2 root mailman 108 Jun 29 09:30 data drwxrwsr-x. 2 root mailman 4096 Jun 29 09:30 icons drwxrwsr-x. 3 root mailman 20 Jun 28 16:28 lists drwxrwsr-x. 2 root mailman 81 Jun 29 10:49 locks drwxrwsr-x. 2 root mailman 43 Jun 28 16:32 logs drwxrwsr-x. 2 root mailman 20 Jun 29 09:30 mail drwxrwsr-x. 11 root mailman 4096 Jun 29 09:30 Mailman drwxrwsr-x. 40 root mailman 4096 Jun 28 14:45 messages drwxrwsr-x. 2 root mailman 6 Jun 28 14:45 pythonlib drwxrwsr-x. 11 root mailman 4096 Jun 28 16:32 qfiles drwxrwsr-x. 2 root mailman 4096 Jun 29 09:30 scripts drwxrwsr-x. 2 root mailman 6 Jun 28 14:45 spam drwxrwsr-x. 41 root mailman 4096 Jun 28 14:45 templates drwxrwsr-x. 4 root mailman 4096 Jun 29 09:31 tests Thanks! Jewel

2 2

admindb web forms not making changes
by David Magda 30 Jun '16

30 Jun '16

Hello, I received moved a Mailman instance (via rsync) from a Debian 6 machine to Debian 8, and while most things are generally okay, some the admin web forms don't appear to be working anymore (under Apache 2.4). I've run "check_perms" and it comes back clean. So I can create a new list ("dmtest1") just fine, and the owner gets a message with the new password and such. I then use another e-mail account to send a message to "dmtest1-subscribe" which sends back to corresponding "confirm" e-mail; I click on the confirm URL and that works. The owner / moderator of the list then gets the 'new sub req' message. I click on the "at your conv" link with "admindb/dmtest1", enter the password from the creation message, and I get the list of sub requests. However, when I select "Approve" and click on "Submit All Data", I get sent to the "Dmtest1 Moderator Authentication" page to enter the password. The following appears in Apache's access.log when I click on 'submit': 10.10.10.42 - - [30/Jun/2016:08:52:19 -0400] "POST /mailman/admindb/dmtest1 HTTP/1.1" 200 1268 "http://lists.[foo-example].org/mailman/admindb/dmtest1" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0" There's nothing in Apache's error.log, and nothing in /usr/local/mailman/logs/. Re-entering the password and approving/submitting is just a loop. Another list admin says that they have some messages with bodies that are bigger than the list limit, and that "discard" does not work. He says that "the page just refreshes". Any ideas? Regards, David

2 1

Number of Recipients
by Julian Kippels 24 Jun '16

24 Jun '16

Hi, I have a question regarding the number of recipients per mail. If I have a list with 50 entries, does mailman send one mail with 50 recipients, or 50 mails with one recipient each? Thanks, Julian -- --------------------------------------------------------- | | Julian Kippels | | M.Sc. Informatik | | | | Zentrum für Informations- und Medientechnologie | | Heinrich-Heine-Universität Düsseldorf | | Universitätsstr. 1 | | Raum 25.41.O1.36 | | 40225 Düsseldorf / Germany | | | | Tel: +49-211-811-4920 | | mail: kippels(a)hhu.de | | jabber: jukip100(a)xmpp.hhu.de ---------------------------------------------------------

3 2

moderator page behind nginx with SSL
by John Griessen 24 Jun '16

24 Jun '16

The rest of mailman version 2.1.22 is working fine with SSL and some rewriting by nginx and yet https://cibolo.us/mailman/admindb/open_electroporator gives a message "will be sent over an insecure connection" when I seta button to discard and then do the submit all data button. Is there a way to use SSL here? Or... will I need to disable SSL for this page to get that submit to work?

5 10

Making a Case for Upgrading MailMan from 2.1.17
by Dave Nathanson 24 Jun '16

24 Jun '16

I'd like some help in making a case to convince my hosting company to upgrade from Mailman 2.1.17. I run several email lists for clubs, these are discussion lists that get up to 20 messages per day, and include up to 150 members. Replies are directed back to the list. My primary issue with MM 2.1.17 is about list messages from members who don't have their human names configured into their email clients, resulting in a list message from an unknown. It is just from "via listname <listname(a)example.com>" Since I'm still stuck on 2.1.17. I don't know what I am missing in the newer versions. I just know that it's been over 2 years since 2.1.17 which has an annoying omission due the the whole DEMARC thing. What are the advantages of upgrading beyond 2.1.17? How best to make a good case to convince them to upgrade their MailMan? What version should I ask for? Thanks! Dave Nathanson Mac Medix

3 3

Mailman-Users June 2016