>Personally I'd like to see an option for a "Never delete anything >ever" policy. Anything deleted, say in a user's personal email box, >is merely MARKED deleted in the backend. Administrators can still get >at it. And maybe the user can pull it out of a "Recycle Bin" or >something. Interestingly, the current server doesn't actually delete a message at the time the user asks for that operation; the message is actually moved to a hidden room. We defer the disk operation for performance reasons, not for administrative reasons, though.
>Corporate nazi's would love it. Many companies seem to have policies >where they keep all emails for a period of x months or years or >whatever. This is a service better performed by an external program. I'm not really fond of the idea of a message store growing bigger and bigger forever. I don't know what the practical upper limit is for Berkeley DB, but I've got some folks at work who never empty their Trash and never delete anything from the Sent Items folder. A few months ago, we had a customer pay for me to add a Journaling feature to the Citadel server. Every message that passes through the system (even if it didn't arrive via SMTP) is duplicated and sent out to a destination of the system administrator's choice. This was done so that they could use the SECCAS [ http://www.seccas.com/ ] archiving service in order to comply with Sarbanes/Oxley.
