Replying to Community emails should work more like other mailing list systems?

[qqrs]

I'm filing this issue because I have, once again, sent an email to hundreds of people when I intended to email the thread originator directly. It's been a couple years since I replied to a Community thread and I'd forgotten it doesn't work like most other mailing lists. Of course it's a little tricky since Community is aiming to be a blend of forum software and a mailing list.

This relates to #321. Community forges the From header, but uses a Reply-To so replies go back to the Community list.

Google Groups behavior:

from:	Original Poster <[email protected]>
to:	Some Mailing List <[email protected]>

"Reply" -> to: [email protected]
"Reply All" -> to: [email protected], cc: [email protected]

Community email behavior:

from:	Original Poster <[email protected]> via mail.community.recurse.com 
reply-to:	[email protected]
to:	[email protected]

"Reply" -> to: [email protected]
"Reply All" -> to: [email protected]

Possible proposed alternative... What if Community didn't use the Reply-To? Would the user be able to reply to OP only or reply all if they want to send to OP and the list?

(I realize Community isn't under active development, filing this for future consideration)

[nicholasbs]

Thanks for the clear report!

+1. The status quo clearly isn't right -- it should probably work how Google Groups works.

I won't promise a specific timeline, but we'll make this change eventually (also happy to take but by no means expect a PR since this is all open source, and that will still be blocked on one of the ~2 people who know this codebase to review/deploy 😄)

[porterjamesj]

OK, we tried removing the reply-to, and it worked "as expected" in that:

• If you just click "reply" to an email, your reply goes to the original poster and not the list
• If you click "reply all", it goes to the original poster and the list. However, this results in your reply appearing in the original poster's email inbox twice (one email is the actual email you sent them, and the other is generated by community).

We've rolled back the change for now, since this "double email" behavior seems kind of annoying for the OP.

We want to ask for input first, from @qqrs or anyone else. Does anyone know if this is how other mailing lists (e.g. Google groups) work? And if not, how do they solve this problem? Does this double email behavior seem too annoying? Or is it worth it to have the behavior of clicking reply be more intuitive?

[qqrs]

Thanks for taking this on @porterjamesj.

I tested with Google Groups and OP only receives one copy of replies. It comes directly from the reply-er, not via the list (i.e., there's no mailing list and mailed-by header).

Mailman docs suggest this might be done by skipping list recipients if the headers indicate they are already receiving a copy.

Do not send a copy of a member's own post specifies whether a member posting to the list will get a copy of their own posting.
Filter out duplicate messages to list members (if possible) specifies whether members who are explicitly listed as a recipient of a message (e.g. via the Cc: header) will also get a copy from Mailman.

Think that approach might work?