Gene Heskett wrote: > I don't see a thing there that kmail should get a tummy ache over. That > script has been running daily for close to 20 years now. If fetchmail is > running, incoming mail is handled automaticly by sending kmail a check > mail message over the dcop or dbus message bus. All kmail has to do is > retrieve anything procmail has put in /var/spool/mail/* and sort it to > the correct folder. Since kmail is single-threaded, thats maybe a 200 ms > freeze of the composer while it's doing that. The only independent > thread seems to be the parent thread doing the indexing as killing it > kills the other kmail instances seen by htop. 5 total, but the other 4 > never record any cpu time. > > Computers should save you work, not make it, so I write scripts to > automate it. > > Thank you deloptes. > > Cheers, Gene Heskett I don't know Gene. I am not sure it is single threaded - I use kontact - and I am not sure it is good idea to let it run on /var/spool/mail/*. I have stopped using this +10y ago. I do not remember why anymore. I have an IMAP - locally and on the ISP end. I am afraid your issue is too specific that someone can reproduce and debug it. IF I were you, I would try to narrow down the problem - for example decouple the chain in your process and see where it goes crazy. What I remember from the past is that I found out, that the IMAP Maildir should not be the KMail Maildir - but forgive me I was naive and unexperienced back then. regards --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
