From kmail-devel Wed Jul 25 06:53:40 2001 From: Holger Schurig Date: Wed, 25 Jul 2001 06:53:40 +0000 To: kmail-devel Subject: Re: Bug#29633: filter has some problem with modified directory X-MARC-Message: https://marc.info/?l=kmail-devel&m=99604621417660 > The idea is to attempt to prevent mail loss when exceptional > events that KMail was not designed to handle occur. > > In order to prevent mail loss when an external application > (like procmail) modifies folder files in ~/Mail I want to > check for an out of date index file everywhere that the > index file is updated which is in three places. This is all nice and well. But it is extremely annoying that KMail just terminates and that one can not see any reason for this. I doubt that many users open a konsole, issue an "ulimit -c 0" command and start KMail by hand, just to see that it wasn't a core dump actually ... As far as I understand it, this happens in the filter code. So, if you think that accessing a mail folder is unsafe, then just don't filter the message, leave it in it's current place. Put a messagebox on the screen that states the problem and that has a "Do not show up again" checkbox. I understand that this cannot be done now because of feature freeze. So the better approach would be to just uncomment this code. After all, you made a working configuration (/home via NFS, no procmail-filtering, KMail get's it's mail via POP3 and filters it itself) unworkable. When KMail+NFS+Procmail has a problem together, then the software that is broken should be fixed. Am I right that KMail was not broken ?!? Greetings, Holger PS: I hope my words are not too strong. I don't want to attack you or make you uncomfortable. :-) _______________________________________________ Kmail Developers mailing list Kmail@master.kde.org http://master.kde.org/mailman/listinfo/kmail