From: <po...@ve...> - 2004-10-27 19:10:19
|
Hello, 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, Iavor |
From: bob <squ...@no...> - 2004-10-28 11:38:59
|
Latest tests here observe the following: 1. The 1st page of email works reliably in all browsers 2. Any other page of email experiences the problems you have noted. 3. There is a variable used on every single page of mail EXCEPT page one called use_mailbox_cache 4. setting the variable on the pages where use_mailbox_cache to zero seems to get rid of any problems. Questions: 1. how does setting that variable to 0 affect use of squirrel in a high volume production environment, particularily when it comes to the amount of extra load it puts on the email server due to increased use of imap access due to a cache not being used? 2. why does squirrel not use this variable on page one? 3. what are the real benefits of using this variable and the code associated with it ? Possible Answers: 1. make squirrel set the variable to zero or manipulate the mailbox cache when moving, deleting or changing the read status of the email, so that the display reflects the mailbox accurately. For now, I am going for changing the variable, but this bug, once recognised officially, really needs fixing :o( po...@ve... wrote: >Hello, > >>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, > >Iavor > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Sybase ASE Linux Express Edition - download now for FREE >LinuxWorld Reader's Choice Award Winner for best database on Linux. >http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click >-- >squirrelmail-devel mailing list >Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines >List Address: squ...@li... >List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.devel >List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=7139 >List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel > >---------------Cleaned by Atlas Internet http://atlas.co.uk --------------- > > |
From: bob <bo...@no...> - 2004-11-01 03:30:02
|
Jonathan Angliss wrote: > It's fairly simple... Marc is in the process of rewriting how we > >handle emails from an IMAP server IF you don't have server side sort >enabled. > >But as you all know, devel means it is likely to break, be broken, >have bugs, be constantly changing etc etc. As such, Marc probably >hasn't got to the stage of fixing the cached information with the >changes. The fix to force the mailbox cache to false every page load >will work, but negates the whole point of using the cache in the first >place. I'll take a look, if somebody hasn't already, to see what we >can do about fixing the cache correctly. > > It is also broken in version 1.4, as well, which is why I became aware of it and posted my findings about discovering this. The mail was titled: Re: [SM-DEVEL] does not refresh and was posted on the 28th of this month. If squirrel is displaying multiple pages of email the 1st page worth works, primarily because it doesn't submit a variable to tell squirrel to use the mailbox cache, but subsequent pages submit a variable that means the cache is used and it doesn't work properly as a result. We found this out while doing an internal betatest and, if the additional overheads imposed by not using the cache are too much, it will prevent us from launching it as the foundation of our webmail client. I am suprised no-one has noticed this before, and even more suprised that it isn't a recognised bug within the current version :o/ |
From: Marc G. K. <ma...@sq...> - 2004-11-03 15:20:38
|
> Jonathan Angliss wrote: > > >> It's fairly simple... Marc is in the process of rewriting how we >> >> >> handle emails from an IMAP server IF you don't have server side sort >> enabled. >> >> >> But as you all know, devel means it is likely to break, be broken, >> have bugs, be constantly changing etc etc. As such, Marc probably >> hasn't got to the stage of fixing the cached information with the >> changes. The fix to force the mailbox cache to false every page load >> will work, but negates the whole point of using the cache in the first >> place. I'll take a look, if somebody hasn't already, to see what we >> can do about fixing the cache correctly. >> >> >> > > It is also broken in version 1.4, as well, which is why I became aware > of it and posted my findings about discovering this. The mail was > titled: Re: [SM-DEVEL] does not refresh and was posted on the 28th of > this month. If squirrel is displaying multiple pages of email the 1st > page worth works, primarily because it doesn't submit a variable to tel= l > squirrel to use the mailbox cache, but subsequent pages submit a > variable that means the cache is used and it doesn't work properly as a > result. We found this out while doing an internal betatest and, if the > additional overheads imposed by not using the cache are too much, it > will prevent us from launching it as the foundation of our webmail > client. I am suprised no-one has noticed this before, and even more > suprised that it isn't a recognised bug within the current version :o/ > > Okay, here an explanation of use mailbox cache: On login we retrieve a list of subscribed mailboxes and the belonging flags by doing an LSUB once and a LIST call for every subscribed mailbox to make sure the mailbox flags are correct / complete. On normal usage it's insane to retrieve that list on every reload of the left frame because all we are interested in is a change in the number of unseen messages per mailbox. Only when you hit the folder link on top of your page we refresh the list with subscribed mailboxes. If I'm correct use_mailbox_cache is used to control that behaviour in stable. In devel the url var use_mailbox_cache is removed and we refer to the session to retrieve the cached list and force to retrieve a non cache= d list when you enter the folders page. Now you probably understand why the left frame doesn't refresh your folderlist. It only updates the unseen/total count per mailbox. The reason why we do that is because of performance. The link above the mailboxlist is changed from "Refresh mailboxes" to "Check mail". Regards, Marc Groot Koerkamp. |
From: bob <bo...@no...> - 2004-10-28 11:21:28
|
We also seen this problem on 2 different windows. The people concerned experiencing this are not newbies either, and IE has been set to fetch a fresh page every time. We even installed a vanilla squirrel to check. I have now witnessed this on the mac version of firefox! However, when I opened the right frame in a seperate tab, and changed the variable use_mailbox_cache to zero, everything appears to work as it should. *note* this is most commonly demonstrated when one logs in and goes beyond the 1st page of emails displayed. This does hint at a caching issue ... but change the variable as above and finding it working better, leads me to believe it is not a caching issue and that the impression that it is, is a co-incidence. anywhere i can edit to make sure that this variable is always 0 so that the differences in performance can be observed ? I will do a grep to find myself but if a person knowledgable about the source can point me it might be quicker. *possible evidence that it is not a browser caching issue* I am not sure that it is possible to have a cached copy of the page. After all, according to my best guess, a variable is being passed to a php script on the server which needs to run and perform the action before going on to another php script which then generates a fresh page. A cursory scan of the pages served up by apache seems to show no difference in the number and sequence of pages served to a browser that works and one that doesn't. Someone who knows more might be able to explain how this is so, even though cached pages are being loaded ... but it is compeletely confusing me! My best deductions to date point to the po...@ve... wrote: >Hello, > >>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, > >Iavor > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Sybase ASE Linux Express Edition - download now for FREE >LinuxWorld Reader's Choice Award Winner for best database on Linux. >http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click >-- >squirrelmail-devel mailing list >Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines >List Address: squ...@li... >List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.devel >List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=7139 >List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel > >---------------Cleaned by Atlas Internet http://atlas.co.uk --------------- > > |
From: bob <squ...@no...> - 2004-11-03 16:06:57
|
Everything I was talking about in that email refers to things done in the RIGHT frame. Log into an account with a lot of email, enough so that squirrel has to list it over a few pages. Goto the second or third page of emails listed (this is essential because it will function correctly on the 1st page). Select some emails and then delete them. Notice that, when the list of emails (the right frame) refreshes, those mails you chose to delete are still there despite the the right frame having refreshed. If you chose to make read messages as unread, or unread ones as read, their status is not updated despite the the right frame having refreshed. system 1 tested on (my test box): apache 1.3.29 php 5.0.0 system 2 tested on (production server): apache 1.3.28 php 4.3.3 Both exhibit the same problem, whether running the latest stable or dev/cvs version. The only factor seperating whether or not it works is the use of the mailbox cache on all pages of mail EXCEPT the first page. Marc Groot Koerkamp wrote: > >Okay, here an explanation of use mailbox cache: > >On login we retrieve a list of subscribed mailboxes and the belonging >flags by doing an LSUB once and a LIST call for every subscribed mailbox >to make sure the mailbox flags are correct / complete. > >On normal usage it's insane to retrieve that list on every reload of the >left frame because all we are interested in is a change in the number of >unseen messages per mailbox. >Only when you hit the folder link on top of your page we refresh the list >with subscribed mailboxes. > >If I'm correct use_mailbox_cache is used to control that behaviour in >stable. In devel the url var use_mailbox_cache is removed and we refer to >the session to retrieve the cached list and force to retrieve a non cached >list when you enter the folders page. > >Now you probably understand why the left frame doesn't refresh your >folderlist. It only updates the unseen/total count per mailbox. > >The reason why we do that is because of performance. The link above the >mailboxlist is changed from "Refresh mailboxes" to "Check mail". > > > |
From: Jonathan A. <jo...@sq...> - 2004-11-03 23:19:02
|
Hello Bob, On Wednesday, November 03, 2004, bob wrote... > Everything I was talking about in that email refers to things done in > the RIGHT frame. 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. > Log into an account with a lot of email, enough so that squirrel has > to list it over a few pages. > Goto the second or third page of emails listed (this is essential > because it will function correctly on the 1st page). > Select some emails and then delete them. > Notice that, when the list of emails (the right frame) refreshes, those > mails you chose to delete are still there despite the the right frame > having refreshed. 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), and allow for us to avoid doing the big nasty sort work ourselves. Because the sort is so intensive for PHP, we try to avoid doing it as often as possible, and use a cache after the first time of loading a folder. 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? :) -- Jonathan Angliss (jo...@sq...) Posting Hints: http://www.squirrelmail.org/wiki/en_US/MailingListPostingGuidelines |