On Tuesday 22 May 2007 11:02, Ross Boylan wrote: ... > 4> a0006 UID STORE > 194:223,225:269,489,500,513,517,519:521,523:524,526,528,531,541:542,544:545 >,552:553,555:556,562:563,566:568,570:572,2238:2245,2261:2265,2269:2274,2276, >2289:2290,2292:2294,2298,2300:2301,2303:2306,2308:2310,2312:2314,2321:2323,2 >339:2341,2347:2348,2350,2357,2360:2361,2365,2369:2374,2399:2401,2403,2414,24 >16:2418,2420:2423,2425:2428,2440:2441,2443,2450:2451,2455:2461,2464,2472,248 >0:2482,2487:2489,2491,2509:251 # many more UID's > ,30851:30859,30861 +FLAGS.SILENT (Old) > mutt_socket_write: ERROR: wrote 4091 of 30105 bytes! > > So it looks as if the UID list is too long. > Perhaps I'm not seeing it other cases because a more natural contiguous > range (e.g., 1:20000) can cover the messages in a few characters. My INBOX > has a lot of out of temporal sequence messages as a result of the way it > was populated. It also has a lot of gaps in UIDs as a result of moving > messages out of the INBOX. > > I'm not sure how much energy this is worth to repair. The fundamental > problem is that mutt, like almost every other email client, is trying to > represent and manipulate every single message in the folder rather than > just enough messages to fill the screen. Mulberry, which was recently > open-sourced, is the only one I'm aware of that does better. It's possible > evolution does too, but it has some other bugs right now. > > In other words, even if this were fixed, the results would still be quite > slow for large boxes. > In this particular case there are probably ways of getting around the problem other than expanding the allowable message length.
1. If, as seems to be the case, the intent is to do a STORE for every message in the box (except ones that arrived since mutt formed its index) there are easier ways to do so. IMAP says unknown UID's are silently ignore, so 1:nnnnn would suffice for the range (or maybe 0:nnnn). IMAP says new messages get increasing UIDs, and provides a call to get the current top UID. One could also use the session ids, which are consecutively numbered (though then one would need to track deletions that lower nnnn). In either case one would want to avoid touching messages that arrived after mutt got its index. 2. Maybe in this case using the \Recent flag, instead of Old, would suffice? \Recent is updated automatically by the server. Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
