Summary: | copy sent mail in sent folder failed: user@aim.com: Append failed, server replied: A000077 NO APPEND failed | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | themroc <rauchweihe> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | major | CC: | hofrichter, tobias |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
themroc
2012-02-10 20:04:15 UTC
Same bug here for kmail 4.8.4 with Freenet. Sent e-mail is not stored in imap "sent folder" but definitely sent. Error message is: "Freenet Mail: Append failed, server replied: A000437 NO Error in IMAP command received by server." Ok the problem seems to be related to storing the wrong flags. Starting akonadi with
>export KIMAP_LOGFILE=/tmp/imap.log
>akonadictl restart
and inspecting the imap log file yields:
C: A000113 SELECT "INBOX.sent"
S: * FLAGS ( \Draft \Answered \Flagged \Deleted \Seen \Recent )
S: * OK Limited [ PERMANENTFLAGS ( \Draft \Answered \Flagged \Deleted \Seen ) ]
S: * 296 EXISTS
S: * 0 RECENT
S: * OK Ok [ UIDVALIDITY 1070205188 ]
S: * OK ACL [ MYRIGHTS acdilrsw ]
sending an email gives the following output in the log file:
C: A000130 APPEND "INBOX.sent" (\Seen $SENT) {349}
S: A000130 NO Error in IMAP command received by server.
C: A000131 LIST "" *
As far as I understand the $SENT flag is not supported by the server and should not be appended.
using the patch for bug 278082 fixes the problem *** Bug 327849 has been marked as a duplicate of this bug. *** 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. 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. |