I'm looking at migrating from an old server running mailman 2.1.15 (Debian
wheezy) to a new Ubuntu 18.04 LTS system. I'd like to upgrade to mailman3
as a part of this migration. I was reading the migration docs
(<http://docs.mailman3.org/en/latest/migration.html>), which seem to
require both mailman2 and mailman3 be installed concurrently on the same
system. Is that correct, or can I rsync the mailman2 list information onto
the new server without mailman2 itself being present, and import from there?
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
I have a spam-problem like anyone else. Most of the spam my listserver
receives has some kind of impilict destination so the implicit rule
catches most of the spam that way. This is fine. What is not so fine,
however, is that this results in a moderation message to the sender.
I'd like to stop that so that the spammer has no confirmation that the
mail was received.
I can probably stop this in postfix before the mail reaches mailman3,
but I'd prefer changing the behaviour of the rule. Is there any
setting that could be used or should I just modify the rule?
I want to whitelist an email address on all lists to bypass moderation.
The email address is not a subscriber. On google I
found accept_these_nonmembers but I do not know how to use it.
Please show me some examples how to whitelist someone(a)example.org.
Thanks in advance.
Is there a simple way to force the mailman3 install to run off of a
specified config/specified db without having to enter it manually each
I just want any administrator to be able to enter mailman without wrecking
Systems Administrator @ Afilias Canada
A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8
T. +1.416.646.3304 x4186
we are trying to set a once public list to private but have trouble
doing so. In Postorius this doesn't seem to work - you can change "show
list on index page" via the settings, but the value isn't saved. Is
there a way to set advertised = False to a specific list via the shell?
Thanks & Regards,
(Kulturserver editorial staff)
I'd like to test out some bugfixes in the master branch, namely the
merge request related to:
But I use the maxking docker images of which the 'rolling' and 'latest'
tags are apparently not really used. Might it be possible to push these
a litte bit more frequently?
Thank you and best regards,
In Mailman 2 the site admin could add a member to a list using the -wn parameter of add_members to avoid sending a welcome message.
On the host (outside the docker container) I've made an updater using the REST API to keep certain lists updated with imported addresses from one of our other systems, though respecting opt ins and opt outs. Similar to Mailman 2 I would like to avoid the welcome message to those automatic updated members, even the list is configred to send welcome message to those opting in by will, and I also like to avoid forcing the list owner/moderator to approve all new members automatically updated even the list is set for moderation of new members opting in by will.
What is the payload for "no welcome message"?
def add_new_members(listname_fqdn, members):
for member in newmembers:
payload['list_id'] = listname_fqdn.replace('@', '.')
payload['subscriber'] = member
payload['pre_verified'] = True
payload['pre_confirmed'] = True
payload['pre_approved'] = True
response = mmapipost('members', payload)
response = requests.post('http://172.19.199.2:8001/%s/%s' % (restapiversion, apicommand), data=payload,
Is there any documented procedure moving from a working install of
mailman3 and postorius to a docker-based version? The reason would be
to get a setup that is somewhat easier to maintain and upgrade.
That said much of the work is to keep a mta, web server, spamfilter,
grey list solution, dkim signing etc. running and up to date. I
suspect that there is no pre-made docker images for that?