I have finished my how-to install Mailman 3 on Debian 10 completed to
the point where you can use it to get a fully functional Mailman 3
environment up and running. This is a comprehensive guide that walks you
through installing EVERYTHING (currently!) that Mailman 3 needs to run.
It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have
not added the update directions yet but will very soon. I also plan on
adding a section on setting up DKIM and Xapian with Mailman 3.
I hope this helps those who wish to get a Mailman 3 server up and
running quickly and brings a sense of sanity to the confusion regarding
the various documentation out there concerning the installation of
Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20
at some point.
Without further ado:
I am sure the above guide can use improvements. Feel free to contact me
off-list to point out mistakes/improvements, etc.
I’m getting bounces back from postfix (553 5.1.3 Error: malformed address) for my confirm replies.
I found a similar issue in this lists’ archives back in 2017 but that issue was supposedly fixed in version 3.2
I’m running the current docker containers.
I’m pretty sure I have all of the mailman settings in postix:
# Support the default VERP delimiter.
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
owner_request_special = no
the entries in /opt/mailman/core/var/data/postfix_lmtp look like they should match
> On Feb 26, 2021, at 14:08:54 PST, Mail Delivery System <MAILER-DAEMON(a)ip-172-31-18-222.us-west-2.compute.internal> wrote:
> This is the mail system at host ip-172-31-18-222.us-west-2.compute.internal.
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
> For further assistance, please send mail to postmaster.
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
> The mail system
> host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address
> (in reply to RCPT TO command)
> Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal
> X-Postfix-Queue-ID: E144B8BC3C5
> X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com
> Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST)
> Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu
> Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu
> Action: failed
> Status: 5.1.3
> Remote-MTA: dns; 172.19.199.2
> Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address
> From: Steve Mats Mats <willey(a)selby.com>
> Subject: Re: Your confirmation is needed to join the matsmats-mm3-test1(a)mm3.aca-aws.s.uw.edu mailing list.
> Date: February 26, 2021 at 2:08:52 PM PST
> To: matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu
>> On Feb 26, 2021, at 11:41:54 PST, matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu wrote:
>> Email Address Registration Confirmation
>> Hello, this is the GNU Mailman server at mm3.aca-aws.s.uw.edu.
>> We have received a registration request for the email address
>> Before you can start using GNU Mailman at this site, you must first confirm
>> that this is your email address. You can do this by replying to this message.
>> Or you should include the following line -- and only the following
>> line -- in a message to matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu:
>> confirm d6f77a2572ef55a8b2c4ca0d77de8493fbb55856
>> Note that simply sending a `reply' to this message should work from
>> most mail readers.
>> If you do not wish to register this email address, simply disregard this
>> message. If you think you are being maliciously subscribed to the list, or
>> have any other questions, you may contact
Based on recent threads, I've added two tasks to our 2021 GSoC ideas
Bcc'd to David and Johannes because I referred to threads starting
with their posts. If you want me to paraphrase in the task
description, let me know, but I preferred to do it this way to
encourage applicants to join the community. (Note: we haven't been
selected yet, so this isn't any more public than the archived mailing
Suggestions of other GSoC tasks and refinements to existing ones
welcome. However, please discuss them on the list (or to a core dev
privately) unless you have GSoC experience. Google has specific
requirements for Summer of Code projects, so there are a lot of
important tasks that should not be on that page.
If you have an enhancement that you'd definitely like to put on our
agenda, and also suggest for GSoC, feel free to file an issue on the
tracker and point me, Mark, or Abhilash to it.
we are about to migrate our Mailman 2 instance to Mailman 3.
As we are hosting many (small) mailing lists for different customers, we
get in trouble about future handling of mail archives. Mailman 2 just
used mbox files per list and flat files for public archive, so archives
do not matter apart from some storage. With hyperkitty, all messages for
all lists are stored in on single database and I'm a little bit scared
of a single database table with dozens of GB of data.
Many of our users do not really need archiving, some customers also
asked archiving to be disabled for legal reasons within their lists.
Can I as the server admin disable archiving (or set other list options)
in a way that the list admin can not change it via postorious?
Can I have custom archiver settings per list or per domain
I've imported a list from Mailman2 and had the owner send a message for testing purposes.
His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held.
However if we attempt to view the message in Postorius web UI then an error is thrown.
In the web interface the error is simply "Mailman REST API not available. Please start Mailman core."
But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below.
[Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages
Does "Service Unavailable" mean I'm missing something in the configuration?
Thanks for your help.
For context, I have been lurking on this site for a number of years now,
in order to track the progress of this wonderful mailman3 project.
Further context, I am chair of a 66 unit condominium and pay for two
lists provided by EMWD.com and get a hands on feel from an mailman3
*Is there another site that might best communicate the future goals,
plans, objectives, and time frames for mailman3 or is the status of the
project at the state of being primarily reacting to problems, as
evidenced in this problem solving forum, at least as it seems to me,
with no offense meant or intended?*
Something I find surprising is a problem described in an image grab
below relating to an inability to amend a list entry to include a name
to be associated with an email address, as if the data needs to be
immutable. When a workaround was unsuccessfully explored to delete the
entry and then resubmit an amended entry but with the same already
deleted email address, that was still refused, presumably because of
pointers to archived data don't permit, but this seems like a
particularly onerous restriction, or perhaps even a bug, or at least a
severe design constraint. *Is this item on an existing to do list?*
Thank you in advance for any responses to the questions in bold to
facilitate faster reading, etc.
Mailman2 and other mailman3 installs I’ve seen included links in the moderation ‘requires approval’ or list subscription request approvals. But the messages from my mailman3 server does not have the links. What configuration am I missing?
I’m running off the stable 0.3 docker images as updated this morning to the current releases (3.3.3, 1.3.4, 1.3.4)
> From: list2-owner(a)mm3.xxx.s.uw.edu
> Subject: list2(a)mm3.xxx.s.uw.edu post from xxx(a)jhmi.edu requires approval
> Date: February 25, 2021 at 2:18:14 PM PST
> To: list2-owner(a)mm3.xxx.s.uw.edu
> As list administrator, your authorization is requested for the
> following mailing list posting:
> List: list2(a)mm3.xxx.s.uw.edu
> From: xxx(a)jhmi.edu
> Subject: this is a post that should be moderated
> The message is being held because:
> The message is not from a list member
> At your convenience, visit your dashboard to approve or deny the
> Begin forwarded message:
> From: mm3-test-mem-owner(a)mm3.xxx.s.uw.edu
> Subject: New subscription request to Mm3-test-mem from xxx(a)uw.edu
> Date: February 25, 2021 at 12:49:05 PM PST
> To: mm3-test-mem-owner(a)mm3.xxx.s.uw.edu
> Your authorization is required for a mailing list subscription request
> For: xxx(a)uw.edu
> List: mm3-test-mem(a)mm3.xxx.s.uw.edu