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.
Every now and then, "Mailman 3" is mentioned on this list. As I
understand it, MM 3 is completely different from the current MM 2 we all
are using, and as Mark Sapiro wrote earlier today, questions regarding
MM3 belong somewhere else. And I think I'll be using MM 2 as long as MM
2 is offered by our provider (via the cPanel installation).
However: What is the state of Mailman 2 at the moment? I think it is
still supported and developed. But will this change in the near or in
the distant future?
No, I am not afraid of learning something new - I am just wondering :)
Thank you, Christian
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
Hilfe für Strassenkinder in Ghana: http://www.chance-for-children.org
I have a list administrator who is on gmail. Forwarding held
spam-messages to him does not work, since google rejects mail that has
spam attached. Is it possible to send notification of pending actions
*without* attaching the held message?
I'm using Mailman 2.1.22 packaged by Ubuntu 16.10.
It appears that on one (but I think not all) of my mailing lists,
Mailman is base64-encoding every single message. Yes, including
ones that 100% definitely contain only ASCII characters. Does anyone
know why Mailman would be doing this?
You might say that base64-encoding all messages shouldn't be
a problem, and you'd be partly right. However there is also another
problem: Mailman is getting the line break encoding wrong in its
base64-encoded messages - by which I mean the encoded representation
of line breaks inside the base64 data. As per RFC 2045 s6.8: "line
breaks must be converted into CRLF sequences prior to base64 encoding"
but Mailman is outputting just LF.
The latter problem definitely appears to be a bug in Mailman,
or perhaps the Python 'email' package. The former seems likely to
be a configuration issue, but it's not obvious to me where.