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 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
a few weeks ago I upgraded from 2.1.16 (as far as I can remember...) to
2.1.29. Everything seemed to work fine at first. But then I found out
that a lot of posts - actually far more than half of them - aren't
archived any longer. What logging the errors tells me is this:
Feb 28 12:29:02 2019 (3123) Uncaught runner exception: 'ascii' codec
can't decode byte 0xb5 in position 26: ordinal not in range(128)
Feb 28 12:29:02 2019 (3123) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 77, in _dispose
File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 216, in
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 596, in
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 640, in
author = fixAuthor(article.decoded['author'])
File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 63, in
while i>0 and (L[i-1] in lowercase or [error message stops right
As I read in a previous thread the reason for this may be non-ascii
compliant characters in the post, especially the "from:"-line. But why
would Python or Mailman now all of a sudden use ASCII instead of UTF-8
in the first place? And if so: How can I change that behaviour?
I am using Python 2.6.6 on a Centos 6 system. The output of
/usr/lib64/python >>> import string >>> string.lowercase is
'abcdefghijklmnopqrstuvwxyz' (as it is supposed to be).
Any help would be appreciated. Thank you
We have a problem since we updated from Mailman 2.1.27 -> 2.1.29
(FreeBSD). If we try to add an User on the Webgui "members/add" the Gui
says successfully added and in the logs we see this:
> logs/subscribe:Sep 20 10:04:59 2018 (20772) ugh_panteghini.ch: new
> shouldfail(a)pascalchristen.ch, admin mass sub
The user even get his confirmation mail with the password and link to
his account. But if he tries to log in it says he's not authorized:
> logs/mischief:Sep 20 10:09:48 2018 (33059) Login failure with private
> rosters: shouldfail(a)pascalchristen.ch from X.X.X.X
> logs/security:Sep 20 10:09:48 2018 (33059) Authorization failed
> (private): user=shouldfail(a)pascalchristen.ch: list=ugh_panteghini.ch:
And if I check it with the command line tool the user isn't added:
> ./list_members ugh_panteghini.ch
Sometimes we're able to add an user when we set the "Send notifications
about new registrations to the list owner?" to No. But it's like 50/50
if it works then or not.
Do you guys have any idea whats wrong?
I've been using mailman to send routine announcements for a long time
and more and more what people want is a text message. I've been able to
discover gateways for individual carriers so that I can send to
<number>@<gateway>.<carrier>.com and the subscriber gets a text, so
phone notification which is quick and handy. This has been well
I've been looking at the list of carriers getting longer and have
looked into email to sms services but what I've seen has been
commercial and too expensive.
Is there a collaborative or open source email to sms project? Can anyone
refer me to better information? I've been pretty much just casting
around so far.
In modern fantasy (literary or governmental), killing people is the
usual solution to the so-called war between good and evil. My books are
not conceived in terms of such a war, and offer no simple answers to
----- Ursula Le Guin
Server: Ubuntu 18.01
I have followed these:
% update-rc.d mailman defaults
But still, mailman doesn't start on reboot.
Nothing in the logs suggest any reason.
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)