JSL>> A long time ago there was a thread on the dangers of leaving messages
JSL>> in the inbox. Unfortunately I no longer remember exactly what the
JSL>> danger was. I searched the archives for the subject line above but
JSL>> found nothing explaining the problem. Does anybody remember?
RO> Basically it comes to this.
RO> The Inbox is a high traffic folder: every message that enters your
RO> message base first arrives in the Inbox, moving and deleting
RO> (automatically and manually) means another mutation of your Inbox.
RO> Due to these multiple mutations it's easy for things to go awry.
RO> There's your first reason not to use the Inbox for permanent storage.
RO> When your Inbox is large it's more difficult to mutate it then when
RO> it's small, so using the Inbox for permanent storage makes it more
RO> likely for things to go awry.
RO> Of course executing compress and purge daily minimises the chance that
RO> things go bad.
RO> I've never had a corrupt Inbox, so I've never been bitten, but in the
RO> past the issue came up regularly. But why use a mail client with an
RO> extensive filtering engine like TB when you store everything in the
RO> Inbox.
I totally agree with every word Roelof wrote. My addition: the only way I
saw corrupted Inboxes (I am a TB distributor) that people used the
Compress at exit. When I send the registration keys to users, this is
the information (in brief) I send them in the text of the mail before
the actual reg. code:
- switch off the Compress at exit forj all Inboxes, this is how you can
do it
- make manual compress of Inboxes at every two weeks, a month, based
on your email load
(I compress my folders every Sunday)
Vili
--
Macasoft Bt.
www.thebat.hu
www.macasoft.hu
_, )\__/( ,_
/'.;`-.`{..}',-';.`\
/'.'; `-,`-""-',-' ;`.`\
\/\/^\---.\;;/.---/^\/\/
________________________________________________
Current version is 4.1.7 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
