-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Apr 22, 2016 at 08:12:04AM -0400, The Wanderer wrote:
[...] > In this case, what appears to happen is that Gmail assumes that > Message-ID is unique, and consequently that it only needs to keep one > copy of a message with any given Message-ID. Since the person sending a > mail already has one message with that Message-ID (in their Sent > folder), Gmail sees the incoming mail as a duplicate, and discards it. Sounds kinda plausible. Any Googler listening who'd care to shed light? C'mon, folks... > This means that the mailing-list software _could_ technically work > around this behavior by modifying the Message-ID of the received message > before it sends that message out to list members. > > That strikes me as a dreadful idea from a design perspective, however, > even just on basic principle.... A less brutal approach would be to drop (nearly-) dupes coming whithin a short period of time from googlemail... > > And... would you want to complicate a server setup just to cater to > > some client idiosyncracy? > > ...so my answer to this would be "definitely not". we seem to be in violent agreement here. Just live with the dupes, for me it's part of the landscape already (oh, lookee, a gmail!). [...] > The reasonable man adapts himself to the world; the unreasonable one > persists in trying to adapt the world to himself. Therefore all > progress depends on the unreasonable man. -- George Bernard Shaw But doesn't that contradict the above? (cool quote, btw). regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcaF9IACgkQBcgs9XrR2kYvTACdFh1YD1J5oVPSmTOK3nqHuPrd tpMAn2C1Tv9ADaNAcseTd5XMmNfUpaB0 =GHyD -----END PGP SIGNATURE-----