Hey Eric, I figured out something (should have seen it sooner) but it might be related to COMPRESS issue. I noticed that the Maildir Message implementation returns FileInputStream for getBodyContent but SimpleMessage returns an InputStream derived from SharedFileInputStream. Our Message implementation borrowed from the Maildir implementation since we store our files individually on the file system.
For certain messages the plain text communication returns fine for a UID FETCH X (BODY.PEEK[TEXT]) but on SSL for some messages get stuck after returning the last character. After I switched to using SharedFileInputStream both returned fine. Does any of this make sense? Anyway I am now thinking that this has more to do with how COMPRESS fails on the maildir implementation as well. What do you think? Roy On Tue, Jun 26, 2012 at 5:26 AM, Eric Charles <[email protected]> wrote: > On 06/26/2012 07:45 AM, [email protected] wrote: >> Unfortunately I have yet to get around to figuring out what was wrong with >> the COMPRESS option for IMAP. Partially due to lack of time (we can deal >> with no compression for now) and partially due to my newbiness. I tried to >> grok the code for COMPRESS but was left kind of confused. I tried to follow >> the chain of command but for some reason could not find where the >> compression was actually handled. Could someone point out the class that >> actually does the compress and decompress? >> > > I still have your build which breaks the ipad. > I made test and it was indeed giving issue on my ipad, but I didn't further > investigate. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
