Bug 63166 - Email gets sent to /dev/null when disk is full.
Summary: Email gets sent to /dev/null when disk is full.
Status: RESOLVED DUPLICATE of bug 50462
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.5.3
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-23 16:11 UTC by Casey Allen Shobe
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Casey Allen Shobe 2003-08-23 16:11:11 UTC 
Version:           1.5.3 (using KDE 3.1.3)
Installed from:    compiled sources
Compiler:          gcc version 3.2.2
OS:          Linux (i686) release 2.4.20

I was expecting an email from somebody I was chatting with on gaim.

Never got it.  Never got the resends I requested.  Never got any other mail for that matter, either.

Finally figured out my disk was full when I tried a file transfer in gaim, and it reported saving the file but didn't really, and finally I tried a df, and saw that my disk was full.  So I cleared up some space, but apparently my mail that I recieved when my disk was full got deleted for me.
Comment 1 Stephan Kulow 2003-09-20 22:56:32 UTC 
Do you use maildir or mbox, IMAP or POP3?
Comment 2 Casey Allen Shobe 2003-09-20 23:26:47 UTC 
maildir, pop3.
Comment 3 Stephan Kulow 2003-09-21 10:22:35 UTC 
then I doubt your message is lost. As soon as the message write fails, kmail ends 
before marking the POP3 message as deleted. Perhaps your index isn't uptodate, 
but the message should be either still on the server or in your maildir.
Comment 4 Till Adam 2004-05-16 17:10:17 UTC 
Can you confirm that indeed no mail was lost? If so, we should probably change the description of this bug to something like: "Downloading pop mail to a full disk silently fails without showing an appropriate error message". Otherwise it should be raised in severity.
Comment 5 Till Adam 2004-05-16 20:23:36 UTC 

*** This bug has been marked as a duplicate of 50462 ***