Gmail not echoing your own posts to Yahoogroups back to you. About 6 months ago or so I switched to using Gmail as my outgoing mail server as well as my incoming. I still use a local email reader. Now, I belong to and contribute to quite a large number of Yahoogroups some of which I run. It puzzled me that my own posts to those groups weren't coming back to me via the inbox. It finally got sufficiently annoying to research and at that point I discover that this is a known bug in Gmail and has been for getting on for 2 years. Your outgoing email is in the sent and all folders in Gmail. But when the email is echoed back to you by yahoogroups, gmail is not so helpfully just discarding it. Probably because it has the same email ID as one already in their database. This is just wrong, but clearly isn't going to get fixed. The work arounds are all abit messy because you have to use a different smtp send server to normal and/or a different send email address just for posting to yahoogroups.
What I haven't checked yet is whether the same behaviour happens in mailing lists hosted in googlegroups or mailman.
I've found an old message sent via different smtp server. And I can confirm that Yahoogroups is not rewriting the Message-ID: header. So my local email reader is storing the sent message, sending it via a 3rd party SMTP server, it routes to yahoogroups, is exploded to the list, comes back via gmail and finally via POP3 back to my local email reader. Locally, I now have 2 copies but with the same message-ID. One in my sent folder and one in the mailing list folder. This is what I think should happen. Because my local email reader does this and isn't phased by it, it makes GMail look wrong.
As far as I can see if I want to go on routing my email via GMail's exceptional spam filtering, I have to either put up with this or use somebody else's SMTP server on the outgoing leg of the route.
I believe GMail relies heavily on the Message-ID and particularly on the uniqueness thereof - which it's entitled to under the RFCs. Having messages with the same Message-ID showing up in different places would break things for them. So changing this behaviour would be a very hard thing for them to do, and to be fair, there's a diminishing number of people who are affected by it.