[GH-ISSUE #164] Keys not matching #164

Closed
opened 2026-03-01 17:45:23 +03:00 by kerem · 4 comments
Owner

Originally created by @a7x-bit on GitHub (Jun 2, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/164

Hi,

Can you explain why keys are not matching from mailer@annonaddy.me?

I am getting error
"Encrypted but end to end key did not match the sender"

Originally created by @a7x-bit on GitHub (Jun 2, 2021). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/164 Hi, Can you explain why keys are not matching from mailer@annonaddy.me? I am getting error "Encrypted but end to end key did not match the sender"
kerem closed this issue 2026-03-01 17:45:24 +03:00
Author
Owner

@willbrowningme commented on GitHub (Jun 3, 2021):

This is because your email client is using the From: header to check the key's identity.

However the From: header on AnonAddy is set to the alias email address.

It would not be feasible to add every alias email addresss as an identity to the "mailer@anonaddy.me" signing key. It also isn't really feasible to create a new signing key for every single alias so that it matches.

At the moment I'm not sure if there is any solution for this, except for sending every single forwarded email from "mailer@anonaddy.me" but then this would break many users mail filters etc.

I will have a think and see if I can come up with anything.

<!-- gh-comment-id:853688186 --> @willbrowningme commented on GitHub (Jun 3, 2021): This is because your email client is using the From: header to check the key's identity. However the From: header on AnonAddy is set to the alias email address. It would not be feasible to add every alias email addresss as an identity to the "mailer@anonaddy.me" signing key. It also isn't really feasible to create a new signing key for every single alias so that it matches. At the moment I'm not sure if there is any solution for this, except for sending every single forwarded email from "mailer@anonaddy.me" but then this would break many users mail filters etc. I will have a think and see if I can come up with anything.
Author
Owner

@a7x-bit commented on GitHub (Jun 3, 2021):

Thanks. Basically, key identity has to match allias email to work. Maybe ok for few keys, I can see this being a issue.

<!-- gh-comment-id:853933035 --> @a7x-bit commented on GitHub (Jun 3, 2021): Thanks. Basically, key identity has to match allias email to work. Maybe ok for few keys, I can see this being a issue.
Author
Owner

@willbrowningme commented on GitHub (Feb 4, 2022):

Closing this for now as there is no solution to this issue that I'm aware of that would allow emails to be forwarded from aliases whilst having an exact identity match for the signing key.

<!-- gh-comment-id:1030122916 --> @willbrowningme commented on GitHub (Feb 4, 2022): Closing this for now as there is no solution to this issue that I'm aware of that would allow emails to be forwarded from aliases whilst having an exact identity match for the signing key.
Author
Owner

@xyhhx commented on GitHub (Feb 6, 2024):

except for sending every single forwarded email from "mailer@anonaddy.me" but then this would break many users mail filters etc.

Can you make this a configurable option? Then, along with the Reply-To: header, a filter could probably be created

<!-- gh-comment-id:1929730965 --> @xyhhx commented on GitHub (Feb 6, 2024): > except for sending every single forwarded email from "[mailer@anonaddy.me](mailto:mailer@anonaddy.me)" but then this would break many users mail filters etc. Can you make this a configurable option? Then, along with the `Reply-To:` header, a filter could probably be created
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#164
No description provided.