Bug 16019 – Evolution crashes while accessing IMAP server via SSL

• Product: Gentoo Linux
• Status: RESOLVED WORKSFORME

[Description Steve Juranich 2003-02-19 13:02:28 UTC]

I just emerged evolution this morning.  There is an "ssl" line in my
/etc/make.profile/use.defaults.  I set up an IMAP account that uses SSL (I know
this is correct).  I have the "Use SSL Always" flag set on the account setup
page, but I keep getting errors that evolution can't access the server on port
143.  This makes sense since the server is running on port 993.  What doesn't
make sense is why evolution is even trying port 143.

Sometimes evolution is able to deal with this elegantly (just giving an error
message and proceeding).  Other times it crashes ( get a crash dialog, but
everything is stripped out, so there's no stack dump or anything useful.

Another thing that might be important, I'm running fluxbox with no other GNOME
applications running.  I don't know if this would affect anything.  Mozilla-mail
is able to read my mail okay, but it has its own issues that makes me want to
try other mailers.

Reproducible: Always
Steps to Reproduce:
1. Set up an IMAP account that uses the SSL protocol.
2. Click on evolution's "Inbox" icon.
3. Wait.  And wait.

Actual Results:  
Somtimes an error message, sometimes a crash dialog box.  Either way, I can't
get my email.

Expected Results:  
Connected to my email server and shown me my messages.

I'm BRAND NEW to gentoo (just installed on Monday), so if I've left anything
out, please let me know.  I'm happy to help in any way I can.  Here's my "emerge
info evolution" output:

coffee (~)
% emerge info evolution
Portage 2.0.46-r12 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r2)
=================================================================
System uname: 2.4.19-gentoo-r10 i686 AMD Athlon(tm) Processor
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Lin
ux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share
/config /usr/X11R6/lib/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY="/usr/local/portage"
USE="x86 oss 3dnow apm arts avi crypt cups encode gif jpeg kde libg++ mikmod mmx
 mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib gtk
html gdbm berkdb slang readline tetex bonobo svga java guile X sdl gpm tcpd pam 
libwww ssl perl python esd imlib oggvorbis gnome gtk qt motif opengl mozilla"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O3 -pipe"
CXXFLAGS="-march=athlon-xp -O3 -pipe"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

[Comment 1 Alastair Tse (RETIRED) 2003-02-19 13:49:36 UTC]

What version of evolution and mozilla are you using? Evolution uses mozilla's libs for SSL/TLS access.

You need to add "-g" to your CFLAGS for any meaningful stacktrace. I've encountered evolution using the wrong port before, but that was on a RedHat box. Have you tried forcing it to use 993 by changing the mail server to mailserver.com:993 ?

[Comment 2 Steve Juranich 2003-02-19 14:41:00 UTC]

I'm using Mozilla 1.2.1.  Evolution 1.2.1.

When I force the program to use 993 (via the :993 statement), rather than a crash or error dialog, it just hangs.

I typically don't compile with -g, in the interest of keeping my binaries small.

It took about an hour and a half to build Mozilla on my machine, so if I can avoid doing that again, I'd be happy.

Thanks for the help.

[Comment 3 Alastair Tse (RETIRED) 2003-02-21 15:27:14 UTC]

are you using an old ~/evolution directory from the 1.0.x series?

nevertheless, try moving it aside and set up the account again and see if it 
still hangs/crashes. i can connect to 3 different IMAP SSL servers without any problems.

[Comment 4 Alastair Tse (RETIRED) 2003-02-24 15:16:46 UTC]

the symptoms look alot like this bug

http://bugs.ximian.com/show_bug.cgi?id=35674

but this doesn't mention it crashing .. at least it explains why it attempts to try 143.

[Comment 5 Alastair Tse (RETIRED) 2003-03-19 08:19:54 UTC]

can't do much without anymore additional info. reopen if you have more information, but it works fine for me.

[Comment 6 Alastair Tse (RETIRED) 2003-09-28 14:09:09 UTC]

reclosing