> From time to time I notice that Squirrelmail does not refresh the messages
> after delete or move. Refresh of the frame does not help too. Change of
> the pages does not help too. What helps is clicking on Inbox and going to
> the page with the message in question from there.
> Has anybody experienced anything like that?
> This is about Squirrelmail 1.4.3a with Courier.
> Thanks for your help,
Have you tried from several browsers and several computers to make sure it
is not a browser or cacheing issue? Is there a web cache between you and
the server? Is your browser checking for new pages each time? OS and
I have not seen issues on my 1.4.3a install using either Mozilla 7.2 or IE
6 on windows 2000/XP.
Mozilla 1.7.3 on Windows XP (Home and Professional). Tested it on least on
two different computers with completely different firewall and other
software. Happens through different ISPs in different countries.
It seems to start to happen on 2nd or 3rd such action after login. Click on
Inbox and then on the page where the deleted message is _always_ fixes the
issue (message is not there). But only changing pages within the Inbox does
not fix the issue (message stays there). Turning off of Mozilla cache does
Can it be something with the Squirrelmail pages or server issue?
Jonathan Angliss wrote:
> Trying to get my brain to play catch up, as somebody asked a question
> with a similar subject about the folder list not refreshing if you
> read a message, and visa versa.
:o) no worries, sorted now. It was the second time someone replied &
mis-understood what I was saying :o( .. In any case, getting understood
is the only concern. I just want to get squirrel rolling here, and start
working on making a couple of plugins that we need to make.
> Right, this is because we use a cached view of the mailbox. This only
> occurs if you don't enable server side sorting. Most IMAP servers
> support it (at least the top ones that spring to mind do)
Any idea if communigate supports server-side sorting ? The admins who
maintain it are not around for a few days, so just seeing if you or
anyone else here knows off the top of their head while I try find some
online docs to see if it's something they can do for me.
> We should refresh the cache after most operations, or at least update the
> flags in the cache for the changed messages, however I think something
> went astray there, which is what you are seeing. If your IMAP server
> supports server side sorting, I *strongly* recommend it, it'll save
> your IMAP server, and your web server a lot of work.
> Does that make sense, or am I in the wrong thread? :)
That makes sense. If I wasn't able to enable server-side sorting, but I
was able to make the use_mailbox_cache variable turn zero when
performing delete/unread/read actions, would that be something that the
squirrel team would want to use? Or would solving it require a more
complex/elegant solution ?