Summary: | next message is selected after deleting attachment | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Antonio Rojas <arojas> |
Component: | disconnected IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andres.karner, bb_64, bjoern, kde.bugs, kollix, mey.wer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Antonio Rojas
2009-11-16 10:45:09 UTC
Works for me in KDE 4.4.0 No, still happens in 4.4.1 *** Bug 229007 has been marked as a duplicate of this bug. *** *** Bug 229564 has been marked as a duplicate of this bug. *** This is really ennoying. also would be nice to have the possibility to choose „delete all attachements“ right-clicking in one message... Even worse is another buggy behavior: (using imap and lokal mbox-format) copy an e-mail with attachement to a lokal e-mail-folder „bla“ after deleting the attachment of e.g. 5 MB the message is shown as e.g. to have 125 KB But the file /home/user/.kde/share/apps/kmail/mail/bla has become 5 MB larger instead of 5 MB smaller!!!!! (using kmail 3.5.7. - quite old version for the only reason, that there is no newer kmail-standalone-package - installing newer kde in older linux (opensuse 10.3) is nearly impossible - using newer linux (opensuse) brings many problems - and kde4 works worse than kde3 (e.g. worse printing-funktionality, missing kcontrol) So please, have an idea to solve that problem for kde3.) I think, it could be a problem for large e-mail-folders (mbox-files) on a nearly full harddisk. In thunderbird compressing an “e-mail-folder” (means a file in mbox-format) writes a new file and then replaces the former with the new. So it needs place for the temporary data. I suppose, kmail does something similar. If there is no place to write the temporary data, it failes. ??? What does kmail? Where does it write? (I could give another path, where there is enough space.) *** Bug 298373 has been marked as a duplicate of this bug. *** Can't reproduce anymore in 4.11 |