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 18.104.22.168] Timeout
>> waiting for output from CGI script
>> /usr/local/mailman/cgi-bin/admin, referer:
>> [Fri Aug 26 19:59:23 2016] [error] [client 22.214.171.124]
>> 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.
On one of my lists I'm seeing some spam from non-subscribers getting
through. It appears that the trick is to put a subscriber's address in the
"real name" of the sender. E.g., this got through, without being held for
moderation, on a list with generic_nonmember_action = discard (emails of
the innocent obfuscated):
*From:* "xxx(a)johnxxx.com <jgl(a)johngreenwaltlee.com>" <enrollment(a)ekonek.com>
*Date:* July 18, 2018 at 5:27:24 PM CDT
*To:* <listname(a)server.org <osg-l(a)cool.conservation-us.org>>
*Subject:* *[OSG-l] No. PL-01-17923 AIC Objects Specialty Group Discussion*
*Reply-To:* My List's Name <listname(a)server.org
Invoice No: No. PL-01-17923
Billing Date: Jul 19, 2018
Due Date: Jul 22, 2018
Amount Due: 1,047.48
etc. (I'm avoiding sharing the links that follow). xxx(a)johnxxx.com IS a
subscriber on the list. However enrollment(a)ekonek.com is not. Yet this
message went straight through, as if it had been sent by a subscriber.
I've looked at the archives of mailman-users and it looks like--from a very
a) this cheap trick should not be sufficient to allow the message through
b) the content of the message as delivered to the list may not reflect the
exact contents/metadata of the message as it was sent.
Still, I don't really know what else could be going on here, or how to
I receive about 8 bounce messages a day for one of my lists from people
trying to post to it who aren't members.
The list is set up as private so not sure how these spammers find it.
I've been to the bounce page but can't work out how to stop these
messages but allow bounce messages from members?
Jaws certified 2016
Email, iMessage & FaceTime
I'm trying to submit a form or two from a program and I can't quite
understand Mailman's form handling, this with Mailman 2.1.23.
What I've done is a little program that does something simple: it first
authenticates [and gets the appropriate cookies], then I GET the
mass-removal page [to get its csrf_object. Then I do a simple POST with
just three form fields:
csrf_object=> <whatever it was in the GET of the page>
unsubscribees => the email address,
'setmemberopts_btn => 'Submit Your Changes'
The response I get back is the original page - no error and no success, just
the mass-removal page again. It is what would happen if you clicked on
the submit button without giving it anything to do
I've also tried a similar POSTing with every field from the form included,
and always the same: a 200 response and I get the mass-removal page back
again. I'd look at the code, but I'm a perl guy -- never messed with python.
What does Mailman do to when receiving a POST to decide if there's
something to do or not? THANKS!
-- Too many people; too few sheep --
Hello, until recently I had my mailman web configuration in a directory in my
www domain, like www.mydomain.de/mailman. Now I changed the structure to have
an URL like lists.mydomain.de. I also changed the apache configuration and the
/etc/mailman/mm_cfg.py file. This kind of works, I can access my admin panel
fine. But some internal urls like the mailing list archive still refer to the
old www url. What must I do to clean that up?