David Cunningham wrote: > >For example, j...@test.com is on lists te...@lists.test.com and >te...@lists.test.com. d...@test.com sends an email to both >te...@lists.test.com and te...@lists.test.com. So, j...@test.com get's >two copies of the same email, one from each list. > >I know that the "nodupes" feature is only designed to stop duplicates >in the event that a user is specifically defined in the email. For >example, it works great when d...@test.com sends an email to >te...@lists.test.com and CCs j...@test.com directly. j...@test.com only >gets one copy. > >But, I have users insisting that before I upgrade to the latest >version of Mailman, this also worked when users were on multiple lists.
The nodupes feature works as you understand. It has never worked to avoid duplicate copies of cross-posted messages. Possibly there was some modification in the prior Mailman version that did this duplicate avoidance and was removed by the upgrade. Possibly you were using the regular_exclude_lists feature (under Non-digest options in the web admin interface) to avoid multiple copies of cross posts and some how in the process of upgrading this setting was changed. -- 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 http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
