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 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 mark it as accept then submit, the request returns 200, the page
reappears and the message is still there. Why?
Things I wonder if they are related:
* Under the message, it says "The sender is now a member of this list"
* The post goes over http, but the get requests are over https.
It's a private list, running mailman 2.1.13, the url goes like this:
If there's not a good answer, it's not a big deal, just curious. I could
discard the message and see what happens too.
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
Hi Mark, etc,
I’ve been a happy user of Mailman for years via a webhost on a shared server which runs cPanel. I’m the list owner for various lists, and in general it’s been working well. The current Mailman version the webhost have is 2.1.23.
But in recent months I’ve noticed that, as list owner, when I subscribe or unsubscribe someone, instead of just receiving an email with the subject:
“<listname> subscription notification”
“<listname> unsubscribe notification”
I receive an email with the subject:
“Bounce action notification”
“This is a Mailman mailing list bounce action notice:
List: Bro [for example]
Member: mylistadminaddress(a)mydomain.com<mailto:firstname.lastname@example.org> [for example]
Action: Subscription bounce score incremented.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at mailman(a)somedomain.com<mailto:email@example.com>.” [for example]
And that email contains an ATTACHMENT which has the subject:
“<listname> subscription notification”
“<listname> unsubscribe notification”
- This didn’t used to happen with these same lists, and I don’t know what’s triggered the change in behaviour.
- Even if I change the list “owner” address to another of my addresses, it still happens.
- I have admin_notify_mchanges set to “Yes”.
- I don’t have any moderators set up.
Q1. Is this a known issue?
Q2. What’s the likely cause of this problem suddenly starting to happen?
Q3. What’s the likely solution?
Q4. Do you need any more info to troubleshoot the cause of this? If so, what, exactly?
I hope I may have solved some postings being shunted on a few of my lists,
cd /usr/local/mailman; unshunt qfiles/shunt
I discovered 3 lists had missing '\n', shown with
cd /usr/local/mailman/lists; config_list -o - ListName
bounce_matching_headers = """# Lines that *start* with a '#' are comments.
cd /usr/local/mailman/lists ; config_list -o ~/tmp/ListName ListName
vi ~/tmp/ListName ; config_list -i ~/tmp/ListName ListName
& I hope the shunting will stop.
I did autopsy snapshots of /usr/local/mailman before & after last unshunt,
if anyone feels like telling me what to look for.
Unfortunately the corrupt bounce_matching_headers lines in configuration
were undetected by these automatic checks
cd /usr/local/etc/rc.d; ./mailman stop ; ./mailman start
cd /usr/local/mailman/lists ; ../bin/check_db -a
cd /usr/local/mailman/lists ; ../bin/check_perms
The errors probably derive from a fumbled edit by me using an older mailman.
I'll do more visual inspection on my most troublesome list.
Julian H. Stacey, Computer Consultant, BSD Linux Unix Systems Engineer, Munich
Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
I installed Mailman 2.1.16 today on Ubuntu 14.04.
We are using the email domain lists.xxx.com which worshippers well for mailing lists, however the main domain I am using for normal email is xxx.com.
The problem arises when trying to contact Mailman admin following this instruction:
“If you are having trouble using the lists, please contact mailman(a)lists.xxx.com.xn--ivg
Is there a possibility to setup the xxx.com domain for this sentence, or if not, make an alias so that mailman(a)lists.xxx.com is forwarded to mailman(a)xxx.com
According to the documentation, I can set Privacy Options > Sender Filters > Accept_these_non-members to allow members of other local lists to post. It is not working for me.
I added: @digital to Accept_these_non-members (digital(a)parishplayers.org is a valid, working list)
It still holds mail from people on the digital mailing list.
Am I doing something wrong?
F × S = k (the product of freedom and security is a constant)