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?
I have spent some time now trying to understand the list admin interface to Mailman 3.0. There is no context-sensitive help and looking around at the Mailman sites, I mostly find instructions on how to install Mailman 3.0, but no documentation on using it (other than for end users - which is much improved over MM2).
I also looked in the FAQ. Is there such docs and, if so, where can I find them. It’s about terminology and how to mangle the headers, etc.
Oh, and a big thanks to Brian Carpenter of EMWD for his help installing MM3, as I ran into a wall in my own attempt. MM3 appears to be a big end-user improvement over MM2. Thanks also, developers, for the work on MM3 development. I can see that it was a mountain of work to get that done.
Can anyone tell me where the actual member bounce value is stored? I want
to setup a cron job to reset the member bounce value to 0 for
certain members whose mailboxes are only active when they have a satellite
overhead to give them internet connectivity (about 8-10 hours each day).
They keep getting disabled because their bounce value breaks the threshold
value but this cannot be avoided due to their location and lack of
internet. Thank you for your time and knowledge.
On 12/12/19 12:46 PM, Chromatest J. Pantsmaker wrote:
> I'm the system admin (though I'm not great at it). I have a problem with
> spam. Hundreds of spam messages are posted to my lists each week.
> non-subscribers so they don't go to the lists, but they *do* go to
> list owner which floods my inbox.
> I'm looking at the page on how to use SpamAssassin:
> Is that the best way to do what I need?
> If so, what's the best method to use in my case?
> My system:
> Mailman 2.1.20
> Apache2 / 2.4.18
> Postfix 3.1.0
> Ubuntu 16.04.1 LTS
With Postfix, you should activate the built-in SPAM control, "postscreen".
The details on how to use it are in POSTCSCREEN_README when you install
from source, I don't where/if Ubuntu puts it, or if they build it for
their distro, but it just works. "man postscreen" should get you started.
I have it checking spamhaus.org, spamcop.net, and barracudacentral.org
I sometimes add IP ranges to "/etc/postfix/postscreeen_access.cidr",
(they've mainly been from Brazil, Korea, and China), when I notice a new
source that the blacklists haven't yet found, blocking out vast swathes
of the internet doesn't trouble me.
I'm the system admin (though I'm not great at it). I have a problem with
spam. Hundreds of spam messages are posted to my lists each week. They're
non-subscribers so they don't go to the lists, but they *do* go to me, the
list owner which floods my inbox.
I'm looking at the page on how to use SpamAssassin:
Is that the best way to do what I need?
If so, what's the best method to use in my case?
Apache2 / 2.4.18
Ubuntu 16.04.1 LTS
Is there any way to delete a list (mailman 2.1.9) but leave its archives
available? I know that rmlist by default doesn't delete list archives, but
with the list no longer in existence, they're no longer viewable via the
web interface. Is there perhaps a way to just disable a list without
deleting it? It would need to be in a way which keeps the list's aliases
out of the alias file, not just disable delivery.
One of my main gripes is the From: mangling that we had to use to allow AOL and Yahoo subscribers to send messages without messing everyone else up. I have now been informed that Mailman 3 does not solve this problem, but I’d like to move to Mailman 3 anyway. So what to do?
How about this:
1. Replace the From: address with a no-reply address on the list server. Don’t add the sender’s address in quotes.
2. Keep the ‘Reply-To:’ address as the sender’s address (that’s what I have it set to now - I don’t want people to reply to the lists).
3. Put HTML mailto: links for ‘Reply to Sender’ and Reply to List’ at the bottom of the message.
My other solution:
Require subscribers from AOL/Yahoo and whichever other service with the same misguided policy to get another email address for the lists.
Is there anyone on this who will be willing to help installing Mailman 3 for me on a Linux system. I have tried and I have had two experts try as well, but we have all run into difficulty. I’ll pay, of course.
I'm trying to get mailman up and running, using Apache as the web
server, and I appear to have run into a fundamental and insoluble
Now, please be gentle with me, it's a good 15 years since I last used
Linux servers in anger, and I am very far from being an expert with
Apache configuration, so there may be a very dumb question coming up.
I have the mailman lists working correctly, I can subscribe to lists,
send messages, and so on. However, I have the apparently widespread
problem that the admin web pages just silently ignore commands.
Reading through this list, I see that this is apparently due to the
ScriptAlias redirection just silently dumping the data content of HTTP
POST requests. Which seems a bit odd to me, but what do I know?
The standard installation of mailman uses the following httpd conf directives:
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
Require all granted
This makes sense to me, redirecting calls to /mailman/<cgiscript>
through to the directory in which those scripts are installed. But if
the standard package setup uses HTTP POST, and ScriptAlias dumps HTTP
POST data, how could this ever work?
The documentation says that the Exec directive can be used as an
alternative, which would seem to side-step this problem, but I cannot
find the Exec directive anywhere in the Apache documentation.
Can anyone provide a sample config that works, please? I'm thoroughly
confused, and none of the threads I've found on this list show any
kind of full solution.