Bug 309968 - Encrypting email malfunctions
Summary: Encrypting email malfunctions
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepim
Classification: Applications
Component: messagecore (show other bugs)
Version: 4.9
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 14:39 UTC by Steve
Modified: 2017-01-07 22:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Steve 2012-11-12 14:39:09 UTC 
On kmail3, sending encrypted email works fine. After migrating to kmail4 (4.9.3 specifically), I can no longer exchange encrypted emails with anyone. I get a generic error that seems meaningless:  Could not compose message: general failure.  That doesn't give me a clue as to how to solve the problem. Reading encrypted emails works fine, its just the sending that is broken.

Reproducible: Always

Steps to Reproduce:
1. Receive encrypted email
2. Reply such that it will be encrypted
3. Click send
Actual Results:  
vague error message

Expected Results:  
mail sent encrypted
Comment 1 Laurent Montel 2012-11-12 14:54:46 UTC 
Need more infos.
I can send encrypted emails.
Verify your encrypt settings etc.
Comment 2 Steve 2012-11-12 15:13:24 UTC 
Its configured to use OpenPgp/Mime via gpg. Looking around, there are next to no settings to configure. What would you need to see? I haven't changed anything from kmail3 and it migrated via the migration tool.
Comment 3 Denis Kurz 2016-09-24 20:59:57 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:21:33 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.