> 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) > 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. > Thanks for the notes Nick. I can see there's more I need to add to my research list. Cheers Don
