Re: Delayed expunge / undeleting messages

From: Wesley Craig (no email)
Date: Thu Jan 18 2007 - 13:28:30 EST

  • Next message: Wesley Craig: "Re: Replication and failover"

    A bunch of people already pointed out unexpunge, so I'll point out
    that the delayed expunge / unexpunge functionality doesn't help if
    the user deletes a whole folder. See:

            https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2871

    for the problem report and a patch for a proposed solution.

    :wes

    On 18 Jan 2007, at 02:34, Janne Peltonen wrote:
    > The purpose of the delayed expunge mode appears to be to reduce the
    > amount of disk I/O during expunge and add responsiveness to the
    > client.
    > But I've been thinking... I've got lots of users that accidentally
    > delete important messages, and sometimes even ask us immediately after
    > deleting (and expunging) those messages if they could be recovered.
    > Now
    > if the message was alive last night when we backed the system up, it
    > could be recovered. But if the message was new, it couldn't.
    >
    > But if there is a delay in expunging the message, the file containing
    > the mesage might just lie around in the mail spool, and could be
    > identified reasonably easily. Is there a way to add the message back
    > to the index? A quick hack would probably be something like copying
    > the
    > message file to N., where N is an unused message number, and
    > reconstructing the mailbox. But is there another way? I always feel
    > uncomfortable writing stuff to the mailspool bypassing Cyrus.

    ----
    Cyrus Home Page: http://cyrusimap.web.cmu.edu/
    Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
    List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
    

  • Next message: Wesley Craig: "Re: Replication and failover"





    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs



    Powered By FreeBSD   Powered By FreeBSD