Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
qqrs opened this issue May 3, 2024 · 1 comment

Comments

@qqrs
Copy link

qqrs commented May 3, 2024

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 <op@example.com>
to:	Some Mailing List <some-mailing-list@example.com>
"Reply" -> to: op@example.com
"Reply All" -> to: op@example.com, cc: some-email-list@example.com

Community email behavior:

from:	Original Poster <op@example.com> via mail.community.recurse.com 
reply-to:	general@lists.community.recurse.com
to:	general@lists.community.recurse.com
"Reply" -> to: general@lists.community.recurse.com
"Reply All" -> to: general@lists.community.recurse.com

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
Copy link
Member

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 😄)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants