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\+.*@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
On 10/02/2017 05:21 AM, Marc Sluiter wrote:
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?
I think so.
See the note I just added at <https://gitlab.com/mailman/mailman/issues/401#note_42163915>.
For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*@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?)
I'll be working on a fix. My inclination is to change all the regexp -confirm and -bounces table entries from, e.g., /^list-bounces@example\.com$/ to /^list-bounces(+.*)?@example\.com$/
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02-Oct-17 13:28, Mark Sapiro wrote:
I'll be working on a fix. My inclination is to change all the regexp -confirm and -bounces table entries from, e.g., /^list-bounces@example\.com$/ to /^list-bounces(+.*)?@example\.com$/
Er, if you want it to work:
/^list-bounces@example\.com$/ to /^list-bounces(\+.*)?@example\.com$/ ^-------
.
On 10/02/2017 10:34 AM, tlhackque via Mailman-users wrote:
Er, if you want it to work:
/^list-bounces@example\.com$/ to /^list-bounces(\+.*)?@example\.com$/
Thank you. (too much multitasking and not enough coffee)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Marc,
after having seen that you were able to config a mailman instance beside mailcow, I would like to ask you weather you could share all the necessary steps for the setup? :)
I already found out that there is a separate repo that tries to merge mailcow and mailman, but I would like to run them as you did.
Thank you very much in advance and greetings Moritz
participants (4)
-
Marc Sluiter -
Mark Sapiro -
moritzgnisia＠gmail.com -
tlhackque