[GH-ISSUE #571] Feedback regarding updated Display From Format #975

Closed
opened 2026-03-14 11:20:41 +03:00 by kerem · 1 comment
Owner

Originally created by @vlad-tim on GitHub (Dec 9, 2023).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/571

Hi there, thanks for a new major version with the revamped UI. I have updated from v0.14.1 to v1.0.4 and it went mostly smoothly, but I encountered one issue, which took me some time to figure out, and I wanted to leave feedback.

Apparently the default From header format was changed

from
sender@sendersdomain.com <somealias+sender=sendersdomain.com@mydomain.com>
to
sender at sendersdomain.com <somealias+sender=sendersdomain.com@mydomain.com>

This caused my email filters to break because they match From header by patterns like sender@sendersdomain.com , which conveniently is an actual sender email address, but with the new format it no longer matches. I am currently considering to update my filters to match somehow differently, for example by sender at sendersdomain.com or sender=sendersdomain.com, or maybe switch to the custom header X-AnonAddy-Original-Sender header, because there doesn't seem to be an option to keep the prior format , and I could not find a specific issue/PR that clarifies the need for the change.

Question 1: out of curiosity, what was the rationale for this change?

Suggestion 1: outline this as a breaking change in the release log, so folks who update can quickly spot it.

Originally created by @vlad-tim on GitHub (Dec 9, 2023). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/571 Hi there, thanks for a new major version with the revamped UI. I have updated from `v0.14.1` to `v1.0.4` and it went mostly smoothly, but I encountered one issue, which took me some time to figure out, and I wanted to leave feedback. Apparently the default `From` header format was changed from `sender@sendersdomain.com <somealias+sender=sendersdomain.com@mydomain.com>` to `sender at sendersdomain.com <somealias+sender=sendersdomain.com@mydomain.com>` This caused my email filters to break because they match `From` header by patterns like `sender@sendersdomain.com` , which conveniently is an actual sender email address, but with the new format it no longer matches. I am currently considering to update my filters to match somehow differently, for example by `sender at sendersdomain.com` or `sender=sendersdomain.com`, or maybe switch to the custom header `X-AnonAddy-Original-Sender` header, because there [doesn't seem to be an option to keep the prior format](https://github.com/anonaddy/anonaddy/blob/dc88b9bcd25f8a4f5f394bb51b03473ca338bea0/app/Mail/ForwardEmail.php#L385-L398) , and I could not find a specific issue/PR that clarifies the need for the change. Question 1: out of curiosity, what was the rationale for this change? Suggestion 1: outline this as a breaking change in the release log, so folks who update can quickly spot it.
kerem closed this issue 2026-03-14 11:20:47 +03:00
Author
Owner

@willbrowningme commented on GitHub (Dec 11, 2023):

Thanks for the feedback, this was added with v1.0.0 along with the rebrand update. To be honest I completely forget to mention it. I've just added it to the release notes now - https://github.com/anonaddy/anonaddy/releases/tag/v1.0.0

The reason for the change is to reduce the chance of messages being rejected as spam. If an email is forwarded and the display from part of the From header is support@paypal.com for example then many email providers will assume this to be a phishing attempt and reject the message.

<!-- gh-comment-id:1850293091 --> @willbrowningme commented on GitHub (Dec 11, 2023): Thanks for the feedback, this was added with v1.0.0 along with the rebrand update. To be honest I completely forget to mention it. I've just added it to the release notes now - [https://github.com/anonaddy/anonaddy/releases/tag/v1.0.0](https://github.com/anonaddy/anonaddy/releases/tag/v1.0.0) The reason for the change is to reduce the chance of messages being rejected as spam. If an email is forwarded and the display from part of the From header is `support@paypal.com` for example then many email providers will assume this to be a phishing attempt and reject the message.
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#975
No description provided.