On 1/8/04 9:07 PM, "Charlie Fritzius" <[EMAIL PROTECTED]> wrote:
> on 1/8/04 8:55 PM, jud spencer at [EMAIL PROTECTED] wrote: > >> On 1/8/04 8:50 PM, "Julian Vrieslander" <[EMAIL PROTECTED]> wrote: >> >>> I've tried many variations of the IMAP settings for my work account on the >>> server at U of Washington (UW-IMAP, natch). Right now I've got a config >>> that works OK most of the time. But even though the traffic in this account >>> is very low (maybe 5 messages per day), I still get corruption in my client >>> database every few weeks, requiring advanced rebuild to fix. >> >> Hmm., I use a UW-IMAP implementation as well and don't have any problems of >> the sort. I will say that the UW implementation is perhaps the worst that I >> have seen. > > While I do understand this statement and tend to agree, I find if very odd > that UW-IMAP's implementation of IMAP is so bad. After all, THEY INVENTED > IMAP! Why can't they get IMAP right!?!? It just boggles the mind... The UW-IMAP developers apparently feel that the problems are in Entourage. Here is a quote from a website maintained by the UW Computing and Networking Group: <http://www.washington.edu/imap/IMAP-FAQs/> >>>>> 7.39 Why doesn't Entourage work at all? It's hard to know. Entourage breaks almost every rule in the book for IMAP. It is highly instructive to do a packet trace on Entourage, as an example of how _not_ to use IMAP. It does things like STATUS (MESSAGES) on the currently selected mailbox and re-fetching the same static data over and over again. It seems that every time we understand what it is doing wrong in Entourage and come up with a workaround, we learn about something else that's broken. Try building imapd with the ENTOURAGE_BRAIN_DAMAGE option set, in order to disable the diagnostic that occurs when doing STATUS on the currently selected mailbox. >>>>> I am not competent to judge whether the fault lies with UW-IMAP or Entourage. Maybe it would be worthwhile for someone on the Entourage team to contact the UW-IMAP group and compare notes. I can't help with the technical issues, but (since I am at UW) I would be willing to make a couple of phone calls to find an appropriate local contact, and forward the info to Jud. Mark Crispin is still here, but I don't know if he is still actively working on IMAP. I can't provide a recipe to reproduce the client DB corruption that I occasionally see. But I can provide a few relevant facts. I sometimes save an unsent message in my IMAP Drafts folder, and then reopen, edit and send it later. Since I access this IMAP account from three Macs, I might send the message from a different computer than the one used to save the draft. After sending the message, I usually try to delete the draft. Sometimes it cannot be deleted from my local Drafts folder, and that's the tipoff that the DB is corrupted (or out of synch). The message is apparently not on the IMAP server. If I check the Drafts folder on another Mac, the message does not show. An advanced rebuild gets rid of the undeletable message. Currently I have one of these undeletable messages in the Drafts folder on my work Mac. If it would be useful, I can provide Jud with a copy of the DB. I can even provide a copy of the DB from another Mac which does not show this message. This is Entourage X 10.1.4, running in Mac OS X 10.3.2, with IMAP4rev1. All options in IMAP Account "Options" tab are disabled. All options in the "Advanced" tab are disabled except for "Save sent messages in mail/Sent Items folder", "Save Drafts in mail/Drafts folder", and "Purge deleted messages when quitting Entourage." -- Julian Vrieslander <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
