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?
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?
i just did make one vm instance Ubuntu 18.04 on google compute
engine. barely i did install postfix at there. hmm if possible, i wish
to run mailing service for my family and me -- it needs a little bit some comunication plus some
records about family history. yes i want GNU Mailman very
much!!! google compute engine blocked port 25 by default. in this case i
can run mailman with other port (example 625)? again question, Mailman
can act with 625 or 1625 or 2625, ...?
Sincerely, Byung-Hee from South Korea.
^고맙습니다 _地平天成_ 감사합니다_^))//
To clarify, I did get off Microsoft's blacklist, but after I did I
decided that particular list was probably too high traffic.
On 9/25/2019 10:10 AM, Brian Carpenter wrote:
> Are they subscribing via the listinfo page? If so then you can edit that
> page via the list admin interface and remove the subscription form.
> Also getting off of Microsoft's blacklist is not hard to do. It certainly
> would have been easier than all the trouble you are going through now.
> Have a great day!
> Brian Carpenter
> -----Original Message-----
> From: Mailman-Users <mailman-users-bounces+brian=emwd.com(a)python.org> On
> Behalf Of Jayson Smith
> Sent: Wednesday, September 25, 2019 10:04 AM
> To: mailman-users(a)python.org
> Subject: [Mailman-Users] Totally disable list subscriptions?
> For years I ran a Mailman list on my own server, until it obviously
> became too much of a load for certain ISPs to think I was sending
> legitimate Email. The final straw was when Microsoft blacklisted my IP
> from sending to all of their Email services (Hotmail, live.com, Outlook,
> etc.). I decided to move that heavy traffic list to groups.io. Still, I
> wanted there to be a placeholder at the list's old URL that would tell
> people the list has moved, and where to find it. For this reason, I
> created a new, empty, dummy list with the old list's name, and set
> subscriptions to require moderator approval. I have a Milter set up to
> block all inbound mail to the list's old addresses with a 551 failure
> message giving the URL of the new list. However, from time to time
> someone will subscribe via the web, so I still need to reject their
> subscriptions and point them to the new location. Is there any way in
> Mailman to outright disable any and all subscription attempts for a
> specific list?
> Mailman-Users mailing list Mailman-Users(a)python.org
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Hello. Mailman 2.1.23 package on Debian 7.
If a subscriber's nomail flag is set by admin, does monthly subscription
info/reminder message still get sent to that subscriber? There's one
subscriber on a list that, although we don't want to actually unsubscribe,
for the time being must not receive any emails whatsoever from the list.
Where would I read up more on this?
Thanks so much.
Is there a simple method to detect if a new list was created?
As mailman updates the alias file (/var/lib/mailman/data/aliases in our installation) with any new list I thought of
checking the modify date of the aliases file.
Is this a sufficient method?
Dipl.-Inform(FH) Peter Heitzer, peter.heitzer(a)rz.uni-regensburg.de
For years I ran a Mailman list on my own server, until it obviously
became too much of a load for certain ISPs to think I was sending
legitimate Email. The final straw was when Microsoft blacklisted my IP
from sending to all of their Email services (Hotmail, live.com, Outlook,
etc.). I decided to move that heavy traffic list to groups.io. Still, I
wanted there to be a placeholder at the list's old URL that would tell
people the list has moved, and where to find it. For this reason, I
created a new, empty, dummy list with the old list's name, and set
subscriptions to require moderator approval. I have a Milter set up to
block all inbound mail to the list's old addresses with a 551 failure
message giving the URL of the new list. However, from time to time
someone will subscribe via the web, so I still need to reject their
subscriptions and point them to the new location. Is there any way in
Mailman to outright disable any and all subscription attempts for a