Support more than 1 level deep of multipart data in incoming emails about maildrop HOT 4 CLOSED

Actually, I added some debugging, and it looks like our email is failing to be parsed.

When getContent() is called on the multipart message, it is returning a "SharedInputStream" instead of a "Multipart".

Maybe you can help point me in the right direction of how to fix this.

from maildrop.

Ugh-- this message is one of those rare types that makes parsing RFC1341 messages such a pain. The real solution here is to set up a recursive method that goes through a mime multipart and just grabs all text parts, and recursively calls itself for any multipart content items. Once you have the list of all text parts, you could probably just concatenate them together-- that would make the web display easier (we aren't trying to be Gmail after all).

from maildrop.

Actually...it turns out that your code is going 2-levels deep, which is good enough.

The problem mainly lies in Exceptions being squelched, so I couldn't figure out the root cause. I'm going to close out this ticket and create 2 new ones that are more descriptive.

from maildrop.

Encountering with a similar issue, note the previous commit might fix.
Considering I have no idea what I just did, and little understanding what's going on, ... I can still confirm error message's gone ...

from maildrop.