Opened 14 years ago

Closed 13 years ago

#53 closed bug (fixed)

POP3 SSL addon crashes mail_daemon when connection fails

Reported by: genki@… Owned by: nathanw@…
Priority: normal Milestone: R1
Component: Applications Version:
Keywords: Cc: diver
Blocked By: Blocking:
Has a Patch: no Platform: All

Description (last modified by darkwyrm)


This crash happens when the mail_daemon tries to look for new e-mail but the machine is not connected to the network. My ISP wasn't working at the time. (I got no IP from the DHCP).

It seems only POP3 with SSL crashes, the other accounts on standard POP3 seems fine. On those accounts I just get an error message (which is good and correct); "Error while connecting blah blah"

I'm pretty sure this can be reproduced by disconnecting your network cable, or switching off your DSL modem(or similar).

Here is a stack dump:

loading symbols segment violation occurred SSL_pending: SSL_pending: +0017 ec7fb2ab: * 08508b movl 0x00000008(%eax), %edx XXXX@…:sc

frame retaddr

fd1e4534 ea5d360b POP3Protocol::~POP3Protocol(void) + 0000002f fd1e4564 ec768364 BMailChainRunner::MessageReceived(BMessage *) + 000000e0 fd1e4a44 ec19a9c0 BLooper::DispatchMessage(BMessage *, BHandler *) + 0000007c fd1e4a5c ec198a39 BLooper::task_looper(void) + 0000043d fd1e4d28 ec19ae46 BLooper::_task0_(void *) + 00000036 fd1e4d3c ec06c50d thread_start + 00000039 XXXXX@…:

Another one again:

loading symbols segment violation occurred SSL_shutdown: SSL_shutdown: +0015 ec7fc08d: * 00207e83 cmpl $0x00, 0x00000020(%esi) XXXXX@…:sc

frame retaddr

fd1a7564 ec768364 BMailChainRunner::MessageReceived(BMessage *) + 000000e0 fd1a7a44 ec19a9c0 BLooper::DispatchMessage(BMessage *, BHandler *) + 0000007c fd1a7a5c ec198a39 BLooper::task_looper(void) + 0000043d fd1a7d28 ec19ae46 BLooper::_task0_(void *) + 00000036 fd1a7d3c ec06c50d thread_start + 00000039 XXXX@…:

Change History (3)

comment:1 by korli, 14 years ago

Owner: changed from axeld to nathanw@…

comment:2 by diver, 14 years ago

Cc: diver added

comment:3 by darkwyrm, 13 years ago

Description: modified (diff)
Resolution: fixed
Status: newclosed

This bug was fixed in hrev19557 and 19558.

Note: See TracTickets for help on using tickets.