Marc Dirix wrote: > That's nice, but outlook doesn't move them, just deletes them. > > Isn't it possibe to after deleting a folder also only updating status > for those messages whithin the folder? Making it easy to revert > these accidental deletes. (After messages get status 2 they will be > deleted anyway).
Everything *can* be done. Deletion of mailboxes is currently implemented both as a database constraint, but also in the application logic (because of the myisam history). 'IMAP DELETE' on a mailbox triggers an 'SQL DELETE' query on the dbmail_mailboxes table. There is no constraint that triggers deletion of the actual physmessages. Those are (currently) done in the application code (foreach deleted message check if there are more messages linked to the physmessage in question, and if so, etc...). So there is policy both in the database, but also in the application logic. Much of the policy in the application layer could - probably should - be pushed into the database as triggers/rules/procedures whatever. That would give capable DBAs full control over DBMail's storage policies. As to the incident in question: yes we can drop the key constraint between mailboxes and messages, and implement deletion of a mailbox by changing flags. Makes perfect sense to me. Please file a wishlist bug if you don't mind so we can explore the pros and cons. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
