[kdepim-users] Seperate 'sets' of mail boxes
Anne Wilson
cannewilson at googlemail.com
Thu Nov 20 09:34:30 GMT 2008
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20081120/c2558064/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users
More information about the kdepim-users
mailing list