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?
This is a weird one. I think of myself as knowing my way around Mailman
pretty well for a user/admin/installer/upgrader. I'm upgrading to a
Debian 9 system from CentOS 6.5. Debian's Apache configs took a bit of
getting used to, but I actually like them better. It uses Apache 2.4.2.
I wanted to install Mailman from source, since the latest version is
2.1.26, Debian has 2.1.23, and IIRC that's too old to have some screen
reader optimizations I want. So I built, installed, all working well. I
copied over the Mailman config from my CentOS system to use in Apache,
making some changes so it'd work under 2.4.2. Here it is:
# httpd configuration settings for use with mailman.
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
Require all granted
Alias /pipermail/ /var/lib/mailman/archives/public/
Options Indexes MultiViews FollowSymLinks
Require all granted
# Uncomment the following line, to redirect queries to /mailman to the
# listinfo page (recommended).
# RedirectMatch ^/mailman[/]*$ /mailman/listinfo
The problem is that the CGI isn't working. If I go to
http://temphostname/mailman/listinfo/mailman for example, Apache says
/usr/lib/mailman/cgi-bin/listinfo/mailman doesn't exist. If I just go to
/mailman/listinfo I get an Elf binary thrown at me, rather than the page
saying there are no advertised lists. If I do the same thing from the
server using the Lynx web browser, I get the same binary thrown at me,
with a page title, "Mailman CGI error!" It sounds to me like Apache
2.4.2 isn't seeing that /usr/lib/mailman/cgi-bin is, in fact, CGI
scripts, and is trying to treat them like regular files. Has something
else changed between Apache versions?
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 220.127.116.11] Timeout
>> waiting for output from CGI script
>> /usr/local/mailman/cgi-bin/admin, referer:
>> [Fri Aug 26 19:59:23 2016] [error] [client 18.104.22.168]
>> 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 would like to "freeze" an existing mailing list: I want to keep the
mailing list but I want no one newly subscribe the list. Can you
please anyone tell me how I can implement it?
SRA OSS, Inc. Japan
We're currently dealing with some Subscribe Spam. Dealing with it, I
encountered a problem I need help with:
I used Mark's scrip list_pending
(https://www.msapiro.net/scripts/list_pending) to find out how many
Subscriptions we got and which adresses were used. I iterated over all
lists I got from list_lists --bare and took just the ones with "type:
S". Turns out we got 66608 subscriptions from 66560 different adresses.
Luckily, they all match the regex \w*\+\w*(a)gmail\.com, so I tried to
wipe the mess whith another script of Mark, erase
It works nicely for a bunch of lists, but I don't get why it doesn't
work with all of them. Looking more closely I found in
/var/lib/mailman/lists/<listname> the pending.pck file the script is
Does someone have an idea why it might not work for all lists?
I've been assigned the task of attempting to secure our current implementation of GNU MailMan.
Have any of you out there done this?
What did you do?
Some of the initial items that have been directed my way:
1. Can archiving be totally and permanently be eliminated?
2. How and where are the passwords stored?
3. Can user passwords be eliminated and have the list administrator make any user adjustments which should not be necessary?
4. Does the website have to run in http: since passwords are entered at points in the interactions?
Thanks for your guidance and thoughts.