My correspondent sent me a message that I could decipher (so he has my
public key). I could also check his signature: I have his public key,
and he signed well with his private key.
It gets tough, when I want to send him an encrypted message. It's
impossible. An Enigmail alert message appears (2 times in a row),
telling me that "The ID of the key" Ox1F ... "configure is not in your
keychain."
I guess it's due to my many tries. The requested key must be an old key
that is no longer in my keychain (and is no longer usable). I feel that
Enigmail did not really delete it.
Of course, I start all over again, completely removing Gpg4win and
Enigmail (and even passing Ccleaner), but nothing works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Enigmail will never automatically delete any key. It looks to me like the old key of your correspondent is expired or revoked, and you don't have any newer key.
You should ask your correspondent to send you their current public key, such that you can reply encrypted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I am fully aware that Enigmail will never automatically delete a key. That's not my problem.
I deleted the old key, and I have (in my keychain) the new key of my correspondent. The problem is that Enigmail still wants to work with the old key, whereas it is no longer in my keychain.
This looks like you have a per-recpient rule for the correspondent; either self-created or from autocrypt. Please go to menu Enigmail > Edit Per-Recipient Rules and search for the email address of your correspondent. Delete any rule you find that is associated with the email address.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I had thought of that, so I had to delete everything. That said, as the problem persisted, I preferred to add a new rule to try to force Enigmail, but it still did not work. See the attached screenshot.
Pursue your advice, so I removed the rule, but the problem still persists.
I thank you for your answer, but I was seeing this debug log file, and I thought there was really too much personal information (and the file is extremely long).
Anyway, I'm installing my system on a new computer, and we'll see what happens.
Thank you again for your help.
Regards,
Henry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone.
My correspondent sent me a message that I could decipher (so he has my
public key). I could also check his signature: I have his public key,
and he signed well with his private key.
It gets tough, when I want to send him an encrypted message. It's
impossible. An Enigmail alert message appears (2 times in a row),
telling me that "The ID of the key" Ox1F ... "configure is not in your
keychain."
I guess it's due to my many tries. The requested key must be an old key
that is no longer in my keychain (and is no longer usable). I feel that
Enigmail did not really delete it.
Of course, I start all over again, completely removing Gpg4win and
Enigmail (and even passing Ccleaner), but nothing works.
Enigmail will never automatically delete any key. It looks to me like the old key of your correspondent is expired or revoked, and you don't have any newer key.
You should ask your correspondent to send you their current public key, such that you can reply encrypted.
Hello and thank you for your answer.
Yes, I am fully aware that Enigmail will never automatically delete a key. That's not my problem.
I deleted the old key, and I have (in my keychain) the new key of my correspondent. The problem is that Enigmail still wants to work with the old key, whereas it is no longer in my keychain.
You will find attached 2 screenshots.
This looks like you have a per-recpient rule for the correspondent; either self-created or from autocrypt. Please go to menu Enigmail > Edit Per-Recipient Rules and search for the email address of your correspondent. Delete any rule you find that is associated with the email address.
Yes, I had thought of that, so I had to delete everything. That said, as the problem persisted, I preferred to add a new rule to try to force Enigmail, but it still did not work. See the attached screenshot.
Pursue your advice, so I removed the rule, but the problem still persists.
That's weird. Can you attach a debug log file?
https://enigmail.net/index.php/en/faq-en?view=topic&id=15
Hello.
I thank you for your answer, but I was seeing this debug log file, and I thought there was really too much personal information (and the file is extremely long).
Anyway, I'm installing my system on a new computer, and we'll see what happens.
Thank you again for your help.
Regards,
Henry