442496 - Remove duplicate mail on the server side (mailman - inherited lists)

Status: RESOLVED WONTFIX

(Infrastructure & Operations :: Infrastructure: Mail, task)

Description

[Wil Clouser [:clouserw]]

I don't know enough about mail to use the right terms so bear with me please. :)

I'm on several lists that get CC'd on the same mail and I'm wondering if it's possible to make the mailing system smart enough to filter out the duplicates.  For example, I'm on release-drivers and the build mailing list and someone CC'd me on the thread so I'm getting three copies of each email.  Is there a setting that can be turned on that can collapse the duplicates?

Thanks.

Comment 1

[Reed Loden [:reed]]

You can enable the "nodupe" option for your account in mailman.

Comment 2

[Reed Loden [:reed]]

https://mail.mozilla.org/options/build/[e-mail]
https://mail.mozilla.org/options/release-drivers/[e-mail]

Avoid duplicate copies of messages?

When you are listed explicitly in the To: or Cc: headers of a list message, you can opt to not receive another copy from the mailing list. Select Yes to avoid receiving copies from the mailing list; select No to receive copies.

Comment 3

[Samuel Sidler (old account; do not CC)]

I've noticed this, too. It changed in the last couple of months and I've been bearing with it since. Was that due to an upgrade?

I also think it has a problem with recursive messages. For example, I ensured that I had "nodupe" enabled for my qa@ mailing list, but when someone replies to a release-drivers email, I get two copies. I'm not actually on release-drivers, but I *am* on qa@ which is on release-drivers...

Comment 4

[Samuel Sidler (old account; do not CC)]

(In reply to comment #3)
> but when someone replies to a release-drivers email

An email I sent, I mean.

Comment 5

[Wil Clouser [:clouserw]]

Thanks reed.  I've set that option globally on all my lists - hopefully it will help.  It doesn't sound like it will help the problem of being on multiple lists getting the same message though.

Comment 6

[Reed Loden [:reed]]

justdave, I remember you mentioning a while back about a way for mailing lists to know the membership of other mailing lists they inherited, so as to possibly get mailman to understand this issue... Thoughts?

Comment 7

[Dave Miller [:justdave]]

Requires a mailman upgrade.  Need 2.1.11 or later for that, we're on 2.1.9.

Comment 8

[Jeremy Orem [:oremj]]

Changing QA Contact.

Comment 9

[Reed Loden [:reed]]

(In reply to comment #7)
> Requires a mailman upgrade.  Need 2.1.11 or later for that, we're on 2.1.9.

Upgraded to mailman 2.1.11 now... is there anything that needs to done in the mailman admin config for release-drivers to get what clouserw wants, or will it just start to work?

Comment 10

[Dave Miller [:justdave]]

The FAQ entry that mentions this feature now states that it won't be available until Mailman 2.2 :(

The feature request for it on their tracker is still open, and has been touched less-recently than the FAQ.  It does, however, have a patch on it, against Mailman 2.1a4.  Since we're rolling our own mailman package already anyway, perhaps we can get the patch working.

https://bugs.launchpad.net/mailman/+bug/266558

Comment 11

[Ed Lim [:limed]]

We are running version 2.1.18 now, there are also options here[1] with removing dupes. But I don't think we can 100% remove dupes and its not a big enough issue to hunt down the maintainers to fix.


[1]: http://www.gnu.org/software/mailman/mailman-member/node21.html