Chris writes:
Your message was sent, but an error occurred during post-processing. The reported error was "Failed to append to INBOX/Sent: Error appending message: Stream has outstanding operation Appending to local 'Sent' folder instead.".
This error message is coming from your IMAP client, which you say is Evolution. There's no such error message in the IMAP server.
I can find this error message in Evolution's binaries. $ strings /usr/lib64/evolution/3.10/libemail-engine.so | fgrep 'Failed to append' Failed to append to %s: %s Failed to append to local 'Sent' folder: %s
Another error that I've just noticed when attempting to mark all messages in 'Inbox' as read: Failed to mark messages as read. The reported error was "No IMAP namespace for folder path 'INBOX'".
This also looks like an error from your IMAP client, which you say is Evolution. I can also see this error message in one of Evolution's modules.
This looks like either a misconfiguration or a bug in Evolution. The fact that you can actually access INBOX, and that one of the errors occurs only when you're simply trying to mark existing messages as read, points to an Evolution bug.
Google is full of bug reports, that references this error message; but a quick search doesn't find any response or a solution from Evolution.
None of the other folders give this error when marking all messages as read. Inbox is not an actual folder in Maildir on my box it consists of cur, new, tmp. The rest of the folders are such as .AgentOrange and so forth. I'm honestly not sure these even relates to courier imapd but I've tried in the Ubuntu and Evolution lists and though I've received replies no one is quite sure. Any guidance or suggestions would be greatly appreciated.
It
I do have one 'debug.txt' file in my Maildir folder and doing some Googling it seems to belong to imapd but I could be wrong on that. This is only a small portion of the entire file. I could compress and attach it to another post if someone would want to see it.
Looks like you have an option set in the imapd configuration file that creates this log file. This is a log file. Feel free to remove it, or the IMAPDEBUGFILE option in the imapd configuration file.
This file logs the raw messages received from the IMAP client, and the response. In some situation it is useful in tracking down IMAP client bugs, but in this case it looks like Evolution just chokes on itself, without really sending any command to the server. You could certainly leave the config setting in place, remove the log file, start Evolution, and execute the operation that causes the error, then look at the log file to see what commands Evolution sends, and what the responses are. That might be useful to look at, but all that will do is, at the most, identify what commands Evolution is sending, and what's wrong with them, if at all – but, as I said, it's likely that Evolution is not sending anything, but gets confused for some reason.
pgpaPKZ6mFfHV.pgp
Description: PGP signature
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
