that is what I mean by 're-assigning' mailboxes: when you delete a
user, his/her
mailboxes are re-assigned to a __archive__ system user, or maybe
even __public__
with restricted ACLs.
Right. I thought you meant reassigning to the deleted user, and then
delete everything.
Erik Osterman wrote:
This was a good suggestion, but after some research/attempts, I am not
able to get the triggers working in MySQL to accomplish it. It all boils
down to this error:
Can't update table 'dbmail_mailboxes' in stored function/trigger
because it is already used by statement
Paul J Stevens wrote:
Hrm... Well, since the first solution was satisfied without modifying
any code, I'll probably just use a trigger to insert the deleted folders
into a separate table.
That might work if you break the constraint on the messages table against the
mailboxes table. But
First, thanks for taking an interest in this discussion. It wasn't my
intention to shape a whole new feature, if it hadn't been proposed
before. That said, I'd be delighted if it were to make its way into the
mainline.
Paul J Stevens wrote:
- make sure mailboxes are re-assigned when a user
Marc Dirix wrote:
- make sure mailboxes are re-assigned when a user is deleted (trigger)
Doesn't this (at a higher level) sound a bit as the same mistake with
deleting mailboxes versus messages?
If we start using archive to be able to restore accidental mailboxes,
at some point there
- make sure mailboxes are re-assigned when a user is deleted (trigger)
Doesn't this (at a higher level) sound a bit as the same mistake with
deleting mailboxes versus messages?
If we start using archive to be able to restore accidental mailboxes,
at some point there will also be someone
Erik Osterman wrote:
First, thanks for taking an interest in this discussion. It wasn't my
intention to shape a whole new feature, if it hadn't been proposed
before. That said, I'd be delighted if it were to make its way into
the mainline.
Paul J Stevens wrote:
- make sure mailboxes are
Erik Osterman wrote:
Hrm... Well, since the first solution was satisfied without modifying
any code, I'll probably just use a trigger to insert the deleted folders
into a separate table.
That might work if you break the constraint on the messages table against the
mailboxes table. But you
Paul J Stevens wrote:
message deletion can be dealt with by *not* running 'dbmail-util -py'. In that
case message status will be kept at 2, being invisible to the daemons, but still
there in the database.
Yes, this exactly what I want. Would be the process of restoring the
emails?
Paul J Stevens wrote:
message deletion can be dealt with by *not* running 'dbmail-util -py'. In that
case message status will be kept at 2, being invisible to the daemons, but still
there in the database.
To restore an email, is it as simple as setting the status back to 1 and
setting the
To restore an email, is it as simple as setting the status back to 1 and
setting the deleted_flag to 0?
Yes
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Hi,
I'm looking for a way to keep all email ever received whether deleted or
not. As it stands, I don't see that this is possible with dbmail. The
reason is two fold: users frequently delete messages that need to be
restored; we're legally required to maintain a copy of all email.
Storing a
On Mon, Jan 14, 2008 at 05:50:34AM -0800, Erik Osterman wrote:
Hi,
I'm looking for a way to keep all email ever received whether deleted or
not. As it stands, I don't see that this is possible with dbmail. The
reason is two fold: users frequently delete messages that need to be
restored;
It's a valid point and mail will be warehoused on a certain interval.
But we'd like to keep relatively recently deleted mail online.
Restoration is trivial then, since it's just setting the deleted_at
timestamp col back to null for a particular daterange.
Erik
Marc Dirix wrote:
On Mon, Jan
Erik Osterman wrote:
It's a valid point and mail will be warehoused on a certain interval.
But we'd like to keep relatively recently deleted mail online.
Restoration is trivial then, since it's just setting the deleted_at
timestamp col back to null for a particular daterange.
Aren't you
Erik Osterman wrote:
Hi,
I'm looking for a way to keep all email ever received whether deleted or
not. As it stands, I don't see that this is possible with dbmail. The
reason is two fold: users frequently delete messages that need to be
restored; we're legally required to maintain a copy of
16 matches
Mail list logo
