[IMAP-144] DecodingException druing append

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.2
• Fix Version/s: 0.1
• Component/s: JPA Mailbox
• Environment: Linux, can't reproduce on WinXP; Thunderbird
• Assignee: Norman Maurer
• Reporter: Tim-Christian Mundt
• Created: 10/May/10 12:57
• Updated: 11/May/10 18:41
• Resolved: 11/May/10 18:41

Description

For certain messages (which I can't make public) this exception occurs:

org.apache.james.imap.decode.DecodingException: Expected end-of-line, found 'm'.
at org.apache.james.imap.decode.ImapRequestLineReader.eol(ImapRequestLineReader.java:102)
at org.apache.james.imap.decode.base.EolInputStream.eol(EolInputStream.java:67)
at org.apache.james.imap.decode.base.EolInputStream.read(EolInputStream.java:61)
at org.apache.james.imap.store.StoreMailbox.appendMessage(StoreMailbox.java:173)
at org.apache.james.imap.processor.AppendProcessor.appendToMailbox(AppendProcessor.java:137)
at org.apache.james.imap.processor.AppendProcessor.doProcess(AppendProcessor.java:74)
at org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(AbstractMailboxProcessor.java:125)
at org.apache.james.imap.processor.AbstractMailboxProcessor.process(AbstractMailboxProcessor.java:80)
at org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(AbstractMailboxProcessor.java:73)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:44)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:46)
at org.apache.james.imap.main.AbstractImapRequestHandler.doProcessRequest(AbstractImapRequestHandler.java:65)
at org.apache.james.imap.main.ImapRequestStreamHandler.handleRequest(ImapRequestStreamHandler.java:82)
at org.apache.james.imapserver.netty.ImapStreamChannelUpstreamHandler.processStreamIo(ImapStreamChannelUpstreamHandler.java:64)
at org.jboss.netty.handler.stream.StreamHandler$1.run(StreamHandler.java:127)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
INFO 13:58:32,884 | james.imapserver | failed. Mail cannot be parsed.

I can't see, what's special/wrong about that message. The letter in the end of the first line (here 'm') varies. The email at hand has the following structure:

0 multipart/mixed
1 multipart/related
1.1 multipart/alternative
1.1.1 text/plain
1.1.2 text/html
1.2 image/png
2 application/pdf

It seems this error was introduced by switching to streaming, because it doesn't occur with the version I still have from before that - just an assumption.