Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft Exchange Server 2003 IMAP - login stream error #45

Closed
jkolczasty opened this issue Oct 11, 2012 · 2 comments
Closed

Microsoft Exchange Server 2003 IMAP - login stream error #45

jkolczasty opened this issue Oct 11, 2012 · 2 comments

Comments

@jkolczasty
Copy link

Microsoft Exchange 2003 IMAP is not RFC strict, which makes libetpan useless with it. E.g. log from Claws-Mail with libetpan16 1.1:

[12:41:05] * message: Account 'xxxxxxxxxxxx': Connecting to IMAP4 server:
10.0.1.15...
[12:41:05] IMAP4< * OK Microsoft Exchange Server 2003 IMAP4rev1 server version
6.5.7638.1 (xxxxxxxxxxxx) ready.
[12:41:05] * message: IMAP connection is un-authenticated
[12:41:09] IMAP4> 1 CAPABILITY
[12:41:09] IMAP4< * CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS
MAILBOX-REFERRALS NAMESPACE LITERAL+ UIDPLUS CHILDREN
[12:41:09] IMAP4< 1 OK CAPABILITY completed.
[12:41:09] IMAP4> Logging xxxxxxxxxxxx to 10.0.1.15 using LOGIN
[12:41:09] IMAP4< CAPABILITY completed.
[12:41:09] ** warning: IMAP error on 10.0.1.15: stream error
[12:41:09] ** warning: IMAP4 connection broken
[12:41:09] IMAP4< Error logging in to 10.0.1.15

Exchange responses with extra invalid line after "1 OK":
[12:41:09] IMAP4< 1 OK CAPABILITY completed.
[12:41:09] IMAP4< CAPABILITY completed.

Is it possible to write some workarounds for Exchange sh*t^W IMAP?

@dinhvh
Copy link
Owner

dinhvh commented Oct 11, 2012

Could you try not to use CAPABILITY command when you detect an Exchange server?

@jkolczasty
Copy link
Author

I'm just a user of Claws-Mail and there is no way to disable it in that MUA.

Bug on claws-mail (closed as wontfix):
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2750

I could write some test code, but not in the near future, ENOTIME. Sorry.

@dinhvh dinhvh closed this as completed Feb 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants