-
Notifications
You must be signed in to change notification settings - Fork 2
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
Set Reply-To header to original recipients #1040
base: master
Are you sure you want to change the base?
Conversation
The email sent from the system is normally used as a thread. Currently you have to either select the emails manually or hit reply all and remove the sender email.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't the expected behaiviour here would be that it replies to the sender of the receipt? I feel like it could be confusing if it doesn't follow normal email convention
But I don't use the system myself, so I don't really know what the typical use cases are.
The reason I added both the sender and the receiver is sortof twofold
You're probably right though - so I'll see if there are any better ways of solving this. Did some more testing and it turns out when you reply to yourself without an email-list it will pop up as unread in your inbox even if you're the sender - which is kinda annoying.. |
Hmm, I guess it's kind of unintuitive either way when the same email is sent to the sender and recipients. But I feel like for recipients discussing the email they should be using reply-all and just remove the sender, as this is what you would do for any other incoming email. |
The email sent from the system is normally used as a thread. Currently you have to either select the emails manually or hit reply all and remove the sender email.
Has been tested and works the way I expected it to(: