" Not metoo " feature appears to be broken

[dreamhosttest]

I have a mailing list "<email address hidden>". Some members would like to receive copies of the messages they post and some would not, and I've set the members' "not metoo" options accordingly. However, it appears that nobody receives copies of their own messages, regardless of which setting they have. Please advise.

[Mark Sapiro (msapiro)]

Here are some reasons why a poster with not metoo unset would still not receive a copy of her own post from the list.

1) The poster's nodups option is set and the poster has Cc'd herself.

2) The poster is using gmail/googlemail or some other mail service that discards messages with duplicate message-ids. See the FAQ at <http://wiki.list.org/x/2IA9>.

3) The poster receives digests from the list (her post should be in the digest regardless of not metoo).

4) The poster's list delivery is disabled.

5) The poster has some kind of filter rules in her own MUA that filters the message as a duplicate of a sent message.

If none of these explains your issue, please if you can, check your server's outgoing mail logs to see if the message was sent to the poster or not.

Note that in general, eligible posters without not metoo receive their own posts from Mailman lists. If the messages are in fact not being sent to the posters by your list, we'd need more information to debug this. For example, does this problem occur with all lists on this server or just the 'board' list.

Also, it appears that while the mailman installation at <http://lists.phoenixrisingfreeschool.org/listinfo.cgi> identifies itself as version 2.1.14, it is non-standard in that list names in the web interface are of the form "board-phoenixrisingfreeschool.org" as opposed to just "board". Perhaps this issue should be reported to whoever provides this modified version.

[dreamhosttest (dreamhosttest)]

I am the primary mailman admin at DreamHost and am unable to replicate this issue. The user has since removed their list so I can not troubleshoot this further, however I suspect they were using Gmail (which has resulted in this same problem in the past). Thank you for your time and we will update this bug in the future if it turns out to be valid after all.