[Bug 50462] mail is permanently lost if disk is full

[Juan I.Guardia]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=50462         




------- Additional Comments From guard001 jguardia com  2007-04-16 04:44 -------
I can also confirm that this bug is still around (KDE 3.5.6, KMail 1.9.6).  My / (which includes /tmp) and /home are in different partitions.  However, as opposed to what is described by comment #61, it is / which ran out of space. /home still has plenty of space left.  As I checked mails this morning KMail went through the process as it usually does.  No warnings, no crashes, no message boxes.  Both my local as well as POP3 accounts were checked for incoming mail with no problems.  But when I checked their respective folders, however, only the supposedly NEW mails were bogus (Subject: No Subject; Sender: Unknown; Date: unknown; size: 177 B).  All my old mail is there, I can even open their attachments.  So this also confirms my mail folders are intact.

I haven't had a chance to closely study the KMail code, but I can conclude from the comments attached to this bug and my experience as described above that at some point in the mail checking chain of events the NEW messages must be stored SOMEWHERE in / (my guess would be /tmp from what I have read).  I can try to step through KMail with a debuger to see where in the code this happens and go from there, but I am sure the KMail developers are much better at this than I am.  With regards to comments #48 and #50, this IS fully reproducible, as it has happened to me twice under the same circumstances.  To reproduce:

1. Make sure /home is in a separate partition from / (and /tmp, in my case).
2. Fill up / so it gets to 100% capacity. /home should have plenty of space left.
3. Check your mail.  NEW mail is bogus (and lost forever, since it was deleted from mail server).  Old mail should be there.
4. Free up enough space in / .
5. Check mail again.  NEW mail (since step 3) is now as it should be.