Happens still. Same back trace of the bug - kmail crashes under parseMsg() in parse ID or body(). That bug was makred fixed, but now it happens again, always, in identical conditions, and it crashes in identical way My recent crash: [KCrash Handler] #5 0x00007fade7ff5900 in DwEntity::Headers() const () from /usr/lib/libmimelib.so.4 #6 0x00007fadeeccd4f0 in KMMessage::headerField (this=0x20d3610, aName=..., encodingMode=KMMessage::MessageCharsetEncoding) at ../../kmail/kmmessage.cpp:1990 #7 0x00007fadeecd0e75 in KMMessage::msgId (this=0x20d3610) at ../../kmail/kmmessage.cpp:1888 #8 0x00007fadeedc7db9 in KMReaderWin::parseMsg (this=0xc98680, aMsg=0x20d3610) at ../../kmail/kmreaderwin.cpp:1758 #9 0x00007fadeedb6eda in KMReaderWin::displayMessage (this=0xc98680) at ../../kmail/kmreaderwin.cpp:1605 #10 0x00007fadeedb70b4 in KMReaderWin::updateReaderWin (this=0xc98680) at ../../kmail/kmreaderwin.cpp:1545 #11 0x00007fadeedc2f9d in KMReaderWin::qt_metacall (this=0xc98680, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff0ed3e730) at ./kmreaderwin.moc:168 #12 0x00007faded9fdddc in QMetaObject::activate (sender=0xc98728, from_signal_index=, to_signal_index=, argv=0x1) at kernel/qobject.cpp:3113 #13 0x00007faded9f7d83 in QObject::event (this=0xc98728, e=0x20d3610) at kernel/qobject.cpp:1075 #14 0x00007fadede7befc in QApplicationPrivate::notify_helper (this=0x77c680, receiver=0xc98728, e=0x7fff0ed3ed30) at kernel/qapplication.cpp:4056 #15 0x00007fadede831ce in QApplication::notify (this=0x7fff0ed3f1a0, receiver=0xc98728, e=0x7fff0ed3ed30) at kernel/qapplication.cpp:4021 #16 0x00007fadefc3eab6 in KApplication::notify (this=0x7fff0ed3f1a0, receiver=0xc98728, event=0x7fff0ed3ed30) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x00007faded9e8c2c in QCoreApplication::notifyInternal (this=0x7fff0ed3f1a0, receiver=0xc98728, event=0x7fff0ed3ed30) at kernel/qcoreapplication.cpp:610 #18 0x00007fadeda13862 in QCoreApplication::sendEvent (this=0x77af80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #19 QTimerInfoList::activateTimers (this=0x77af80) at kernel/qeventdispatcher_unix.cpp:572 #20 0x00007fadeda1125d in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #21 0x00007fade4c81bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0x00007fade4c85598 in ?? () from /lib/libglib-2.0.so.0 #23 0x00007fade4c856c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0x00007fadeda111a6 in QEventDispatcherGlib::processEvents (this=0x743930, flags=) at kernel/qeventdispatcher_glib.cpp:327 #25 0x00007fadedf104be in QGuiEventDispatcherGlib::processEvents (this=0x2899d, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x00007faded9e7532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #27 0x00007faded9e7904 in QEventLoop::exec (this=0x7fff0ed3efd0, flags=) at kernel/qeventloop.cpp:201 #28 0x00007faded9e9ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x0000000000402fe9 in main (argc=, argv=) at ../../kmail/main.cpp:146 on ubuntu 9.10 amd64 kmail Version 4.3.2 (KDE 4.3.2) The original bug (duplicates) was first reported in 2006 year. Would be so nice to fix it now in 2010.