I Created a Bug-Report under IMAP-362 <https://issues.apache.org/jira/browse/IMAP-362>

Is there any workaround, that i can prevent such malformed mails from being delivered to the mailboxes at all?

Simon

On 01.04.2012 11:43, Eric Charles wrote:
the best is that you open a JIRA (https://issues.apache.org/jira/browse/IMAP) so we don't forget to treat that (should be easy to have a unit test that simulates this, and then finding a fix).

thx, Eric

On 01/04/12 10:38, Simon Klaiber wrote:
For the Problem to occur the Body really needs to have a length of 0

When I send a mail wit an empty body with Thunderbird MAIL_BYTES is 2
Bytes long and contains HEX 0D 0A

But you are right even if I clear MAIL_BYTES I cant recreate the problem.

The Mails that cause the problem are those "completely empty" Spam Mails
you get from time to time. The next I get I will try to export to find
out what the problem is.

Thanks for the Quick Reply
Simon



On 01.04.2012 10:13, Eric Charles wrote:
Hi Simon,

mime4j warning does imply there's a bug.

I sent a mail with nothing in the body, and I can move it from a
folder to another. Have you got a scenario I can replay to show the
issue?

Thx, Eric

On 01/04/12 09:54, Simon Klaiber wrote:
Hello,

after upgrading from James 2 to James 3b3 i encounter Problems when
using IMAP.

They occur as soon there is a Mail with a Empty Mailbody (
length(MAIL_BYTES) = 0) )
I encounter this problem with Thunderbird and with iOS Mail.

It is very obvious but not necessarily limited to when you try to move
such a message to another folder (for instance Junk Mail Controls in
Thunderbird) but also when updating the specific folder from iOS Mail.

In the Logs i get following Warnings when this happens:

jvm 1 | WARN 09:34:02,449 | org.apache.james.mime4j.parser.MimeEntity |
Unexpected end of headers detected. Higher level boundary detected or
EOF reached.
jvm 1 | WARN 09:34:02,449 | org.apache.james.mime4j.parser.MimeEntity |
Invalid header encountered


As soon as I delete these data sets from the JAMES_MAILBOX Table
everything works alright again.

I run on Ubuntu Linux with MySQL as jpa store.

Thanks
Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



Reply via email to