GNOME Bugzilla – Bug 242873
Fail to connect POP server and crashed (seg fault)
Last modified: 2003-06-05 21:41:43 UTC
Description of Problem: Today, I installed and use it at the first time on the FreeBSD 5.0-CURRENT, which it has Gnome 2.3.1. However, I ran and filled out my account information and it will never let me login to the POP server. It works great on the different email clients such as Opera 7's M2 and etc. Steps to reproduce the problem: 1. Connect to the POP server and it is taking a quiet while to get it crashed. 2. To crash it more quick, just press the cancel button while it connects to the POP server. 3. Actual Results: It crashed with the seg fault. Expected Results: It crashed with the seg fault. How often does this happen? Always. Additional Information: I ran it under the gdb, so here's backtrace of it: =========================== (gdb) r Starting program: /usr/X11R6/bin/evolution-1.3 (evolution-1.3:70294): GConf-CRITICAL **: file gconf-listeners.c: line 339 (ltable_insert): assertion `gconf_valid_key(where, NULL)' failed (evolution-1.3:70294): camel-WARNING **: Invalid root: '//usr/home/mezz/evolution/local/Drafts/mbox.ibex.index' (evolution-1.3:70294): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution-1.3:70294): camel-WARNING **: block size: 1024 (1024) OK (evolution-1.3:70294): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution-1.3:70294): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution-1.3:70294): camel-WARNING **: flags: unSYNC file:///usr/local/share/xml/catalog:1: error: Start tag expected, '<' not found CATALOG "sdocbook/catalog" warning: failed to load external entity "/usr/home/mezz/evolution/config/storage-set-view-expanded:default" warning: failed to load external entity "/usr/home/mezz/evolution/views/mail/galview.xml" warning: failed to load external entity "/usr/home/mezz/evolution/filters. xml" warning: failed to load external entity "/usr/home/mezz/evolution/filters. xml" (evolution-1.3:70294): camel-pop3-provider-WARNING **: Bad server response: DELE, LIST, LAST, NOOP, RETR, RSET, STAT, TOP, UIDL or QUIT Program received signal SIGBUS, Bus error. g_hash_nodes_destroy (hash_node=0xd0d0d0d0, key_destroy_func=0, value_destroy_func=0) at ghash.c:691 691 ghash.c: No such file or directory. in ghash.c (gdb) bt
+ Trace 36825
no idea, could be anything.
Joe Marcus Clarke (marcus@FreeBSD.org) has help me last night to get the more information. Let me copy and paste in here.. ========================== I see the problem. Your mail server isn't replying with the +OK code. Take a look: Server: +OK mezz7 is welcome here Client: CAPA Server: DELE, LIST, LAST, NOOP, RETR, RSET, STAT, TOP, UIDL or QUIT Now, look at mine (which works): Server: +OK Mailbox open, 1978 messages Client: CAPA Server: +OK Capability list follows: TOP LOGIN-DELAY 180 UIDL USER SASL LOGIN Evo is expecting the POP result code of either +OK or -ERR. When it doesn't see that, it dies. Granted, it should be more graceful about it, but the mail server is in violation of the POP3 RFC (good luck getting your ISP to fix it). Joe ========================== I believe, Evolution still needs to fix this, because I already tested on Mozilla mail, Opera mail, balsa and other mail clients and they all have no problem. I am happy to do anything if you need the more information. I can attach the tcpdump output if you need it.
it doesn't crash for me or anyone else with similar broken POP servers. Also, the reason those other mail clients work with your broken POP server is because they don't send a CAPA command - of course, since they don't send a CAPA command, they cannot take advantage of the security (and other) POP extensions that the POP server may implement. We *do* take advantage of those, so we MUST continue to send CAPA. You can of course modify your sources to not send a CAPA so it works for you...
*** bug 243904 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 240788 ***
btw, failed to mention this last time but the good news is that the crash has been found/fixed. (it was random memory corruption elsewhere (not in the pop code) which often triggered when popping mail).
Thanks for found and fix the crash problem. However, I won't be able to test it any longer because I am not going to install this product anymore. Sorry about that, it's when all the other mail clients that will work with my ISP's broke POP server with plenty of features that are function fine. Contract and bug my ISP to get the POP server fix isn't that simple. Let's close it.