Bug 332323 - Error in IMAP command UID: Too long argument
Summary: Error in IMAP command UID: Too long argument
Status: RESOLVED DUPLICATE of bug 340622
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.12
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-19 13:54 UTC by Malte S. Stretz
Modified: 2014-11-04 09:52 UTC (History)
3 users (show)

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


Attachments
Output collected via KIMAP_LOGFILE (142.46 KB, text/plain)
2014-03-19 13:56 UTC, Malte S. Stretz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Malte S. Stretz 2014-03-19 13:54:15 UTC
I regularly get an error popup which tells me "Error in IMAP command UID: Too long argument".

I finally found the time to debug this and posted the relevant IMAP output below. The affected folder seems to be a mailinglist folder with lots of old mail. I have auto-expiry configured for that folder so maybe that triggers the issue.

The server is running a rather old Dovecot 1.1.11-0ubuntu11.

Reproducible: Always

Steps to Reproduce:
1. Open KMail
2. Wait (probably until mail arrives)
3. Error
Actual Results:  
Will be attached ("Comments cannot be longer than 65535 characters.")

Expected Results:  
No error
Comment 1 Malte S. Stretz 2014-03-19 13:56:19 UTC
Created attachment 85636 [details]
Output collected via KIMAP_LOGFILE
Comment 2 Malte S. Stretz 2014-03-19 13:56:49 UTC
In xsession-errors I also found:

kmail2(8532) MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill: Circular In-Reply-To reference loop detected in the message tree 
kmail2(8532) MessageList::Core::ModelPrivate::findMessageParent: Circular In-Reply-To reference loop detected in the message tree 
 list is empty 
A message was received from the server with no job to handle it: "* BAD Error in IMAP tag: Too long argument. " "(2a20424144204572726f7220696e20494d4150207461673a20546f6f206c6f6e6720617267756d656e742e20)"
Comment 3 Christian Mollekopf 2014-11-04 09:52:25 UTC
Thanks for the report, I'll track this in a separate ticket.

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