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
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.
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'."
Hi, This problem is not caused by mailman, but I still want to give it a
shot here. I'm hosting a mailing list on top of mailman. Emails are
supposed to be sent out by AWS ses. However, ses requires that sender
address must be verified, which leads to a problem that emails sent by
subscribers to mailing list cannot be sent to other subcirbers, since their
addresses are not verified. And it is impossible to verified every
subscriber. Are there smtp service providers allowing unverified email
address to send out emails, or do I have other solutions?
Dear Mailman Cognoscenti,
I'm helping one of my list owners send out 5K plus invitations to
students to subscribe to his mailing list. Our current configuration:
Since this was the first time doing this, I suggested breaking the
batch input into 3 groups, 50, 500, and the rest. The 50 went fine,
as did the 500, but the largest batch gave him a generic web server
> Internal Server Error
> The server encountered an internal error or misconfiguration and was
> unable to complete your request.
> Please contact the server administrator, root(a)conundrum.unh.edu and
> inform them of the time the error occurred, and anything you might
> have done that may have caused the error.
> More information about this error may be available in the server
> error log.
I looked at the logs and I couldn't find anything that hinted at what
went wrong. So I asked the owner to send me the last back and I'd
give it a try. I wrote a script that removed folks already subscribed
to his list and split the remaining subscribers up into 6 files with a
thousand records each. I just tried uploading the 1st batch of 1K,
with the following options:
Subscribe these users now... (*) Invite
Send welcome message... (*) No
Send notifications... (*) No
And entered a 7 line paragraph explaining the invitation.
I ended up having the same error happen. Looking at the Mailman logs,
I can't see any difference before or after my submission. In the
HTTPD logs, I see:
>> [Fri Aug 26 19:59:23 2016] [warn] [client 126.96.36.199] Timeout
>> waiting for output from CGI script
>> /usr/local/mailman/cgi-bin/admin, referer:
>> [Fri Aug 26 19:59:23 2016] [error] [client 188.8.131.52]
>> Premature end of script headers: admin, referer:
So is there an inherent limit to the number of invites that can be
submitted via the web form?
As a work around, how would I do large invites on behalf of the owner
from the command line, including the 'extra text' that is allowed via
the web interface?
the UNH Mailing List Server Admins
Bill Costa, senior admin
Is there an efficient way to change the domain name that mailman is
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
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.
I have a mailman installation with over 300 lists. It is cPanel, but
I am the administrator so have access to command line etc.
I have just two lists that receive a bunch of spam subscribes each
day -- hundreds of them, in fact. For some reason -- which is good,
they are held, so don't go through, not quite sure why. Two
questions -- first is there a file I can erase for each list that
will get rid of all the held subscriptions, without breaking anything
else. I tried once, and my installation broke -- don't know if it is
related, but don't want to try again unless I do it right.
Secondly, there is some commonality in the subscribe addresses, are
there strings I can use to discard the subscribes so I never have to see them.
Below are examples, there is a common word, or a common word, a
period ., and another common word, then a plus sign + then a 4 5 or 6
character word, all alpha, and @gmail.com
Here are examples:
If I could knock these out, it would be helpful. This has happened
several times previously, but has always stopped after a few weeks.
This time it has been a couple months.
Finally, I know it is probably too late in the Mailman2 cycle to get
a new feature, but in the web UI, it would be nice if you could
delete all deferred subscriptions. You can do so with deferred
messages, that are held, but not subscriptions.
I?m having a couple of problems with a Mailman 2.1 list.
I want to add several addresses as new subscribers so as a first step
I added one of them using the mass subscription facility in membership
management. Mailman accepted the data but when I subsequently checked
the subscriber list it wasn?t there. This has been the case for two
Today I checked manually that the recipient address was in fact
working and decided to resubscribe using the same method. I enter the
data in the text box (I?ve done this several times) then click on the
"submit your changes" button below and get this message, ?Error: The
form lifetime has expired. (request forgery check)?
This happens without any special delay on my part, not more than a few
minutes. Please advise.
"As long as politics is the shadow cast on society by big business,
the attenuation of the shadow will not change the substance."
-- John Dewey
I see a blank response from a list's email from a user ho say he did
not sent any response. It seems like an automatic response to a read
confirmation, but this response was sent to many lists on our server
(triggering moderation alerts on the other lists, and my attention).
Is it possible that the original sender set the 'confirmation request'
on the MUA and that request propagated past mailman and got into
If yes: Is there a way to intercept and delete these requests on the
Using mailman from Debian 8: 2.1.18-2+deb8u2
Administración de Redes
Facultad de Ciencias de la Alimentación
Universidad Nacional de Entre Ríos
we've been running Mailman for many years and have never had stability
issues, but about a month ago we moved the server from RHEL 5 to RHEL 6 and
to the current version (2.1.25), and since then it has already happened
twice that one of our four OutgoingRunners got "stuck" and stopped handling
mail. When that happens a simple restart of the service does not work.
These processes remained:
mailman 1663 0.0 0.0 233860 2204 ? Ss Jan16 0:00
/usr/bin/python2.7 /usr/lib/mailman/bin/mailmanctl -s -q start
mailman 1677 0.1 0.9 295064 73284 ? S Jan16 35:35
/usr/bin/python2.7 /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:3:4
root@mailman3/usr/lib/mailman/bin]$ strace -p 1677
Process 1677 attached
recvfrom(10, ^CProcess 1677 detached
[root@mailman3/usr/lib/mailman/bin]$ lsof -p 1677
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python2.7 1677 mailman cwd DIR 253,0 4096 173998 /usr/lib/mailman
python2.7 1677 mailman rtd DIR 253,0 4096 2 /
python2.7 1677 mailman 10u IPv6 46441320 0t0 TCP
In both instances the OutgoingRunner was stuck on an SMTP connection. I had
to use "kill -9" to get rid of it.
Any ideas what might be causing that?
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
Apparently our host provider performs spam tests only on outgoing, rather
than incoming - since my spamassassin blacklists don't have any effect.
So I've discovered the filters offered in Mailman after being completely
buried by spammers trying to post to our subscriber only list.
I've started putting these in Sender Filters:
but what is the syntax for blocking domains ending in
etc, other than .com.
I've been reading up on python expressions but at first reading it is a bit
overwhelming - hoping for a simple example.
I've also started adding in words under Spam filters such as:
Wondering if anyone would care to share their lists of filters - or a good