[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#45694: acknowledged by developer (kmail fails to update its folder index properly)
From:       Marc Mutz <mutz () kde ! org>
Date:       2002-07-25 17:04:30
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 25 July 2002 03:30, V K wrote:
<snip>
> This is incorrect behaviour. It's dangerous. It's a bug, but feel
> free to close the bug report.
<snip>

Please read what people write. He said it's duplicate.

> Have done so, more than once. It requires me to specifiy all folders,
> 1 by 1, which for >50 folders is at least tedious. Even if I put the
> effort in, kmail forces me to specify a second file, and then, when I
> load one of the folders, SWOOOOOOOOOOOOOSH, the folder is suddenly
> empty and everything is in the second file. Excuse me? Do I specify
> that file as well then? Ad infinitum? The manual may say something
> about this topic but the kmail feature is completely useless. Net
> result is as I said, kmail doesn't do folder locking.

KMail assumes ownership of ~/Mail, at least as long as it is running. 
Point. If KMail doesn't fit your needs, why do you insist on using it? 
Most people that talk like you use another mailer...

> Most of my folders are safe though, as kmail's (also de-facto)
> non-existing ability to access folders in sub-directories (before you
> mention the obvious, yet it's in the manual but it requires at least
> 3 attempts to get working) can only be described as utterly
> braindead. I'd be interested in the rationale behind this though.
<snip>

I'm not sure I'm with you here. Can netscape mail access folders in 
subdirs not ending with .sbd?

Marc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9QC+e3oWD+L2/6DgRAnX8AKCGqAhuo+y9PdFFWpDWhsoWVi2xGQCeJsuE
DqnOvsHMIkuJYWBkAmp+Opk=
=cLt7
-----END PGP SIGNATURE-----



(Complete bug history is available at http://bugs.kde.org/db/45/45694.html)
[prev in list] [next in list] [prev in thread] [next in thread]