You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a recipient of the mailing list I have no option to easily reply to All and / or reply to the sender.
ETA: 11/01
Expected result
What Thunderbird does is offer 3 options:
Reply to the list: writes a mail to the mailing list
Reply to all: Writes to the sender, to the list and potentially other recipients
Reply: Writes only to the sender
Reply:
Reply to list:
Reply to all:
Current behavior
I only have 2 options: reply and Reply All:
Reply actually replies to the list.
ReplyAll is buggy...
Additional information
If an email contains the List-Post: <mailto:[email protected]> header then it should be used to create a Reply to list button.
If I click it then it composes a reply to the list. If the List-Post header is absent then the Reply to list shall not be displayed,
Design:
Backend will then rewrite the Reply-To header to the original sender, and we would have the expected behaviour.
The text was updated successfully, but these errors were encountered:
Description
As a recipient of the mailing list I have no option to easily reply to All and / or reply to the sender.
ETA: 11/01
Expected result
What Thunderbird does is offer 3 options:
Reply to the list
: writes a mail to the mailing listReply to all
: Writes to the sender, to the list and potentially other recipientsReply
: Writes only to the senderReply:
Reply to list:
Reply to all:
Current behavior
I only have 2 options: reply and Reply All:
Reply actually replies to the list.
ReplyAll is buggy...
Additional information
If an email contains the
List-Post: <mailto:[email protected]>
header then it should be used to create aReply to list
button.If I click it then it composes a reply to the list. If the
List-Post
header is absent then theReply to list
shall not be displayed,Design:
Backend will then rewrite the
Reply-To
header to the original sender, and we would have the expected behaviour.The text was updated successfully, but these errors were encountered: