Prerequisites

• [×] I have searched open and closed issues to make sure that the bug has not yet been reported.

Bug report

Describe the bug
The one-click unsubscribe feature has the following configuration choices:

• Original action: Use the same unsubscribe policy set by your sender. SimpleLogin will make sure to hide your mailbox address.¹
• Disable alias: The unsubscribe action will disable the alias that received the email.
• Block contact: The sender of the email will be blocked: you won't receive emails from this sender to your alias anymore.

Information is lost when disable alias is set. The original action is needlessly destroyed when it could be preserved under a different header.

Expected behavior
When disable alias is set, inbound messages containing a List-Unsubscribe: header should be altered conservatively, to preserve header info. The contents of List-Unsubscribe: should be moved to X-SimpleLogin-Original-List-Unsubscribe:.

There is no good reason to throw that information away. To give a concrete example of a situation I am facing at the moment, I received many marketing emails from my bank. I obivously cannot disable the alias because the bank may need to send more legitimate messages in the future. So I need the bank’s unsubscribe link in order to obtain a more granular cancellation of e-mail traffic than what SimpleLogin can offer.

Alias disabling is a blunt intrument. But at the same time it can still be useful in some situations. So users face an inconvenient choice: give up the sender’s unsubscribe action or give up the convenience of a one-click alias disabler. I was forced to give up the alias disabler.

Bug vs. Feature

Folks might debate over whether this is a feature request or bug report. I firmly assert that it is a bug report because needless loss of useful information is always bug. The original List-Unsubscribe: data should not be lost no matter what configuration the user selects.

Footnotes
¹ What does this mean: “SimpleLogin will make sure to hide your mailbox address.” ?? The sender’s unsubscribe feature would not know about the mailbox address so simply passing that information through verbatim poses no risk of exposure. The documentation should probably clarify that.