Bug 288920

Summary:	Append failed, server replied: A000002 BAD invalid APPEND command syntax, invalid message flags list syntax
Product:	[Applications] kmail2	Reporter:	gianted <gianted>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	igor.larionovo, swisscarbon, tmp_prince-promo
Priority:	NOR
Version:	1.99.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description gianted 2011-12-13 21:12:45 UTC

Version:           1.99.0 (using KDE 4.7.3) 
OS:                Linux

Append failed, server replied: A000002 BAD invalid APPEND command syntax, invalid message flags list syntax. It happens sometimes in tray system notifier.

Reproducible: Sometimes

Steps to Reproduce:
Not easily to reproduce... it seems to appear browsing IMAP folders.


Expected Results:  
No error message.

OS: Linux (i686) release 3.0.0-14-generic
Compiler: gcc

Comment 1 gianted 2011-12-15 23:18:50 UTC

(In reply to comment #0)
> Steps to Reproduce:
> Not easily to reproduce... it seems to appear browsing IMAP folders.

I retry again and it seems to be reproducible when a message is notified as "sent".

Comment 2 Igor Larionovo 2012-11-05 15:14:26 UTC

Same issue here.
I get the same error.
It happens when I send messages.
It happens to me with email accounts @bluewin.ch mapped via IMAP.

Sent messages are then stored locally rather than on the server (which is a pain in the neck).

All my other IMAP accounts work fine.

Comment 3 Carlo Alberto Sanjust 2013-09-23 11:48:57 UTC

The problem is related to the $SENT flag.
Akonadi debug log says:

C: A000035 APPEND "Sent" (\Seen $SENT) {422}
S: A000035 BAD invalid APPEND command syntax, invalid message flags list syntax

Whereas the server supports: FLAGS ( \Answered \Flagged \Deleted \Seen \Draft $MDNSent $fax $urgent $voice)

Comment 4 swisscarbon 2013-09-23 12:45:27 UTC

this is a dublicate of: https://bugs.kde.org/show_bug.cgi?id=291332

Comment 5 Denis Kurz 2016-09-24 18:02:17 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 6 Denis Kurz 2017-01-07 22:26:06 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.