KMail, and its difficulties with broken network connections

[olembe]

I really like KMail. There, I've said it. It scared me at first, but after just a day or two I came to love it more than any other email programme I've ever used.

However. I run Kubuntu on a laptop, which is frequently being put to sleep and restored as I move from place to place. And KMail really doesn't like this very much. It's pretty much at the stage where after a restore, KMail won't speak to an IMAP server again until the computer has been restarted.

I've just tried quitting KMail, when it was in this state of refusing to talk to the server, and after quitting typed "ps -ef | grep -i mail". It seems KMail has loads of backend processes that don't quit with the main programme, which might explain why quitting it and then restarting it doesn't solve its connection problems:

~$ ps -ef |grep -i mail
ian    8245   1 0 08:15 ?    00:00:26 /usr/bin/kmail -caption KMail
ian    8249 1759 0 08:15 ?    00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-ian/klauncherMT1760.slave-socket local:/tmp/ksocket-ian/kmailNa8245.slave-socket
ian    8260 1759 0 08:15 ?    00:00:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-ian/klauncherMT1760.slave-socket local:/tmp/ksocket-ian/kmailLE8245.slave-socket
ian   10809 1759 0 09:43 ?    00:00:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-ian/klauncherMT1760.slave-socket local:/tmp/ksocket-ian/kmailkC8245.slave-socket

Any thoughts on this? Would killing all these processes be likely to get me to a state where KMail could be launched again successfully? I mean, I shouldn't have to do that, but would it be likely to work until the programme is tightened up a bit? Or would killing those processes be likely to cause problems?