| Summary | S/MIME bug with german umlauts |
| Queue | IMP |
| Queue Version | 6.2.2 |
| Type | Bug |
| State | No Feedback |
| Priority | 2. Medium |
| Owners | |
| Requester | flo (at) degnet (dot) de |
| Created | 09/21/2014 (4002 days ago) |
| Due | |
| Updated | 11/11/2014 (3951 days ago) |
| Assigned | 09/23/2014 (4000 days ago) |
| Resolved | 10/17/2014 (3976 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
having to disclose private certificate information?
certificate is causing the issues then. Or provide a publicly
available certificate where we can reproduce the issue.
Hi Michael,
sorry for the late reply. I've been trying to generate an example self
signed private certificate with german umlauts according to the howto
using https://gist.github.com/richieforeman/3166387 with no luck.
Horde Webmail imports the example self-signed certificate without any issues.
My private S/MIME certifcate is issued by StartSSL.
How may I provide you the information needed for debugging without
having to disclose private certificate information?
-Florian
State ⇒ Feedback
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ S/MIME bug with german umlauts
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
I'm unable to import any private S/MIME certificate into IMP webmail
which contains any german umlauts.
I guess this is an encoding issue using the MySQL backend.
Thank you for your feedback,
-Florian