Hi,
This might be a really specific one; looking for guidelines on doing the
right thing with the API c-client offers.
Here's the setup:
o Server: Exchange 2007, with IMAP ports enabled
o Client #1: simplistic client implementation using c-client (I'll
give you a better idea in later)
It would probably be more useful if you set OP_DEBUG in your mail_open()
calls and collect the mm_dlog() events; this will show a protocol
telemetry of what the server is actually doing.
With that in mind, I agree that this seems to be bad behavior on the part
of the server and your surmises a
How did you do this? Did you change IMAPSSLPORT in imap4r1.c from 993
to 994 (the most straightforward way)? Or did you use some other
means? If so, what?
We didn't change IMAPSSLPORT. We're running Solaris 10 and controlling
this through inetd:
[EMAIL PROTECTED]> svcs -a | grep imap
online
On Thu, 1 May 2008, Ken Keating wrote:
How did you do this? Did you change IMAPSSLPORT in imap4r1.c from 993
to 994 (the most straightforward way)? Or did you use some other
means? If so, what?
We didn't change IMAPSSLPORT. We're running Solaris 10 and controlling
this through inetd:
Hmm.
Here is the slightly compressed log; edited private info out.
It's still long though, sorry everyone...
mail_open
===
2008-05-01 15:41:58,718 Mail - Login -
Mailbox/Server[{:993/ssl/novalidate-cert}INBOX],
username[path], OpenOptions[1]
2008-05-01 15:41:58,796 Mail - [IMAP]
A couple of notes:
There is no reason to believe that a STATUS command in any way reflects
what is going on with the selected mailbox stream, even if the mailboxes
are the same. So, although interesting, the STATUS results are actually
inconclusive.
Next:
My first hunch looking at the 2nd
