Re: [Imap-uw] Unread flag always on after reindexing
fredag 13 mars 2009 04:18:58 skrev Mark Crispin:
> I am very confused reading this message.
>
> Why did you run mixrbld and mixdfix? These are very powerful tools that
> should only be run in specific circumstances.
It is too long ago I did this for me to remember the exact reason. I think it
had something to do with kmail complaining about an attibute missing for
certain mail when doing a search.
Sounded very much like a corruption in the mailbox to me, Especially since it
happened only in my INBOX.
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.
> What were the exact text of any complaint messages which you received?
> Those message are very specific. Paraphrasing them in a problem report
> destroys their usefulness.
>
> There are several messages in mixrbld, mixdfix, and the mix driver in
> c-client; but none contain the string "out of sequence".
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".
I did check this up and found that you have indicated earlier that it is not a
real problem. Also tried mixcvt to copy the mailbox as somewhere suggested,
but even the result still had the same problem.
> I have no idea what kmail and horde/IMP webmail do. Have you tried access
> with Alpine? If so, what behavior do you see?
Don't have Alpine here, but checked with thunderbird, and still have the same
thing.
Best
Dag
___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
Re: [Imap-uw] Best way to refresh the message numbers of a stale folder?
On Fri, 13 Mar 2009, Shawn Walker wrote: The application has multiple threads with 2 connections to the IMAP server. One of them is for IDLE. This application does not use c-client to do IMAP client. c-client does not support client-end IDLE. Presumably, by "thread", you mean threads in a process as opposed to message threads. UW imapd does not run multi-threaded; each IMAP session has its own process. Nor does the c-client library use threads. So, whatever is threading and using IDLE does not seem to have anything to do with c-client or imapd. When something happen on the IDLE thread, the server send a list of untagged IMAP commands to the client of what happened. The server sends untagged IMAP responses, not commands. The IDLE thread see that it need to update a folder, but the IDLE thread has two messages the UID of 100 and 101 (an example). But, UID 101 is doesn't exist anymore, but UID 102 is on the server. So, the IDLE thread request the message cache for UID 102 but c-client doesn't know about 102 in it's message cache due that it only know of UID 100 and 101 and return with a NIL. Hence, the message cache is stale. This makes no sense, so I have to guess what you are talking about. My guess is that client has two IMAP sessions open. One of those sessions did an IDLE command that notified the client of new messages. You expected that the other session would instantaneously know about those new messages, even though that session had not yet been notified. That is not the way IMAP works. Each IMAP session has its own independent state, and is notified of new messages independently. Why do you have two IMAP sessions open on the same mailbox? That, by itself, suggests that you are not using IMAP properly. No well-written application should need more than one IMAP session open to a mailbox at a time. The only way that I can get the message cache to throw away it's message cache is to disconnect from the server and then reconnect to the server and then the message cache will have UID 100 and 102. It there is a change in the mailbox state, the session will be notified of that fact as part of executing a command. State changes do not magically transfer from one session to another. What I need is to tell c-client to refresh it's message cache to have UID 100 and 102. Is there a c-client call that I make that will do that? You need to execute a command. If nothing else, a NOOP command. -- 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 Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
Re: [Imap-uw] Best way to refresh the message numbers of a stale folder?
The application has multiple threads with 2 connections to the IMAP server. One of them is for IDLE. When something happen on the IDLE thread, the server send a list of untagged IMAP commands to the client of what happened. The IDLE thread see that it need to update a folder, but the IDLE thread has two messages the UID of 100 and 101 (an example). But, UID 101 is doesn't exist anymore, but UID 102 is on the server. So, the IDLE thread request the message cache for UID 102 but c-client doesn't know about 102 in it's message cache due that it only know of UID 100 and 101 and return with a NIL. Hence, the message cache is stale. The only way that I can get the message cache to throw away it's message cache is to disconnect from the server and then reconnect to the server and then the message cache will have UID 100 and 102. What I need is to tell c-client to refresh it's message cache to have UID 100 and 102. Is there a c-client call that I make that will do that? Mark Crispin wrote: On Thu, 12 Mar 2009, Shawn Walker wrote: What is the best way to refresh a stale folder state? I'm having a issue with one thread that contain a stale UID in it's cache. I don't know what you mean by a "folder state", much less a "stale folder state" or the act of refreshing such; nor what "message numbers of a stale folder" may be; nor what a "thread that contains a stale UID in its cache" may be. I know that I could disconnect from the server and reconnect, but is rather expensive to have to wait for the server/client to connect. I'm even more bewildered reading this sentence than I am the previous one. Please explain what behavior that you are seeing, and what behavior you expect in its place. Maybe I'm going senile; I haven't a clue as to what you're talking about. -- 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. -- Shawn Walker Senior Software Developer Bynari, Inc. 6220 Gaston Ave, Suite 403 Dallas, Tx 75214 http://www.bynari.net swal...@bynari.net (800) 241-1086 (214) 350-5772 X29 (214) 352-3530 fax ___ Imap-uw mailing list Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
Re: [Imap-uw] Unread flag always on after reindexing
I am very confused reading this message. Why did you run mixrbld and mixdfix? These are very powerful tools that should only be run in specific circumstances. What were the exact text of any complaint messages which you received? Those message are very specific. Paraphrasing them in a problem report destroys their usefulness. There are several messages in mixrbld, mixdfix, and the mix driver in c-client; but none contain the string "out of sequence". I have no idea what kmail and horde/IMP webmail do. Have you tried access with Alpine? If so, what behavior do you see? On Thu, 12 Mar 2009, Dag Nygren wrote: After running mixrbld my mix-format inbox always shows about half of the box is unread, both in kmail and accessed from my horde/imp webmail. Trying to mark the mails as read doesn't do anything. Have also tried using mixdfix. Doesn't change anything though. Had complaints about mails being out of sequence from one of the tools, don't remember which. The mailbox has once been transformed from MH to mix format, but worked fine for months after that. Could this explain the numerous "out of sequence" messages from the rebuild process? Any hints on how to fix this. Now it is a bit hard to spot new mails... -- 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 Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
Re: [Imap-uw] Best way to refresh the message numbers of a stale folder?
On Thu, 12 Mar 2009, Shawn Walker wrote: What is the best way to refresh a stale folder state? I'm having a issue with one thread that contain a stale UID in it's cache. I don't know what you mean by a "folder state", much less a "stale folder state" or the act of refreshing such; nor what "message numbers of a stale folder" may be; nor what a "thread that contains a stale UID in its cache" may be. I know that I could disconnect from the server and reconnect, but is rather expensive to have to wait for the server/client to connect. I'm even more bewildered reading this sentence than I am the previous one. Please explain what behavior that you are seeing, and what behavior you expect in its place. Maybe I'm going senile; I haven't a clue as to what you're talking about. -- 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 Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
[Imap-uw] Best way to refresh the message numbers of a stale folder?
What is the best way to refresh a stale folder state? I'm having a issue with one thread that contain a stale UID in it's cache. I know that I could disconnect from the server and reconnect, but is rather expensive to have to wait for the server/client to connect. Regards, Shawn ___ Imap-uw mailing list Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
[Imap-uw] Unread flag always on after reindexing
Hi After running mixrbld my mix-format inbox always shows about half of the box is unread, both in kmail and accessed from my horde/imp webmail. Trying to mark the mails as read doesn't do anything. Have also tried using mixdfix. Doesn't change anything though. Had complaints about mails being out of sequence from one of the tools, don't remember which. The mailbox has once been transformed from MH to mix format, but worked fine for months after that. Could this explain the numerous "out of sequence" messages from the rebuild process? Any hints on how to fix this. Now it is a bit hard to spot new mails... Best Dag ___ Imap-uw mailing list Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
