X-Status flag, reconstruct and a suggestion
Andrew Morgan
morgan at orst.edu
Sat Oct 4 12:24:03 EDT 2003
On Sat, 4 Oct 2003, Diego Rivera wrote:
> On Sat, 2003-10-04 at 09:37, Rob Siemborski wrote:
> > I think I meant that "if you write it, I'll look at it and strongly
> > consider including it." Not "I'll write that."
>
> Oh ok...my mistake :) I'll get cracking then...
>
> > Unlike the reconstruct patch, which is helpful for migration, I don't
> > think we would ever take something that modified the contents of message
> > files.
>
> I figured as much, but I thought I'd ask anyway :)
>
> How about adding a second text file a-la "34.status" which ONLY contains
> the X-Status flag? If the file exists, reconstruct could leverage it...
>
> My line of thinking is this: if a catastrophe prevents me from using the
> DBs, or the DBs are partially corrupted for a group of users who also
> happen to have a lot of e-mail, the X-Status information lets me restore
> the entirety of the mailbox status info as it was before the failure,
> rather than have all the statuses reset due to the failure.
Where are the status flags currently stored in Cyrus? The cyrus.index
file? The cyrus.cache file? I know the seen information is stored in a
separate file outside the mailbox directory.
In what cases would you lose the status flags of a message?
Andy
More information about the Info-cyrus
mailing list