Thank you Mark for trying to help me.
When .mixstatus and .mixmeta files are missing, each mail file .mix{nnnnnnn} is
handled by imapd server wrongly as a separate mail-subfolder. At least it is so
offered to imap clients.
When I created empty .mixstatus file by Your advice, I get following error in
imap client:
Error in mix metadata file sequence record
Configuration:
Account: xxxxx
Server: mailserver.ourdomain
User name: yyyyyy
Protocol: IMAP
Port: 143
Secure(SSL): 0
Code: 800cccd2
Mail files looks correct, mixrbld complains at only one file with "Data file
Resurrected/.mix1114115 UID ran backwards (29a4 < 2ab5)", the rest is processed
without errors and .mixindex-rebuild is created successfully.
Looking forward to Your next advice.
Regards.
David
>---------------------------------------------------------
>Od: Mark Crispin
>Přijato: 5.10.2007 17:03:45
>Předmět: Re: [Imap-uw] How to recteate meta and status files of mailbox
>
>On Fri, 5 Oct 2007, [EMAIL PROTECTED] wrote:
>
>> I would like to ask you how can I recreate .mixmeta and .mixstatus files
>
>> of MIX mailbox. I happen to rebuild .mixindex with mixrbld tool but
>
>> messages are still inaccessible through imapd.
>
>
>
>The easiest rebuild of the .mixstatus file is to delete it and recreate it
>
>as an empty file.
>
>
>
>This is the first that I have ever heard of a .mixmeta file needing a
>
>rebuild.
>
>
>
>However, I am concerned by your message. If "messages are inaccessible
>
>through imapd", rebuilding the .mixstatus and/or .mixmeta files is
>
>probably NOT the appropriate step; and rebuilding .mixindex may not be the
>
>appropriate step either.
>
>
>
>It seems to me that you have a problem, and that you are guessing at the
>
>solution, and try ingdifferent things until you find something that works.
>
>That will invariably cause more harm than good.
>
>
>
>mixrbld happily runs and creates a new .mixindex, even if there was
>
>nothing wrong with the old one. In the course of doing so, it can
>
>"unexpunge" previously expunged messages. If there is some corruption
>
>issue in the data files (unlikely but possible) mixrbld may actually end
>
>up with an index file that is worse (phantom or corrupt messages) than
>
>before.
>
>
>
>Deleting .mixstatus and creating a new one tosses out all the mailbox
>
>flags.
>
>
>
>Any rebuild of .mixmeta would probably entail resetting the UID regime
>
>and/or losing message keywords.
>
>
>
>None of these are things that you want to do unless there is a good
>
>reason, which is that the file in question is corrupt and must be
>
>replaced. Just about the only "safe" thing to do is to remove the
>
>.mixsortcache file; the only cost there is the CPU cost of re-collecting
>
>that data from the messages the next time the mailbox is sorted or
>
>threaded.
>
>
>
>Rather than attack the problem randomly, you need (from the onset) to
>
>identify the problem and its cause. Unfortunately, "inaccessible through
>
>imapd" is too vague a statement for much diagnosis.
>
>
>
>What error message(s) do you receive when you try to access that mailbox?
>
>[Exact text of the error message, please]
>
>
>
>What is the observed behavior? Not "it doesn't work", or "messages are
>
>inaccessible". Rather, something like "when I open the mailbox, I get a
>
>'error 69: frotz mark in flob blarg' error message and the program exits",
>
>or "when I open the mailbox, I only see 2 messages when I know there are
>
>10,000 messages in that mailbox."
>
>
>
>-- Mark --
>
>
>
>http://panda.com/mrc
>
>Democracy is two wolves and a sheep deciding what to eat for lunch.
>
>Liberty is a well-armed sheep contesting the vote.
>
>
>
>
>
>
>
>
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
