Version: 1.9.5 (using KDE KDE 3.5.5) Installed from: Debian testing/unstable Packages OS: Linux 1. New message... 2. Attach a file 3. Check the Compress checkbox 4. Save the message in the Drafts folder 5. Edit (reopen) the message in the Drafts folder 6. The filename has got the .zip extension, but the Compress checkbox is not checked. So it is impossible to uncompress the attachment (ie. remove the zip extension, and send the file uncompressed). However, this is possible by deleting and adding the attachment again (<- inconvenient). Also, when checking the Compress checkbox again, KMail tries to compress the already compressed file attachment... I think KMail should remember whether a message's attachments were compressed or not, and provide an option to uncompress the file, thus sending it in the original form.
Exact same thing happens for me. Debian testing, kmail 1.9.5.
Then in this case, a potential solution would be to check if the extension of the attachment is .zip. If it is, there's a chance it was compressed by KMail, and if it wasn't compressed by KMail, then compressing it won't do much (assuming it's a valid Zip Archive).
still reproducible with kmail trunk 861109
Created attachment 27438 [details] Fix: if a new attachment that ends with .zip is created then the compress option gets checked
Thanks for the patch, but looking into this more deeply I found it to be not so trivial, as clicking on the already checked "compress" to uncompress the draft mail attachment again (after! reopening the mail from the drafts folder) leads to the problem that the MIME type and charset is no longer known. It seems a more complex patch is needed ...
Valid in master with the given steps
I confirm it.Will look at it.
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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
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.