Re: Seperate 'sets' of mail boxes

On Wednesday 19 November 2008 21:36:24 Ingo Klöcker wrote:
> > > The trouble with mbox is that every time a message changes status
> > > or is deleted, the whole file has to be read in, compacted if
> > > something has been deleted, then written back to disk.  With large
> > > mailboxes the delay is noticeable.
> >
> > That is not how Pegasus does it, it is very quick.
>
> And it is not how KMail does it. It is also very quick. Status changes
> are only written to the index file. Deleting a message also just
> changes its status leaving the deleted message in the mbox file. To
> prevent the mbox file from growing too large, KMail compacts the mbox
> files from time to time in the background. This compaction is claimed
> to have a noticeable impact on very slow computers.

My apologies for misrepresentation, then :-)  I was remembering, mis-
remembering, it seems - what I had read a very long time ago.

Anne

_______________________________________________
KDE PIM users mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-users

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

iEYEABECAAYFAkklLycACgkQbMErw/n0TZqn2ACeOBENdppZLOEHuvKr+FZkq2eR
zKIAn2XWgg7TwhzhvujatkX3A6+Ifb2Q
=G49x
-----END PGP SIGNATURE-----