willi uebelherr writes: > now i think, it is clear. The feature "duplicate suppression" is a fix > mechanism. I will wait for the answers of the people from the > mailman-users list, what the say about. But in Gmail with a user > configuration never i can resolve the problem.
That's right. GMail considers this a feature, and has consistently refused to even provide an option to receive copies of own mail. You may consider it embarrassing for GMail, but GMail clearly doesn't think it's a problem. If you don't like this feature, you will have to use a different mail service from GMail, or live with it. You may be able to work around it by fiddling with the subscription address as Richard suggests, but I bet it doesn't work (these are different names for the same mailbox). > Gmail follows the RFCs and treats the Message-ID as globally unique for > a particular version of the message. According to RFC5322, changing the > Message-ID is the correct way to identify a new revision of the message. This is absolutely correct. > In other words, if you consider the message sent from the mailing list > to be a different message, change the Message-ID. This is also correct. But only list admins really care about the difference between a direct copy and the copy distributed by Mailman, so it's a bad idea for Mailman to change the Message-ID. It probably won't be supported, unless convincing evidence is presented that there are cases where it won't confuse users and MUAs. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
