im trying to setup mailman and have an issue:
first my environment:
- I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/
- I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/
I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected:
In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp.
Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps?
For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/
Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)?
Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?)
Thanks and greetings,
I am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server:
I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell:
curl: (7) Failed connect to 172.19.199.3:8000; Connection refused
I assume this has something to do with uwsgi which I have no experience with.
Appreciate any assistance with getting Mailman 3 up and running. Thanks!
I have of course activated password login as it was not possible to get the
provider based logins to work (might be but not worth the time for me right
now). Is there any way for an user to request a new password when it is
I presume that the Persona login is removed now. I cannot hide it in my
version or at least I do not know how.
How do I set a template for one specific list? I want one list to have
a special footer template.
I have tried updating the database (template table) without effect so
apparently the database is not used for templates or some kind of
fallback is used to set it to the generic footer. Of course I also
tried to restart mailman after that operation to try to rule out any
I want to use a file://-path as that is the least painful way of doing
it. I also would like a solution to place a file in a special
location. My current templates are in a
structure with names like list:member:generic:footer.txt
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.
I'm not sure if this is the correct forum for this question, but I'm pretty
sure if there is expertise on how to do what I want to do, it can be found
Overview of what I am looking to do:
Due to the impending shutdown (in the next 6 months) of the data center
where our mailman server lives, we are being forced to move the
installation. We are going to be moving it to a different location.
Here is our problem...
Moving things is not really a problem in and of itself - I'm confident that
I can get things set up correctly elsewhere. However, our email server
sends somewhere around 100,000 emails per day, and if you cut over from one
IP address to another IP address, my understanding is that most ISPs will
start to ban you, because they are not used to that sort of volume coming
from an unknown IP. I know it would be better if we could keep the IP
address, but again, due to circumstances beyond my control, this is not
going to be a possibility.
We have been told that "warming up" the IP is the way to go - that is,
cutting over just some of the traffic a little at a time. So what I am
looking for is a way for all mail on our domain to be sent to our current
mailman installation, and based on some configuration (certain mailing
lists?) certain emails being sent out to the list subscribers will first be
forwarded to the new server and be sent from the new IP address.
Does that make sense?
Does anyone know a way that mailman/postfix can be configured to accomplish
Is there a different forum where I might be able to ask experts about this?
I saw in the docs:
> We have it! We just don’t have proper documentation here yet.
Could you please be more specific - can I switch Mailman 3 installation to
is it possible to migrate a mailman3-mysql-database to a
I tried to convert it with pgloader, but some identifiers had to be cut off:
2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner
wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac