On 4/7/23 14:58, Dave Hall via Mailman-users wrote:
On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark@msapiro.net> wrote:
On 4/7/23 13:43, Odhiambo Washington wrote:
On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < as2020+github@fam.tuwien.ac.at> wrote:
I am running MM2 und 3 in parallel without problems, I do have a special MTA setup though (Sendmail). Can't speak for Postfix etc..
Your setup can handle list1@domain1.name via MM2 and MM3, simultaneously, right? :-)
It is possible to have an MM2
list1and an MM3list1@domain1.namesimultaneously on the same server, but what is the MTA going to do with incoming mail tolist1@domain1.name. I suppose it could deliver it to both MM2 and MM3, but I don't see any practical use case for this.I run Exim4 on my servers so I can comment from this perspective. Exim had a concept of 'routers' which are stacked and processed in order of appearance. There is a router for MM2 and one for MM3 that pick off incoming mail based on whether the email address matches a list name. WIth this setup, you could have the same list name in both MM2 and MM3, but it would go to whichever router appears first and the second one would never see it. So I have the MM3 router first, and as I migrate my lists from MM3 the email for those lists no longer gets to MM2.
And mail.python.org which currently has 189 Mailman 3 lists and 223 Mailman 2.1 lists does something very similar in it's Postfix configuration and also prefers Mailman 3.
However, maybe I misunderstood Odiambo's question about simultaneous support for a Mailman 2.1 and Mailman 3 list of the same name. We could certainly have that on mail.python.org, and even have both MM 2.1 and MM 3 web UIs for those lists, but as soon as the MM 3 list is created during migration, mail is only delivered to the MM 3 list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan