GNOME Bugzilla – Bug 211704
"my imap server sucks" option
Last modified: 2005-08-09 13:46:22 UTC
We might want to make a "my imap server sucks" option in the IMAP provider, to make it fall back to IMAP4-non-rev1-with-no-CAPABILITIES behavior, since there are now 3 broken IMAP server bugs in the db.
I'm all for that. We have a br0ken Novell imap server, and it pains me not being able to use imap + evo :( /Richard
This sucks big time. I'd love to have this implemented. On the br0ken imap-server at work (which they refuse to replace since outlook works with it) I get a hang with evo every once in a while.. This is the last thing I get from evo before it hangs: received: A00227 OK UID FETCH completed sending: A00228 UID FETCH 5076 BODY received: * 2 FETCH (A00228 BAD UID Invalid parameter: [?;? ??? /Richard
well, this option will not fix that imap suckage. That imap suckage is unfixable because it is completely broken according to the spec.
Shouldn't Evo simply be able to close the connection and reconnect? I get stuff like that sometimes as well, and Evo gets completely stuck and has to be killed (both 1.2 and 1.3). I always try to disconnect and reconnect first, but it fails to do that either. Maybe just have a timeout in the disconnect and force the connection down if it takes too long.
huh? and what good would reconnecting do?
i thought we had an environmental variable CAMEL_IMAP_BRAINDAMAGED, but i can't seem to find it ahh it is only in 2.0. i wonder if it should be put in 2.1 as well.
CAMEL_IMAP_BRAINDAMAGED is in 2.2 and 2.4 now, although it forces a different fallback, it avoids the use of partial fetches.
i think you meant to close this then? (haha, comment #1)