Forrest Aldrich wrote:
Hi Rudy,
I did this. And it didn't really work.
What I ended up figuring out, is that the root directory of
user/forrie/Mail did NOT have cyrus.* files, though the subdirectories
did. So, via my IMAP client, I created that directory... then went and
did a reconstruct -r
Forrest Aldrich wrote:
Hours after my crash, I am figuring a few things out. One of the
problems has to do with permissions on sasl2.db.
Right now, I have run "reconstruct -r" and it caught all but one
subdirectory in my restored archive. This other directory has
cyrus.index files, etc. an
On Fri, 2004-04-16 at 22:20, John Conant wrote:
> Hi,
>
> Sort of a side note - we started having trouble like that. Turned
> out that our overnight antivirus scan of the mail store would find a virus,
> and quarantine (move!) the infected file, thus messing up the Cyrus
> indexing.
On Fri, 2004-04-16 at 22:58, Craig Ringer wrote:
A message in which he failed to actually attach the file he was talking
about. It's attached this time, as text/plain so that overzealous mail
scanners don't remove it.
Craig Ringer
#!/bin/bash
#
# /var/tmp/scan/clamout is a file containg the outp
Hi,
Sort of a
side note - we started having trouble like that. Turned out that
our overnight antivirus scan of the mail store would find a virus, and
quarantine (move!) the infected file, thus messing up the Cyrus
indexing. Now we schedule a system-wide reconstruct after the virus
scan,
Thanks, but I must have a different version or something, here's what i get when
i run that.
localhost.localdomain> reconstruct -r -f user.chris
usage: reconstruct [-r] mailbox
so that second line is telling me that my usage is incorrect. I cannot use the
-f or the -m flag, and even though -r doe
