| Summary: | Signature failed: secret key specification is ambiguous | ||
|---|---|---|---|
| Product: | Claws Mail (GTK 2) | Reporter: | Clark Williams <clark.williams> |
| Component: | Plugins/Privacy/PGP | Assignee: | users |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.8.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
Ah, meant to add that this is on Fedora 16, using the Fedora package.
Loaded plugins:
Dillo
PGP/Core
PGP/MIME
Python
RSSyl
Do you have another account using the same email address, but without using "Specify key manually" in its GPG preferences ? Can you attach a --debug output ? I had a PEBCK, because I had two keys on my keyring with the same email address. I removed one of them and have no issues signing messages now. Sorry for the noise. That's not a real fix |
on my gmail account, when replying to an email thread, I get the $SUMMARY message in a popup dialog. The full text reads: Could not queue message for sending Signature failed: secret key specification is ambiguous I suspect that this is because I have two keys in my keyring which both have clark.williams@gmail.com as the listed email address. I believe this works ok on regular composes because I selected the "Specify key manually" preference and selected the appropriate key id. Guessing that reply doesn't use that logic?