On 9/17/07, Scott Moseman <scmoseman@xxxxxxxxx> wrote: > On 9/14/07, Scott Moseman <scmoseman@xxxxxxxxx> wrote: > > On 9/14/07, Wm Mussatto <mussatto@xxxxxxx> wrote: > > > > > > > I have one user who occasionally has a unique problem. She will > > > > continue receiving email, but she's unable to move or delete them in > > > > Squirrelmail. She can't even mark them as read. And the interface is > > > > very slow to respond. If I simply open/close her mailbox with pine, > > > > the problem vanishes. Response is back to being quick, she can move, > > > > delete and whatever else. > > > > > > Might help to provide more information. Like, Mail Delivery Agent (e.g., > > > dovecot). I've seen slow response when someone goes into a folder that > > > they haven't accessed for a while because, I think, that Dovecot does a > > > reindex for the new entries. If I go back in the huge mailbox after a bit > > > I get great response because Dovecot continues to index and the next time > > > the box is accessed the indexes are up to date. You could have something > > > similar and its totally outside of SM's area. Don't know if this matches > > > what you are seeing. > > > > > > > Email is received and delivered with sendmail+procmail. > > Email is retrieved using SquirrelMail on Apache with UW. > > > > At this point, we've noticed no lengthy delay that solves it. > > I think the problem was going on for over a day this last time, > > and the mailbox was only about 13MB in size. Not too large. > > > > I suppose the next time I see the problem I will make a copy of the spool, > open/close it with pine to "fix" the problem, and diff them to see what was > changed by pine to resolve the problem. I guess it isn't a common issue. > I'm looking at a diff on the mail spool before and after I opened it with pine to "fix" the problem. The MAILER-DAEMON internal format msg has an updated timestamp and some X-* headers were added to the last 5 messages in the spool -- although there's more than 5 unread. So I still have no clue what was going on with the spool before I used pine to open it and "fix" it. Although I do see several of these errors in the log prior to the user telling me that they were having a problem... imapd[22090]: Command stream end of file, while reading line user=xxxxxxxx host=localhost [127.0.0.1] But I couldn't tell you if something happened to cause the problem to the spool that caused the imap problem, or if perhaps the imap server caused the problem itself. I guess it's not a SM issue, AFAIK, unless the SM to IMAP interaction has a problem somewhere. Not sure how in the world to troubleshoot at this point. Maybe I can try a different IMAP service and see if the problem comes back again? Thanks, Scott ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
