mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 14:15:53 +03:00
[GH-ISSUE #273] My email client has a fit when receiving encrypted mail from aliases #233
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#233
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CaptainFrosty on GitHub (Feb 26, 2022).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/273
That's the only way I know how to describe it. I had to turn encryption off. Only the header will load on the screen and it blinks very fast. When I get a chance I'll try sending one with the debug logs on and see if I can uncover anything.
I'm using eM Client on Windows. The key is stored in it.
@willbrowningme commented on GitHub (Mar 3, 2022):
Are you sure this isn't just an issue with eM Client?
Have you tested sending an encrypted message not through AnonAddy to see if the result is the same?
@willbrowningme commented on GitHub (Mar 13, 2022):
Closing this as I don't think it's related to AnonAddy.
@CaptainFrosty commented on GitHub (Mar 13, 2022):
@willbrowningme The blinking stopped thankfully when I updated it. Probably a database issue; this client seems prone to them. The pgp is working normally now, so that's good. I do get this message:
But it doesn't seem to affect anything.
@CaptainFrosty commented on GitHub (Mar 13, 2022):
And no, it doesn't happen on messages outside of the server, I made sure of that. Odd that the message itself checks out fine...it's only the signature.
@willbrowningme commented on GitHub (Mar 13, 2022):
Glad you sorted it. Don't worry about the cerificate signature warning, it's a known issue - https://github.com/anonaddy/anonaddy/issues/164
It's because the signing key has identity
mailer@anonaddy.mewhich doesn't exactly match the identity of the alias xyz@anonaddy.me etc.@CaptainFrosty commented on GitHub (Mar 31, 2022):
@willbrowningme I see. So unfortunately everyone I send encrypted emails to will see a certificate error? That's not good. It seems like there should be a way to generate keys that share a public key with the signing identity or something like that. Or perhaps I could make another key with that identity?
@willbrowningme commented on GitHub (Apr 1, 2022):
The signature identity mismatch warning is only present on forwarded messages so nobody else will see this.
If you want to send an encrypted email to someone from an AnonAddy alias then you need to encrypt it with their public key and send it as you normally would.
You don't want to sign it with your real email's private key because this would reveal your real email to them. So you can either not sign the message at all, or create a private key for that exact alias and sign it with that, so the identities match.
@CaptainFrosty commented on GitHub (Apr 4, 2022):
@willbrowningme That's what I was thinking, to create a few aliases exclusively for pgp and generate keys for those. It's kind of a pain that pgp uses email addresses for identity purposes rather than some other mechanism, but that's what keeps it decentralized I guess. My client supports aliases, so maybe I can get rid of the warning by setting a policy for the alias.