Version: 1.5.4 (using KDE 3.1.4) Installed from: SuSE Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-166-default add-on to bug 28072, but additionally it has to be mentioned that the draft message converts all ä, ü, ö to some =FC and so on. Expected behaviour would be: - save message same way it is edited, with umlauts in it - sign it when it is sended, not before - automatically removing signature as proposed in 28072 is not really solving the problem.
Umlauts can't be sent over the Internet as is (at least it's not safe because they could be mangled during transport). They have to be encoded as =FC etc. Anyway, where do you see =FC? You should only see this if you view the source of a message. But that's no bug. You don't have to care for the internal encoding of a message. Your comments about pgp signing are duplicates of bug 28072. So I won't comment on them. Vote for bug 28072 if you want.
If you open the draft message and try to edit it, you get all the =FC presented.
Please save a test message as draft, view the source of this test message and add the source code of the test message to this bug report. Do you also get =FC, etc., if the draft is not signed?
If the draft is not signed it looks OK. BTW, the source code of the message seems to be somewhat encrypted....
Created attachment 4537 [details] Saved draft without signature
Created attachment 4538 [details] Same draft with signature
I can't reproduce the problem with the two attached messages (neither with KMail 1.5.4 nor with KMail 1.6). But those messages were base64 encoded (what you described at "somewhat encrypted") and not quoted-printable encoded as the message which causes the problem. I doubt that you can reproduce the problem with those messages. Please provide a signed message which you can reproduce the problem with. Hint: Use less umlauts and more normal characters.
Created two new message which worked better. To reproduce: save the signed message as draft and then open it for editing, which reproduces the bug. If you first close KMail, it displays the valid signature and does *not* show the funny signes when opened for editing.
Created attachment 4568 [details] new testfile w/o signature
Created attachment 4569 [details] message with signature
Created attachment 6280 [details] Example of message before saving as a draft This is a message as it was shown in a composer before saving as a draft.
Created attachment 6281 [details] This is how message looks after saving, reopening and saving again After saving as draft, opening in composer and saving again, this is the result (and yes, in Composer I get similar garbage). Happens only for encrypted drafts (S/MIME in my case).
Created attachment 6282 [details] Message as saved OK, this is concerned message (but probably not much of use to you, because you don't have a key to descrabmle it (BTW, the message was only signed, NOT encrypted).
I've passed a pgp signed mail through all the mail stages (new, draft, save, open, send, receive, trash, save, load, ...) and it still has all the Spanish non-ascii characters right using kmail 1.10.1.
I can't reproduce in 1.10.1 with german umlauts either.