fredag 13 mars 2009 10:00:18 skrev Mark Crispin:
.
> The only reason to run mixrbld/mixdfix is if the mix driver reports errors
> and refuses to open the mailbox. You probably ran mixrbld/mixdfix
> unnecessarily, and that caused your problems.
Ok. Didn't see any warnings on them creating problems. Thought it was more
like fsck. Just rebuilding the metadata from the raw messages.
> However, since you paraphrased the message, this is only a guess. Please
> do not paraphrase messages. It wastes time.
My memory isn't good enough to remember the exact wording of a message 3-4
months ago....
> I don't know how you came to that conclusion, but it is almost certainly
> incorrect.
Hmm...
> If the mailbox opens, it is not corrupt in any way that mixrbld/mixdfix
> can remedy.
So that is a good enough test? Will remember that in the future.
Of course the current problem indicates tha opposite as it very well opens,
but still doesn't work as expected...
> > I saw mixrbld as a means to fix this by rebuilding the mailbox. Ran
> > mixrdfix after this as I saw nothing at all in the mailbox after the
> > rebuild. Now the mails are there, but half of them always marked unread.
> > And cannot be marked as read whatever I do.
>
> I don't know what you did with mixrbld/mixdfix, but neither tool does
> anything with the status file, which is where seen state is kept.
Is ther any documentation on mix?
> > Just checked the source code and the actual message was from mixrbld and
> > was the one on row 181, printf ("Data file %s UID ran backwards.....
> > Isn't that "out of sequence".
>
> The text "out of sequence" does not occur in "Data file...ran backwards",
> and thus is a paraphrase. Please don't do that.
OK. But is does mean the same thing :-)
> If you got a "Data file...ran backwards" message, it is likely that some
> expunge operation did not complete properly. mixrbld will recover from
> this.
Shouldn't a rerun of mixrbld be clean in that case?
> mixcvt should have made a clean mailbox.
Didn't do that.
> I suggest that you try to find some expert who is local to you to look at
> it. There is nothing obvious that can be diagnosed from the other side of
> the world. It is obvious to me that there is more to this story than what
> you say, but unfortunately I do not have the time to investigate it.
I do know my way around C-programming and how to read manuals. Just wanted to
know if there is something simple I could do before digging into a protocol
analysis. Any other mix analyzing/fixing tool I can use?
> Unfortunately, I can't offer the same level of user assistance than I did
> when I was working at UW, and you seem to need much more assistance than I
> can offer. I'm sorry.
Understandable. Just wanted pointers in the right direction (and to mix docus)
Best
Dag
_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
