Hi,
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,
Marc
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:
https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/
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 http://172.19.199.3:8000/postorius/lists/
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!
Brian Carpenter
I've got mailman running on Ubuntu 14.04, with systemd service files to
govern the mailman and hyperkitty qcluster processes.
I notice in the systemctl status call for the qcluster command that
there are a bunch of errors like:
[Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist.
[Q] INFO Process-1:1 processing [rebuild_email_cache_votes]
[Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist.
[Q] INFO Process-1:2 processing [rebuild_thread_cache_votes]
[Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist.
[Q] INFO Process-1:3 processing [rebuild_email_cache_votes]
[Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist.
[Q] INFO Process-1:4 processing [rebuild_thread_cache_votes]
[Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist.
Is there something more I should be doing to sync hyperkitty's database
with mailman? I've got the crontab file in place, and that appears to be
running without error. Anything else?
Thanks,
Eric
Hi,
I am new in the list. I have been looking for this topic in the archives
in order to avoid duplicate, but I could not find any thread.
According to the new GDPR rules, lists owners need to have a
confirmation from subscribers, and this is easy to do with Mailman 3.
What I can't figure out is how to save all the confirmation emails
received from users.
I only see the confirmations commands emails in the logs,
Is there another place/way to store them?
For GDPR compliance it is important to be able to demonstrate that you
received the confirmation, in case you may need it in the future.
Bests
Maddish
--
*MaadiX*
Tu nube en tus manos
https://maadix.nethttps://twitter.com/MaadiXnet
Hi,
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
forgotten?
I presume that the Persona login is removed now. I cannot hide it in my
version or at least I do not know how.
cheers
// David
Docker-mailman 0.1.1
I am using Mailman 3.1 in production and I am trying to debug a problem[1] so I tried to setting Mailman to provide more debug info in the smtp.log file[2]. I might have been doing it wrong, but in the mailman-extra.cfg I set
[logging.smtp-failure]
path: smtp.log
and restarted Mailman, which stopped incoming mails until removing the added section. What is the correct way to get Mailman to provide more debug info in the smtp.log
1) https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa...
2) http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.ht...
Henrik Rasmussen
Hi.
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
caching-related problem.
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
.../var/templates/site/en/
structure with names like list:member:generic:footer.txt
Cheers
// David
Hello,
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.
M.Z.
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
here.
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
this?
Is there a different forum where I might be able to ask experts about this?
Thanks,
-Darren
