After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 211704 - "my imap server sucks" option
"my imap server sucks" option
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-10-04 19:31 UTC by Dan Winship
Modified: 2005-08-09 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Winship 2001-10-04 19:31:19 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.
Comment 1 Richard Torkar 2002-09-03 12:52:46 UTC
I'm all for that.

We have a br0ken Novell imap server, and it pains me not being able to
use imap + evo :(

/Richard
Comment 2 ds98rito 2002-09-03 16:19:56 UTC
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
Comment 3 Jeffrey Stedfast 2002-09-03 17:23:18 UTC
well, this option will not fix that imap suckage. That imap suckage is
unfixable because it is completely broken according to the spec.
Comment 4 Osma Ahvenlampi 2003-05-06 12:30:45 UTC
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.
Comment 5 Jeffrey Stedfast 2003-05-06 17:13:04 UTC
huh? and what good would reconnecting do?
Comment 6 Not Zed 2005-02-22 06:36:41 UTC
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.
Comment 7 Not Zed 2005-08-09 05:26:07 UTC
CAMEL_IMAP_BRAINDAMAGED is in 2.2 and 2.4 now, although it forces a different
fallback, it avoids the use of partial fetches.

Comment 8 Dan Winship 2005-08-09 13:34:26 UTC
i think you meant to close this then?

(haha, comment #1)