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.
We are using mailman 3, and would like to whitelist a domain for acceptance
of messages as non-members.
It seems possible from my online searches, I have also tried with an online
python regex tester(https://www.regextester.com/94044), but I have not
managed to be successful.
Below are 2 examples I have tried
*Head of IT*
*Office: **+27 87 238 4238* <0872384238>
*Mobile : **+971 55 418 4733* <0971554184733>
*Email: **daniel(a)noldor.co.za* <daniel(a)noldor.co.za>
*Web: **www.noldor.co.za* <http://www.noldor.co.za/>
Today I issued "prune_arch -l flohmarkt -d 30" and wondered about the
immense size of the corresponding archive directory archives/private/flohmarkt
du quickly showed me why:
# du -s * | sort -n
Shouldn't prune_arch also clean out the "attachments" directory?
Charité - Universitätsmedizin Berlin
Geschäftsbereich IT | Abteilung Netzwerk
Campus Benjamin Franklin (CBF)
Haus I | 1. OG | Raum 105
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155
I have migrated my old Mailman server to a CentOS 8.3 server containing this Mailman RPM package:
I would like to enable Google reCAPTCHA in mm_cfg.py as explained in /usr/lib/mailman/Mailman/Defaults.py with:
RECAPTCHA_SITE_KEY = xxx
RECAPTCHA_SECRET_KEY = yyy
I have created the prerequisite V2 keys on https://www.google.com/recaptcha/admin and restarted the mailman service.
The Mailman list page now contains a nice "I'm not a robot" frame as expected.
However, when I click "Subscribe", the confirmation page says "[Errno 13] Permission denied” (copied from my memory) and the subscription fails :-(
It finally dawned upon me that this could be a SELinux issue, since I naturally want Enforcing mode. If I use "setenforce Permissive" the Mailman error goes away!
The command "journalctl -t setroubleshoot" tells me:
SELinux is preventing /usr/bin/python2.7 from name_connect access on the tcp_socket port 443.
If you believe that python2.7 should be allowed name_connect access on the port 443 tcp_socket by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# ausearch -c 'python2' --raw | audit2allow -M my-python2
# semodule -X 300 -i my-python2.pp
I can confirm that the Mailman error is fixed by this workaround.
Question: Is there a proper way to configure this SELinux access for python2.7, rather than making this workaround?
Such a solution should be submitted as a bug report to RedHat/CentOS/Fedora.
Thanks a lot,
I occasionally get "Uncaught bounce notifications" where mailman has been
unable to figure out which user/list to increment the bounce counters for,
but where it's blindingly obvious to me. If it's just one or two bounces
I'm happy to leave it alone, but in other cases I'd like to manually
trigger the bounce processing lifecycle.
Ideally I'd like to be able to just suspend these users as if they had hit
the bounce limit for their lists, and let the notification process (and
possibly the user's action to unsuspend themselves) take over. Failing
that, the next best thing is to manually increment the bounce counter for
that list/user combination to trigger suspension that way.
Has anyone already got a script around for doing either thing?
Failing that, is there some documentation somewhere on the object model
that I can use to whip up a `withlist` invocation? The docs on this seem
pretty thin. I can't find anything on list.org that describes the methods
or variables available for lists or subscribers, or how to access them.
The "Site Administrator's Manual" appears to have never actually been
written, and the rest of the docs in the Site Administrator's section
appear to be FAQs and install manuals, none of which address this (that I
The class level documentation returned by pydoc seems like it might be
useful here, but there's a lot to wade through since pretty much everything
appears to be accessed through the MailList class, and there's no example
usage that I've seen so far. I'd prefer to avoid having to go line by line
through the code if I can avoid it, so some pointers (to docs or examples I
can reverse engineer) would be awesome.
I run Mailman 2 on a shared server. Over the years I’ve had occasional deliverability problems owing to spam from other users. In the long run I hope to migrate to Mailman 3, on a Digital Ocean droplet or similar. In the meantime, I’m looking at maybe using an email sending service.
Is it possible to use Mailgun (or alternative services) with Mailman 2/3? Mailgun does its own bounce processing and I wonder how that might tie in with Mailman’s.
If it is possible, in what circumstances (if any) is it advisable?
Thanks for any advice.
Sent from my iPhone
I've been running mailman on an old Ubuntu server that will become defunct
in a couple of weeks. Besides of having a new cloud based server (with
Ubuntu 20.04.1 LTS), I also need to switch from Sendmail to Postfix.
Now, setting up Postfix was not too big a problem, but getting it to work
with mailman has been challenging. Particularly, genaliases gives me a
traceback like this:
Traceback (most recent call last):
File "/var/lib/mailman/bin/genaliases", line 124, in <module>
File "/var/lib/mailman/bin/genaliases", line 118, in main
File "/var/lib/mailman/Mailman/MTA/Postfix.py", line 336, in create
_do_create(mlist, ALIASFILE, _addlist)
File "/var/lib/mailman/Mailman/MTA/Postfix.py", line 320, in _do_create
File "/var/lib/mailman/Mailman/MTA/Postfix.py", line 113, in _addlist
loopaddr = Utils.ParseEmail(Utils.get_site_email(extra='loop'))
File "/var/lib/mailman/Mailman/Utils.py", line 799, in get_site_email
hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain())
File "/var/lib/mailman/Mailman/Utils.py", line 794, in get_domain
AttributeError: 'NoneType' object has no attribute 'lower'
I'm getting no alias files in the /var/lib/mailman/data/ directory, and my
list addresses are not working:
<"|/var/lib/mailman/mail/mailman post test-list"@ardbeg.xxxxxx.net>
from <test-list(a)ardbeg.xxxxxx.net>): unknown user:
"|/var/lib/mailman/mail/mailman post test-list"
I've spent quite some time checking what might be wrong with my Postfix
configuration, and trying to search for previous, similar sounding cases,
but I've reached the point of feeling quite clueless. Any help would be
- Eva Isaksson
I'm receiving a lot of fake Subscription Requests and spend time to
1. how can I "lock" lists not to receive requests except administrator's
2. how can I mass discard those request from console?
Thank you in advance,