> So, all you can do is do a very fast search for known sources > of senders (customers and people) and either copy those > messages to other users or simply assign them to other users > (by assign, I mean do a SQL update on the underlying tables).
I have thought about this, and would like to discuss a good way to implement it. Basically to change ownership of a mailbox. Something like this: # Change the name of the mailbox to avoid conflicts dbmail-mailbox -u oldguy -m INBOX -n INBOX-oldguy # Attach the mailbox to the new user dbmail-mailbox -u oldguy -m INBOX-oldguy -x newguy # Delete the old user and empty out any other mailboxes dbmail-users -de oldguy (BTW, I started working on a dbmail-mailbox utility a few months ago, but wasn't sure where to commit it. At this point, I'll put it into 2.1) > One further thing [though this thread may not be perfect > to ask it, I'll ask anyway :-) ] Is there already a > functionality in DBMail that --whatever the user action-- > *no* mail is actually erased from the mail storage. This is needed for banks, for example. They are required to archive everything. I think that it is better handled by using a domain alias in combination with a local delivery. That isn't possible at the moment because as soon as one delivery method is found, only that one is used. In retrospect, I'm not sure why all three aren't tried. I suppose that in the case of a username that is well formed address, but has an alias that forwards to someplace else, you'd rather not also receive email locally. But I could see a domain alias being used to capture all email for a domain. Perhaps this should become configurable? At least with Postfix, there are options to catch all email and save it. I would recommend using that instead of adding a DBMail config option, unless we really want to. Aaron
