Hi Roy,
See comments inline.
Thx, Eric
On 04/11/2012 08:22 PM, [email protected] wrote:
Hi Eric,
Just to let you know my iPad2 is still doing thousands of loops trying to grab
3 messages from my test inbox even after removing the account and re-adding it.
I wonder if I got something funky happening on our network but wireshark does
not show anything out of the ordinary.
Roy
On Wed, Apr 11, 2012 at 11:36 AM,<[email protected]> wrote:
Not sure if I'm sending this twice... looks like original reply got mangled.
I think apache mail server spam rules have been updated a few days ago.
I had to change my SMTP-out server, the previous one was considered as
spam and a few of my mails didn't reach out.
So even with compress off my iPad keeps attempting to download the second
message in the test inbox over and over again. But I will remove account and
try from scratch agin and see what happens.
With compress off on beta4, I can read mails from ipad.
With compress on on beta4, I can list mails, but read hangs to finally
make client exit (crash?).
BTW, were you asking me to open the jira ticket and update the client
compatibility page? Happy to do it just not sure if the questions was pointed
to me.
Yes, it would be great if you can do this.
The JIRA is used to follow up this issue (description of the issue with
stacktraces, comments, patches,...).
The compatibility page gives a view on which client is supported at the
moment.
I'm also wondering if you are getting the same errors pasted below as I am.
I'm getting these kind of consistenly from outlook and other clients. Parsing
problems and client disconnects (probably do to the parsing problems). This is
with the build from james-app beta 4 tag project with jpa specified as mailbox.
Parsing errors/warning on some mails can occur (for some malformed
mails), but this should not be the general rule.
The stacktrace you gave in the previous mail is related to SMTP. This
can occurs if the server receives such a malformed mail.
It has nothing to do with the ipad issue.
I have set DEBUG level on IMAP, with compression enabled.
I 'only' see the following stacktrace which confirms that the client
does too many requests, but we still have to find the cause of these
multiple requests. I confirm that with compression disabled, everything
works fine.
java.nio.channels.ClosedChannelException
at
org.jboss.netty.handler.stream.ChunkedWriteHandler.discard(ChunkedWriteHandler.java:171)
at
org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:138)
at
org.apache.james.protocols.lib.netty.ConnectionCountHandler.channelClosed(ConnectionCountHandler.java:39)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.cleanup(FrameDecoder.java:354)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.channelClosed(FrameDecoder.java:238)
at
org.apache.james.protocols.netty.ConnectionPerIpLimitUpstreamHandler.channelClosed(ConnectionPerIpLimitUpstreamHandler.java:101)
at
org.apache.james.protocols.netty.ConnectionLimitUpstreamHandler.channelClosed(ConnectionLimitUpstreamHandler.java:72)
at
org.jboss.netty.handler.timeout.IdleStateAwareChannelHandler.handleUpstream(IdleStateAwareChannelHandler.java:43)
at
org.jboss.netty.handler.timeout.IdleStateHandler.channelClosed(IdleStateHandler.java:262)
at
org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(OneToOneDecoder.java:61)
at org.jboss.netty.channel.Channels.fireChannelClosed(Channels.java:398)
at
org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:596)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:350)
at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:274)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:194)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
We are currently running on Windows 64 bit 2008 r2 with java 1.6.0_26. I am
not seeing these problems with beta 3.
windows and java 1.6 should be fine.
so with beta3, compression works with ipad?
[snip]
On Wed, Apr 11, 2012 at 5:19 AM, Eric Charles<[email protected]> wrote:
Hi Roy,
I have just migrated to beta4 (release), and indeed IMAP with compression
enabled breaks ipad mail client in the way you describe.
It works fine with compression disabled.
Thunderbird works fine with compression enabled and disabled.
Would you mind opening a JIRA [1] for this and update the client
compatibility page [2]?
The question is now: 'how can we further debug'? 'ease of use' seems to be
orthogonal to 'ease of debugging' in the ipad case.
Thx again,
Eric
[1] https://issues.apache.org/jira/browse/IMAP
[2] http://wiki.apache.org/james/Server3ClientCompatibility
On 04/10/2012 04:14 PM, [email protected] wrote:
Hi guys,
So i've been working on my company's own customer mailbox implementation
of James on Version 3 originally started with beta 3. I recently upgraded
our code to work with beta 4 but now I notice that when I enable compression
on the IMAP server my iPad will "break out" of the Mail app to the main
screen. It does not do this with beta 3. (No SSL enabled btw, seem to have
problems with self-signed certs with iPad)
I'm going to see if I can test this with the default implementation of
imap that comes with James but if the problem lies with my implementation of
the mailbox (and other pieces) do any of you have suggestions on how one
goes about troubleshooting or bug hunting this?
Regards,
Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
