Hello all,
We've recently had a rash of folks using Treo 650 phones with
SnapperMail 2.3.2 installed to read their email via secure IMAP. We're
currently running Imap 2004c and there appears to be a strange problem
in the initial authorization phase. On the phone side, SnapperMail goes
through some initial steps such as Authenticating, Securing and then it
gets to Authorizing. At this step, it will hang for a few minutes or
more and then eventually continue on successfully. While it works, our
users are wondering if there is any fix to the long wait on initial
connect. In looking at the mail server side of things as well as
network traffic, an imapd process is forked off from inetd and is
sitting on a door_call system call. The last packet sent to the phone's
network is from our mail server. Then there is no traffic whatsoever
for those few minutes. After a few minutes, communication between the
two resumes with the mail server sending the first packet after the
delay and then things seem to function normally and users can
send/receive mail. But we're at a loss of what is going on during the
Authorizing phase and in addition, we've done some tests against Courier
and Cyrus IMAP servers and they don't seem to have the same delay during
this part of the handshaking.
On the SnapperMail side, we have it configured to use Secure IMAP on
port 993 with Always Trust Server selected. As mentioned, it does seem
to work ok except for this initial long delay. So, I am wondering if I
might get lucky and have someone else out there who has used SnapperMail
with UW IMAPD and has either not had problems or have had similar
problems. And if you did have problems were you able to solve them?
thanks much,
--Thomas Lohman - [EMAIL PROTECTED]
Senior Systems/Software Developer
Microsystems Technology Laboratories - MIT
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
