Mailman 3 April 2016 - Mailman-Users

Hide list address?
by Ricardo Kleemann 17 Nov '23

17 Nov '23

Hi, Is there any way to configure Mailman such that, for an announcement-only type list, when a message is sent to the list, the To: shows the member's address, rather than the list address? Some list software allows the ability to hide the list address itself, so that address is not advertised. I couldn't find any configuration specific to that.

7 6

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 21 Sep '18

21 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

Logging sequence?
by Mark J Bradakis 21 May '16

21 May '16

Mailman is not working. Messages come in, nothing goes out. Logs are useless, providing no clue as to what is happening. In a working mailman system. what is the sequence of logging that a message would go through? mjb.

3 3

Seeking Information re: mailman admin page bug
by Holly Hart 01 May '16

01 May '16

Hello, I work for an organization that uses several Mailman email lists which I administer. Starting a couple weeks ago (apparently), the admin request page commands have ceased to function: messages held in the queue remain stuck there, regardless of attempts to discard, reject or accept. The source of the issue is apparently on Python's end. Unfortunately,there is no way to receive a timely response to what should be a basic inquiry (and probably something easy to fix). Have others experienced this bug? Does anyone here know how to fix this? -- Holly Hart Program Coordinator, Iowa Shares www.iowashares.org 319.338.1446 (office) 319.331.91616 (cell)

3 2

RBL Management for new list/IP
by Jim Ohlstein 29 Apr '16

29 Apr '16

Hello, This is not so much a technical question as advice seeking. My apologies if it isn't appropriate for this list. I am new to mailing list management, though not new to mail server management. I've never run into this problem. Background is that I am tasked with creating an announcement list for a group. I'm using a dedicated IPv4 which I have controlled for two months and not previously used for outgoing email. I have not idea what its prior "reputation" was. Mailman settings are pretty much default. I have proper SPF and rDNS records. We have added just short of 1000 members, all by their request at the web interface. A few test messages went out about 4-5 days ago. Since then the only outgoing mails have been signup confirmations and messages to me as list owner. Despite the relatively low volume, my IP keeps getting listed at Spamhaus CSS (https://www.spamhaus.org/css/). I can manually de-list it but it seems as though whenever we send out any mail we get re-listed. I have tried contacting them but gotten nowhere. The only other RBL where we are listed is http://www.dnsblchile.org/. I put in a de-listing request with them over the weekend but they only work during the week. Has anyone dealt with this, and if so, can you offer any ideas? -- Jim Ohlstein "Never argue with a fool, onlookers may not be able to tell the difference." - Mark Twain

2 5

Bounce Processing
by Richard Robbins 22 Apr '16

22 Apr '16

I recently switched my mailman host to a new provider. One of my users is now encountering problems that he hasn't had before. When he sends a message to a list an error message is generated that is in the following form: From: Mail Delivery System <Mailer-Daemon(a)cloud1.emwd.com> To: announce-bounces(a)usml.net Cc: Date: Thu, 14 Apr 2016 13:09:24 -0400 Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [subscriber's email address appeared here and I deleted it] host mxa-00149702.gslb.pphosted.com [67.231.156.216] SMTP error from remote mail server after end of data: 550 5.7.0 You are not authorized to use our domain as a sender address. Action: failed Final-Recipient: rfc822; [subscriber's email address appeared here and I deleted it] Status: 5.0.0 Remote-MTA: dns; mxa-00149702.gslb.pphosted.com Diagnostic-Code: smtp; 550 5.7.0 You are not authorized to use our domain as a sender address. When I asked my host about this I was told that this is an SPF configuration issue and that the sender needs to adjust relevant DNS records. The subscriber spoke to his IT person who said that this appears to him to be a blacklist issue and that the host needs to make an adjustment. Meanwhile, mailman has now removed the subscriber from the mailing list and I had to put him back on, but I assume he will be deleted soon. I'm not really sure what to do. Any advice on how to proceed?

4 8

New user - SMTP failure
by Jim Ohlstein 22 Apr '16

22 Apr '16

Hello, I am trying to set up a new system for a new list but finding that outgoing mail is failing. The setup I have is FreeBSD 10.3 in a jail with localhost at 10.0.250.37. I have confirmed that routing in and out of the jail are correct by sending mail from it via command line, via telnet, and by posting to a newly created list. Unfortunately those messages are not relayed out, nor are list invitations. The system is Mailman 2.1.21, Postfix 3.1.0, and Python 2.7.11. I see this in logs/smtp-failure: Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection refused, msgid: <mailman.0.1461205537.18941.c2-list(a)lists.my.domain> Apr 20 23:07:27 2016 (19197) delivery to my(a)email.address failed with code -1: [Errno 61] Connection refused Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection refused, msgid: <mailman.0.1461205853.19010.c2-list(a)lists.my.domain> Apr 20 23:07:27 2016 (19197) delivery to my(a)email.address ailed with code -1: [Errno 61] Connection refused Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection refused, msgid: <mailman.0.1461206277.19201.c2-list(a)lists.my.domain> Apr 20 23:07:27 2016 (19197) delivery to my(a)email.address failed with code -1: [Errno 61] Connection refused Apr 20 23:07:27 2016 (19197) Low level smtp error: [Errno 61] Connection refused, msgid: <mailman.0.1461207076.19195.mailman(a)lists.my.domain> Apr 20 23:07:27 2016 (19197) delivery to my(a)email.address failed with code -1: [Errno 61] Connection refused Nothing shows up in Postfix logs for these refused connections. And lots of lines that look like this in logs/post: Apr 20 23:07:26 2016 (19197) post to c2-list from c2-list-bounces(a)lists.my.domain, size=583, message-id=<mailman.0.1461205085.18509.c2-list(a)lists.my.domain>, 1 failures Scanning Google I saw issues where there were errors in /etc/hosts. That file is world-readable and there is a correct entry for localhost. I have also confirmed that Postfix is listening on 25 on localhost using telnet and sockstat: # telnet localhost 25 Trying 10.0.250.37... Connected to localhost. Escape character is '^]'. 220 lists.my.domain ESMTP Postfix The above works for root and for a non-root user. # sockstat | grep 25 postfix smtpd 19679 6 tcp4 10.0.250.37:25 *:* root master 19170 13 tcp4 10.0.250.37:25 *:* I'm at a loss as to where to look next. Thanks for any input. -- Jim Ohlstein "Never argue with a fool, onlookers may not be able to tell the difference." - Mark Twain

2 1