Thank you, Mark, for that very helpful and clear reply. I have given this feedback to the people who created the original lists. I have particularly recommended the use of regular_include_lists as I don't believe they need the digest feature for their particular use-case.
Regards Philip On Tue, 7 Jul 2020 at 03:38, Mark Sapiro <m...@msapiro.net> wrote: > On 7/6/20 6:57 AM, Philip Colmer wrote: > > We have a number of "source" lists, e.g. listA, listB and listC. Each > > of them has listZ as a member, with the intention that all posts to A, > > B and C get replicated to Z. > > > > This all works until it gets to the point where posts to Z get emailed > > out to the members of Z. This is currently failing because the gateway > > mail system we are using is reporting "Duplicate header > > 'Delivered-To'". > > > > Is there a setting or mechanism I can set in Mailman 2.1 that strips > > the duplicate header or does anyone have any other suggestions on how > > to resolve this? > > > See the FAQ article at <https://wiki.list.org/x/4030540>. Mailman > doesn't do well with lists that have both individuals and lists as > members (I suspect that is the case here). The main reason for this is > if you declare the parent list as an umbrella list, the individual > members can't get password reminders, but if you don't, anyone can > request a password reminder for the child list and it will be sent to > that list. You can use header filter rules on the child list to discard > password reminders, but that's another step. > > Then there is your issue to contend with which would seem to preclude > having a list as a member of another list because of the way your > outgoing mail service handles this. Note that the Delivered-To: headers > are added by your incoming MTA upon delivery the the parent and then > again upon delivery to the child. Mailman has no setting to strip those, > but you could implement a custom handler to do this if it's your Mailman > server. See <https://wiki.list.org/x/4030615> for info on custom handlers. > > If you aren't concerned about digest members of listZ You can use > regular_include_lists to include, e.g. the non-digest members of listZ > in posts to listA by including l...@example.com in the > regular_include_lists setting of listA, and likewise for listB et al. > > This, along with some caveats is discussed in the FAQ at > <https://wiki.list.org/x/4030540>. > > -- > Mark Sapiro <m...@msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
