On Tue, 13 Apr 2004 21:53, Don Gould wrote: > > From: Nick Rout [mailto:[EMAIL PROTECTED] > > how soon did you look at the folder to see if it moved? > > Seconds later... I flicked to Mozilla (after waiting for Mozilla mail to > finish doing what it was doing - moving the records) clicked the refresh > button (the application one rather than the browser one) and waited... > moments later (yes, moments not seconds (as I had expected)) the list > reappeared with all the messages still displayed. > > > often it *appears* to > > remain in the old folder until you "close" that folder by clicking on > > another. That is to say, the client you did the moving in > > (client 1) will > > show it as moved, but it will still be in that folder on the > > server. another > > client (like your web client, call it client 2) will still > > see it because the > > server does not actually delete it until client 1 closes the > > folder., usually > > by clicking on another one or by closing the client. > > Yes I can see it doesn't behave as well as exchange server does when you do > things. > > > which server and which web client? > > The web client is Open WebMail version 2.30 > (http://www.bvc.com.au/openwebmail/openwebmail.html)
I'll ask again, what server? > > > imap is a fine standard, but the implementations are > > sometimes buggy, and > > there are ambiguities in the standard, and the client > > implementations are not > > entirely consistent. > > > > usenet's comp.mail.imap is a good place to go for the real > > oil. The developers > > of UW server (who wrote the standard), and courier seem to > > hang about there. > > They will expect you to have done some homework, but thats to > > be expected. I'll add that the main problem seems to be that most programmers start writing a pop client that downloads mail to the local machine. When they migrate this to include imap they do not consider that it is a very different paradigm. Their clients insist on caching every damn header on the server, and taking ages to synchronise them. its a pain. One of the best, and most standards compliant email clients is mulberry, a commercial offering that works on mac, win and lin. It caches nothing by default. When it connects it downloads the last n headers, where n is the number of lines that will fit in the list of emails. no wasted time synchronising headers from last week, or last decade. When a client wants to search every header in the inbox for messages from "don" with the subject "imap" it tells the _server_ to do the search, rather than searching through locally cached headers. It is a very nice program, and does imap how it should be done. But I rave, try it for yourself :-) > > Thanks for the notes Nick. I can see there's more I need to add to my > research list. > > Cheers Don
