Bug 137139 - Error while uploading message
Summary: Error while uploading message
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Unmaintained
Component: IMAP (other bugs)
Version First Reported In: 1.9.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-10 06:44 UTC by Lincoln Peters
Modified: 2009-12-30 23:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lincoln Peters 2006-11-10 06:44:07 UTC
Version:           1.9.5 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-2 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17.7lincoln

Lately, I've been seeing the following error pop up about 8 times in a row when I check my e-mail on a disconnected IMAP account (running Dovecot 0.99.14):

Error while uploading message
Could not upload the message dated from <unknown> with subject <unknown> on the server.
The destination folder was Junk, which has the URL imap://lincoln@localhost:143/Junk/;SECTION=\SEEN.
The error message from the server communication is here:
Append aborted.


I have recently upgraded both KMail and Dovecot, so I'm not at all sure which is responsible for the error.
Comment 1 Philip Rodrigues 2006-11-11 22:32:21 UTC
Do you get similar errors if you use a different mail client? That might give a clue as to whether the problem is with the mail server
Comment 2 Lincoln Peters 2006-11-13 06:17:34 UTC
Thunderbird 1.5.0.4 (same computer): No errors.
Mac Mail (on a Mac running OSX 10.4): No errors.

Looks like a KMail issue.


I also noticed that Thunderbird completed a check for new mail significantly faster than KMail, even when both were running on the same computer.  That is probably irrelevant to this bug, but I thought I should mention it, just in case there's a connection.
Comment 3 Björn Ruberg 2009-12-30 23:56:11 UTC
Is this still a problem in KDE 4.3?