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?
Bug in Mailman version 2.1.26
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information in the Mailman error logs.
I was trying to log in to the mailman pending admin tasks page to
delete an attempted post by a non-member.
in /var/log/mailman/error is:
admin(22004): [----- Traceback ------]
admin(22004): Traceback (most recent call last):
admin(22004): File "/var/lib/mailman/scripts/driver", line 117, in
run_main admin(22004): main()
admin(22004): File "/var/lib/mailman/Mailman/Cgi/admindb.py", line
219, in main admin(22004): mlist.Lock()
admin(22004): File "/var/lib/mailman/Mailman/MailList.py", line 162,
in Lock admin(22004): self.__lock.lock(timeout)
admin(22004): File "/var/lib/mailman/Mailman/LockFile.py", line 243,
in lock admin(22004): self.__write()
admin(22004): File "/var/lib/mailman/Mailman/LockFile.py", line 422,
in __write admin(22004): fp = open(self.__tmpfname, 'w')
admin(22004): IOError: [Errno 2] No such file or directory:
admin(22004): [----- Python Information -----] admin(22004):
sys.version = 2.7.15+ (default, Oct 7 2019, 17:39:04) [GCC
7.4.0] admin(22004): sys.executable = /usr/bin/python
admin(22004): sys.prefix = /usr
admin(22004): sys.exec_prefix = /usr
admin(22004): sys.path = ['/var/lib/mailman/pythonlib',
'/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman',
'/usr/lib/python2.7/dist-packages'] admin(22004): sys.platform =
linux2 admin(22004): [----- Environment Variables -----]
admin(22004): CONTENT_LENGTH: 40 admin(22004): SERVER_NAME:
cleanairplan.ca admin(22004): SERVER_PORT: 10000 admin(22004):
HTTPS: ON admin(22004): HTTP_COOKIE: admin(22004): REMOTE_ADDR:
188.8.131.52 admin(22004): PYTHONPATH: /var/lib/mailman
admin(22004): PATH_INFO: /amsmembers admin(22004):
admin(22004): REQUEST_METHOD: POST admin(22004): HTTP_HOST:
cleanairplan.ca:10000 admin(22004): USER: www-data
admin(22004): CONTENT_TYPE: application/x-www-form-urlencoded
admin(22004): SERVER_PROTOCOL: HTTP/1.0
admin(22004): LOGNAME: www-data
admin(22004): DOCUMENT_ROOT: /usr/share/webmin
I don't know what to do about this.
Thought I would share this problem I ran into and the solution incase anyone else has it. Running Mailman 2.1.20 on Ubuntu 16 and a recent update to postfix stopped my lists. In my syslog I was seeing a message similar to:
Oct 24 16:43:59 mailman postfix/smtpd: NOQUEUE: reject: RCPT from mailman.ihmc.us[184.182.233.xxx]: 451 4.3.0 <user(a)ihmc.us>: Temporary lookup failure; from=<podcast-bounces(a)mailman.ihmc.us> to=<user(a)ihmc.us> proto=ESMTP helo=<mailman.ihmc.us>
As it turns out Postfix 3 tightened up on relaying. In my postfix/main.cf I had both
mynetworks_style = subnet
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
I finally found at <http://www.postfix.org/BASIC_CONFIGURATION_README.html <http://www.postfix.org/BASIC_CONFIGURATION_README.html>> that if mynetworks is present then mynetworks_style is ignored. So I commented out mynetworks and changed mynetworks_style = host and now mail from lists is being delivered again.
Hope this helps someone else.
Alan M Ordway
Yesterday we had a major network outage that lasted 2 hours+ This morning I find that the mailman server has "stopped working" I have restarted mailman and now the server but mailman is not processing any emails. The load in top is 0.00 ~0.01 sort of thing, no no disk i/o, no action at all, disks are not full. ssh takes a long time to login but there is no load to cause this. I can see python is running in top but at like 0.3%.
I run mail me@work and postfix sends fast so postfix seems OK, its like Mailman is in a coma, its has chocked to death but its heart is still beating....just seems odd.
What can I do here?
mailman-2.1.29_6, FreeBSD 12.0-RELEASE-p10
After an unscheduled power cut by our hosting provider, one of the
mailing lists hosted on this server came back up with a config.pck file
containing 0 bytes. The file's timestamp corresponded to the time of the
As a result, bin commands such as 'list_lists' would return a corrupt
database error, and overnight cron jobs wouldn't run. This was only for
one list; other lists on the same server were OK.
I've restored the config.pck file from a backup and things seem to be OK
Just checking, though:
1. Have others encountered config.pck corruption from power loss?
2. (putting on my tinfoil paranoid hat) Is there any chance the file
corruption occurred due to an intrusion attempt, and not the power loss?
Apologies if this is a FAQ but I could not find the info.
I have some mailing lists setup on cpanel. One address I have added to my
whitelist in spamassain. I also have no auto discard set, with "Discard
held messages older than this number of days. Use 0 for no automatic
discarding." set to 0.
However, emails from this address come in as auto discarded.
I'd like to prevent that in the future and have the email delivered as
Is there an additional setting I need to configure?