Message Sent to A Re-Created List Results In Error
I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back.
I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not?
Thanks.
- Matt Alberti
On Tue, Dec 15, 2020, at 10:00 AM, matthew@alberti.us wrote:
I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back.
Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs.
I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not?
I personally don't remember seeing such an issue, but Mark or others might know.
Thanks.
- Matt Alberti
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
I checked all over the mailman core logs and couldn't find aproblem. But then I noticed that the 550 error was coming from dovecot-lmtp. I should rename this thread because the actual problem seems to be unrelated to re-created lists.
It seems like the actual problem seems to occur in the followingsituation:
Using Postfix
Using Dovecot
/etc/postfix/virtual includes addresses with same domain as mailman lists.
An e-mail address subscribed to a mailman list is in the /etc/postfix/virtual file as an alias (possibly also if destination address for an alias).
(Possibly related) E-mail address is also one of the list owners.
In that environment, Postfix seems to check only 'virtual_transport' list, which in my case is dovecot-lmtp, and when it doesn't find the mailman listname@domain entry in there, it sends a 550 user unknown. It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp.
When I remove that one address (that is in /etc/postfix/virtual) from the list of subscribers, I'm able to post again. Interestingly enough, when I put it back in as a subscriber. I'm still able to post. So it seems unsubscribing and re-subscribing that address fixed it, or adding an additional list owner and deleting it fixed it, or some combination of those.
I know this might be shaping up to be a very unlikely scenario. But basically the account is mine, an admin, doing testing before/after a deployment.. I'll try to create a few test procedures to document the method to reproduce the problem, and also hopefully fix it. If I can do that, I'll open another thread. This could also be a postfix config error of some kind, which is definitely possible if not likely.
Thanks for reading.
- Matt Alberti
-----Original Message----- From: Abhilash Raj <maxking@asynchronous.in> Sent: Monday, December 14, 2020 11:42 PM To: matthew@alberti.us; Mailman users <mailman-users@mailman3.org> Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error
On Tue, Dec 15, 2020, at 10:00 AM, matthew@alberti.us <mailto:matthew@alberti.us> wrote:
I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back.
Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs.
I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not?
I personally don't remember seeing such an issue, but Mark or others might know.
Thanks.
- Matt Alberti
Mailman-users mailing list -- mailman-users@mailman3.org
<mailto:mailman-users@mailman3.org> To
unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org>
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Matt, I think you're describing exactly the problem that's handled by /virtual alias domains/ that were added to support this case.
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht...
I did an integration between Mailman3 and Zimbra which uses Postfix, and came across the same issue with domains managed by Postfix and Mailman simultaneously.
I documented the case in my Zimbra - Mailman3 integration document here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration/-/blob/master/ma...
See if that helps ...
Best regards, Mojo
On 12/14/20 9:38 PM, matthew@alberti.us wrote:
I checked all over the mailman core logs and couldn't find a problem. But then I noticed that the 550 error was coming from dovecot-lmtp. I should rename this thread because the actual problem seems to be unrelated to re-created lists.
It seems like the actual problem seems to occur in the following situation:
- Using Postfix
- Using Dovecot
- /etc/postfix/virtual includes addresses with same domain as mailman lists.
- An e-mail address subscribed to a mailman list is in the /etc/postfix/virtual file as an alias (possibly also if destination address for an alias).
- (Possibly related) E-mail address is also one of the list owners.
In that environment, Postfix seems to check only 'virtual_transport' list, which in my case is dovecot-lmtp, and when it doesn't find the mailman listname@domain entry in there, it sends a 550 user unknown. It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp.
When I remove that one address (that is in /etc/postfix/virtual) from the list of subscribers, I'm able to post again. Interestingly enough, when I put it back in as a subscriber. I'm still able to post. So it seems unsubscribing and re-subscribing that address fixed it, or adding an additional list owner and deleting it fixed it, or some combination of those.
I know this might be shaping up to be a very unlikely scenario. But basically the account is mine, an admin, doing testing before/after a deployment.. I'll try to create a few test procedures to document the method to reproduce the problem, and also hopefully fix it. If I can do that, I'll open another thread. This could also be a postfix config error of some kind, which is definitely possible if not likely.
Thanks for reading.
- Matt Alberti
-----Original Message----- From: Abhilash Raj <maxking@asynchronous.in> Sent: Monday, December 14, 2020 11:42 PM To: matthew@alberti.us; Mailman users <mailman-users@mailman3.org> Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error
On Tue, Dec 15, 2020, at 10:00 AM, matthew@alberti.us <mailto:matthew@alberti.us> wrote:
I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back.
Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs.
I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not?
I personally don't remember seeing such an issue, but Mark or others might know.
Thanks.
- Matt Alberti
Mailman-users mailing list -- mailman-users@mailman3.org
<mailto:mailman-users@mailman3.org> To
unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>
Mojo, Thanks for the link. I finally got it sorted out. I probably need to write all this somewhere else. I have a combination of local, virtual, alias, and Mailman3 mail transport/routing, all on one server. Virtual, alias, and Mailman3 all use the same domain. Mailman also has an additional domain. It seemed like no matter what I did, the virtual mail would not work and mailman would, or the virtual mail would work but the domain that is both virtual and mailman wouldn't work with mailman.
The problem was the (well documented) behavior when defining"virtual_transport" (for dovecot lmtp) and "virtual_mailbox_domains" (for virtual domains and Mailman domains). When "virtual_transport" is defined, the "transport_maps" option is basically ignored, which causes Mailman to not work (assuming Mailman is setup with virtual domains, not alias or relay). When I took out "virtual_transport", then virtual mail via dovecot stopped working.
To fix it, I ended up creating an additional mysql lookup for thevirtual mail (they use dovecot lmtp for delivery). I put this lookup in the "transport_maps", and things seem to work. Now Postfix will check with both the virtual mailbox database and Mailman's lmtp regex list, and know the correct transport (dovecot-lmtp and mailman-core lmtp) respectively.
So after all that, I have to circle back around and see if there isstill an issue with using aliased or virtual addresses as a Mailman owner or subscriber. I'm guessing probably not, since now the correct transport method for each is now defined to Postfix.
Thanks for reading.- Matt Alberti
-----Original Message----- From: Morris Jones <mojo@whiteoaks.com> Sent: Tuesday, December 15, 2020 1:04 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error
Matt, I think you're describing exactly the problem that's handled by /virtual alias domains/ that were added to support this case.
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml#unusual-postfix-configuration
I did an integration between Mailman3 and Zimbra which uses Postfix, and came across the same issue with domains managed by Postfix and Mailman simultaneously.
I documented the case in my Zimbra - Mailman3 integration document here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration/-/blob/master/ma ilman-zimbra-integration.rst
See if that helps ...
Best regards, Mojo
I checked all over the mailman core logs and couldn't find a
On 12/14/20 9:38 PM, matthew@alberti.us wrote: problem.
But then I noticed that the 550 error was coming from dovecot-lmtp. I should rename this thread because the actual problem seems to be unrelated to re-created lists.
It seems like the actual problem seems to occur in the following situation:
- Using Postfix
- Using Dovecot
- /etc/postfix/virtual includes addresses with same domain as mailman lists.
- An e-mail address subscribed to a mailman list is in the /etc/postfix/virtual file as an alias (possibly also if destination address for an alias).
- (Possibly related) E-mail address is also one of the list owners.
In that environment, Postfix seems to check only 'virtual_transport' list, which in my case is dovecot-lmtp, and when it doesn't find the mailman listname@domain entry in there, it sends a 550 user unknown. It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp.
When I remove that one address (that is in /etc/postfix/virtual) from the list of subscribers, I'm able to post again. Interestingly enough, when I put it back in as a subscriber. I'm still able to post. So it seems unsubscribing and re-subscribing that address fixed it, or adding an additional list owner and deleting it fixed it, or some combination of those.
I know this might be shaping up to be a very unlikely scenario. But basically the account is mine, an admin, doing testing before/after a deployment.. I'll try to create a few test procedures to document the method to reproduce the problem, and also hopefully fix it. If I can do that, I'll open another thread. This could also be a postfix config error of some kind, which is definitely possible if not likely.
Thanks for reading.
- Matt Alberti
-----Original Message----- From: Abhilash Raj <maxking@asynchronous.in> Sent: Monday, December 14, 2020 11:42 PM To: matthew@alberti.us; Mailman users <mailman-users@mailman3.org> Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error
On Tue, Dec 15, 2020, at 10:00 AM, matthew@alberti.us <mailto:matthew@alberti.us> wrote:
I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back.
Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs.
I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not?
I personally don't remember seeing such an issue, but Mark or others might know.
Thanks.
- Matt Alberti
Mailman-users mailing list -- mailman-users@mailman3.org
<mailto:mailman-users@mailman3.org> To
unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com> _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Abhilash Raj writes:
On Tue, Dec 15, 2020, at 10:00 AM, matthew@alberti.us wrote:
I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back.
Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs.
Also, be sure to tell us which MTA (mailserver) you use, and you should check the MTA configuration files to make sure the deleted and recreated list would be recognized.
participants (4)
-
Abhilash Raj -
matthew＠alberti.us -
Morris Jones -
Stephen J. Turnbull