- This topic has 3 replies, 1 voice, and was last updated 18 years, 8 months ago by
.
-
Posts
-
hello..
wish i’d found this place sooner :\
small office (12 people), all macs:
here’s what happened.. our mail server stopped accepting inbound mail on friday afternoon.
the log was showing:
DBERROR: opening /var/imap/deliver.db: cannot allocate memory
DBERROR: opening /var/imap/deliver.db: cyrusdb error
FATAL: lmtpd: unable to init duplicate delivery databaseI did the following:
stopped mail server..
mv /var/imap /var/imap.old
mkdir /var/imap
/usr/bin/cyrus/tools/mkimap
chown -R cyrus:mail /var/imap
sudo -s -u cyrus /usr/bin/cyrus/bin/reconstructfired up the mail server and when i connected in Apple Mail, my inbox was empty. I’m receiving mail fine, but my previous email isn’t there. Same for my other users. Just new stuff. I have 2 questions:
1. is all of our old mail in the “imap.old” directory on the server? Is it at least safe?
2. If so, how to i add it back to what i’ve already received in apple mail the last couple days?
i remember having to do the above commands once before (3 years ago). I had printed them out at the time. But the last time i did this all of my old mail came back (all stamped at 12 noon, but it was there at least). I thought the reconstruct would bring back the old mail? In digging around different sites tonight, i see some solutions vary slightly, like “reconstruct -i”.. or not using the “-s” flag.
anything you can do to reassure that i haven’t lost 2 years worth of mail for everyone in the office.. would be helpful. 😐
thank you!
brian
MacTroll wrote:
Your specific e-mail files are actually in /var/spool/imap/user
Do you still have the old and new mail there?
thank you for replying so quickly.. i thought all the mail was in /var/imap, and when i didn’t see anything resembling old mail in ‘imap.old’ i started feeling a tad sick.
i ssh’d in and looked inside /var/spool/imap/user.. yes, i see old email in there, subfolders from last month, etc. But, i did the reconstruct on saturday afternoon, and we’ve been getting ‘new’ mail for the last 36 hours. Is the new mail going into the same /var/spool/imap/user? And the old mail is there too, even though i can’t see it in Apple Mail? ^-^
i see other files in the user folders for cyrus.cache, cyrus.header and cyrus.index. My god, if you tell me all i have to do is something like delete those and let them rebuild.. and we’ll get our old mail AND get to keep the new mail too.. i’ll owe you my life (or at least my job).
MacTroll wrote:
Although it sounds like you know what the next steps are.
i may have an idea about what to do, but the reality is that i’m a Filemaker DBA who happens to run a mailserver. 🙂 Normally, i would enjoy experimenting with solutions (that’s how i learn), but I’m not really comfortable doing that in this case. This issue is somewhat over my head, and there’s too much at stake to go with my gut.
If i could just clarify, for my own understanding:
1. That the new email (from the last couple days) is in the same ‘store’ as the old mail
2. If i need to delete all 3 cyrus files in each user’s mailbox.. if not, which ones?
3. Do i stop mail services before deleting said cyrus files?
4. What causes these files to be recreated? Do they rebuild when mail services are restarted on the server, do i need to delete and initialize each mail account on the workstations? Etc..
5. That we don’t have to sacrifice the last 2 day’s email to bring back the old stuff.
Thank you so much… and for the mailbfr info. We don’t have it, but i’ll certainly get it installed.
Brian
after much fiddling.. i fixed it with:
sudo -u cyrus /usr/bin/cyrus/bin/reconstruct -r -f user/(user)
there were 2 things wrong with what i was finding on a number of websites. First, it’s user/(user), not user.(user).. at least on our server. That, and the documentation i was turning up was misleading on usage for the -f option. Once i got those 2 things clarified, everything worked fine.
and i’ll be enlisting the mailbfr script/app to save the headache next time.
thanks again
- You must be logged in to reply to this topic.