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'."
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.
TGIF Mailman Gurus,
My current Mailman 2.1.12 server is lists.washlaw.edu and is running on a RedHat vm. I need to move it onto a new server which already has a new instance of Mailman 2.1.22 also on a RedHat vm. I already ran the ./configure command to be the same setup as the OLD server. I have searched the discussion list archives on the steps and am not fully understanding what needs to be done. Below are the steps I do know I need to take but then I am at a loss.
1. Post Postfix, Apache and Mialman on OLD server and NEW servers
2. Tar up the lists and archives from the mailman directory and copy the tar files to the new server
a. tar xvfx /usr/local/mailman/lists
b. tar xvfz /usr/local/mailman/archives
3. Untar the lists and archives onto NEW server
a. tar -xvf lists.tgz
b. tar -xvf archives.tgz
c. Run from /usr/local/mailman/bin ./check_perms -f
4. Run newaliases
I have a list with nearly 45,000 subscribers. When a list owner searches
for a subscriber through the admin interface, she gets a list of addresses,
then a link to follow to get the next 'chunk'. The link leads to
something like the following if I were searching for 'stephanie'.
So, the first chunk is '0' and then the link goes to chunk '1', but it
links back to the top-level admin page.
If you click the chunks of addresses by the alphabetical letters, it will
successfully take you to each section.
Is this a Feature or a Bug ?
I'm using Mailman v2.1.21 on openSUSE Leap 42.1 and received the following email from Cron Daemon:
[Mailman] Cron <mailman@listserv> /usr/bin/python -S /usr/lib/mailman/cron/cull_bad_shunt
Traceback (most recent call last):
File "/usr/lib/mailman/cron/cull_bad_shunt", line 126, in <module>
File "/usr/lib/mailman/cron/cull_bad_shunt", line 121, in main
OSError: [Errno 2] No such file or directory: '/var/lib/mailman/qfiles/shunt/1474407372.553232+5932f7df2b1dccdd77f92f45a8271e33e8f945d8.pck'
Just passing it along in case it's a bug.
I'm going to assume you meant to post to the list, and send there
myself. For security reasons, Mailman lists do not munge reply-to.
Frequently messages contain private information (IP addresses, domain
names, email addresses, and even passwords) that the sender would not
want broadcasted to a publicly archived list.
Adam Morris writes:
> I'm referring to someone who I have banned from subscribing to a mailing
> If I try and subscribe the banned address I get a message saying member
> is banned.
How do you try to subscribe that address? By web or by mail?
In the admin page Privacy Options, there is a ban_list option near the
bottom of the page (this is version 2.1.21, I believe yours was older
so there may be variations). AFAIK that is the only way to ban an
address from subscribing in "stock" Mailman.
Make sure that the member is not in that list. I believe you reported
that you have cleared out that list already, in which case it's
possible that you didn't click the Submit button at the bottom of the
page, and it's still there. I guess it's barely possible that you
cleared the ban_list for a different list than the one you're trying
to subscribe that address to.
If the web interface reports an empty ban list and you attempted to
subscribe by mail, it's possible that there are two Mailman
installations, one handling mail, and the other web (and this one has
no effect on actual list operation). Multiple installations can arise
for a number of reasons such as an incomplete upgrade where either the
mailserver or the webserver was not properly configured.
Otherwise, I don't know what's going on. Perhaps Mark has an idea.