Hey guys, So I've been looking at the James source code and I still can't figure out what we are doing wrong. If I'm understanding the code correctly outside of the Netty ChannelPipeline having the SslHanndler added to it there are literally no differences in how IMAP commands get handled.
This command should work the same with and without SSL right? 4 UID FETCH 1 (BODY.PEEK[TEXT]) However what I'm seeing is that without SSL the BODY.PEEK[TEXT] works fine and ends with: [body content]) 4 OK FETCH COMPLETED And with SSL all I get is the body, but it doesn't finish the fetch response: [body content] And no ending parenthesis and it just hangs when I use openssl. Running wireshark I do see that the server is still continually returning something and will continue until I close the connection. Which I suspect means I've got some weird encoding issue. Perhaps my file (that is basically rfc822) needs to guarantee to be in some charset or encoding? If anyone has a better understanding of how SSL is handled I would greatly appreciate any advice. Thanks. Roy On Wed, Nov 25, 2015 at 3:07 PM, <[email protected]> wrote: Hi guys, I'm having a weird problem with our Mailbox implementation with James 3.0 beta 4 and IMAP with SSL enabled. On some messages when I try to do the line pasted at the bottom in plain text it works fine, but with SSL (and communicating through openssl s_client OR iOS) I get stuck in some weird infinite loop. Its the BODY.PEEK[TEXT] that seems to be the problem. I was hoping someone could point out to me what exactly is different when using SSL and not using SSL? Or if someone can point out any documentation? I had this same problem a few years back using COMPRESS with IMAP and at the time I just disabled COMPRESS. We use to handle SSL separately through our load balancer but recently we have decided to handle the SSL directly through James. 4 UID FETCH 1 (BODY.PEEK[HEADER] BODY.PEEK[TEXT]) Thanks! Roy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
