Paul Lesniewski wrote: > Reply on-list please. > > On 8/23/07, John Hinton <webmaster@xxxxxxxx> wrote: > >> Paul Lesniewski wrote: >> >>> On 8/23/07, John Hinton <webmaster@xxxxxxxx> wrote: >>> >>> >>>> Paul Lesniewski wrote: >>>> >>>> >>>>> On 8/23/07, John Hinton <webmaster@xxxxxxxx> wrote: >>>>> >>>>> >>>>> >>>>>> CentOS 4 systems at least >>>>>> Dovecot >>>>>> Sendmail >>>>>> SquirrelMail 1.4.8 >>>>>> >>>>>> I have a random problem with some accounts. It seems to mostly affect >>>>>> only the root account of a virtual domain. >>>>>> >>>>>> They can login and use SquirrelMail fine. Then suddenly one day they can >>>>>> login, see the list of emails in their inbox, but SquirrelMail says the >>>>>> message has gone away when you click to open it. >>>>>> >>>>>> I can create another folder. Move the message to that folder and open >>>>>> and read it fine. >>>>>> >>>>>> It seems that every function works just like it should except for the >>>>>> read function and only then on the Inbox. >>>>>> >>>>>> We store the root user info in /var/www/<username> >>>>>> >>>>>> >>>>>> >>>>> User account under the web tree?!? Not their mail data, right?!? >>>>> >>>>> >>>>> >>>> Right. As this we run fairly standard sendmail setups, the inbox is >>>> actually in /var/spool/mail >>>> >>>> >>>>>> We store other account under that virtual host in >>>>>> /var/www/homes/<otheruser.domainprefix> >>>>>> >>>>>> >>>>>> >>>>> This is really really bad >>>>> >>>>> >>>>> >>>>> >>>> Yeah, that would be... it's actually >>>> /var/www/<mainusername>/homes/<otheruser.mainusername> >>>> >>>> >>> Why is there ANY user data (mail or not) in the web tree? Unless it's >>> all website stuff... but none of that is related to SM anyway. >>> >>> >>> >>>>>> This is very random, happening only to a few accounts and again, it >>>>>> seems to just start happening for no apparent reason. Almost all root >>>>>> accounts work fine.. then suddenly one breaks at random and stays broken. >>>>>> >>>>>> Does anyone have any ideas where to start looking? >>>>>> >>>>>> >>>>>> >>>>> Server error logs. Send message samples (full headers and content). >>>>> Upgrade SM. >>>>> >>>>> >>>>> >>>> We follow RedHat with updates as we are running CentOS. I actually do >>>> run the dag repository as well and IIRC, his repository is actually >>>> where the last few squirrelmail updates have come in. >>>> >>>> There are no problems with the messages. I can delete the mailfile, send >>>> a message in myself and the same thing happens. >>>> >>>> Nothing shows up that I can find in the server logs.. I just get this >>>> message in SquirrelMail: >>>> >>>> "*ERROR:* >>>> >>>> The server couldn't find the message you requested. >>>> >>>> Most probably your message list was out of date and the message has been >>>> moved away or deleted (perhaps by another program accessing the same >>>> mailbox). >>>> >>>> >>> That's a much different error than you gave the impression of (which >>> is why you should always include this the first time). This is >>> usually due to an out-of-synch UID cache issue. But if it happens >>> only with one message no matter if you log out and back in again, >>> etc., then the issue may be related to the message or the IMAP server. >>> >>> >>> >>>> I've been watching maillog, messages, access_log and error_log. Do I >>>> need to turn up logging? Where should the error show up? >>>> >>>> Meanwhile SquirrelMail will let me select (toggle) a message and move it >>>> to a different folder, even though it seems to think the message isn't >>>> there... and once it is in the other folder it will let me open it. >>>> >>>> >>> I would test with SM 1.4.10 before worrying any more about this. >>> >>> >> I'm running >> >> squirrelmail-1.4.8-4.0.1.el4.centos.noarch.rpm >> >> which is the latest update from RHEL compiled for CentOS. I don't like >> to step outside of what is supposedly know to work by RedHat. >> > > Then suffer its bugs and don't expect support from developers who may > have already fixed such issues or ask RedHat for support. > > SM is a very simple PHP script. You can install it from tarball in > minutes (without destroying the one you get via RedHat) and probably > use the same config file as well. > > >>>> SquirrelMail will also let me select (toggle) individual messages within >>>> the inbox and it allows me to successfully delete them. It just won't >>>> let me click on a subject line to open one to read while it is in the >>>> >>>> >>> ANY messages? Or just one or two? >>> >>> >>> >> Any message, one message, all messages. I can't read any of them. I can >> delete any or all of them. I can move any or all of them and once they >> are outside of the INBOX I can read any or all of them. The only thing I >> cannot do is read a message while it is in the INBOX. >> >> Of about 500 hosted domains across 14 servers, I am aware of only about >> 6 accounts which have this problem. SquirrelMail is available to all our >> users, but the vast majority never use it. So this is not a problem with >> 1% of the SquirrelMail users.. but more likely 10% or so. It has >> happened now on at least three different servers... same exact problem. >> >> >>>> inbox. All other messages in all other folders work fine. >>>> >>>> The other oddity, is this is just on a few accounts not all of them. It >>>> is happening on multiple servers. So far each time it has occurred on >>>> the root user account... so far not on any of the sub-accounts. >>>> >>>> >> John Hinton >> >> This is not a SquirrelMail bug but instead a Dovecot pre 0.99.13 bug. It allows the X-UID header for emails to grow too large. Even deleting the mail INBOX and recreating it does not make this issue go away. The cure.... Upgrade Dovecot. Shut down your mail system including Dovecot. Move to the main mail directory such as /var/spool/mail For the user having the problem, lets say his name is david, run: grep -v '^X-UID: ' david > david2 grep -v '^X-IMAPbase: ' david2 > david rm david2 check that permissions on david held cd ~david/mail (assuming you are using mail as the IMAP mail storage area) cd INDEX ls -al Find the .imap.index files and/or the dovecot.index files and delete them. Restart your mailservices. Test reading email in the INBOX in SquirrelMail. Note: It is a good idea to make backups of key files. Other notes on Dovecot 1+ This version has the ability to set the default IMAP mailfolder, which appears to be a very good idea due to Outlook issues. If you do set this folder in Dovecot, you will want to unset it in SquirrelMail or you'll wind up with ~<user>/mail/mail, assuming you are using mail as the folder name. Also, $imap_server_type = 'uw'; seems to work fine and the delimiter is $optional_delimiter = '/'; Sorry to be misdirected with this, but I really didn't know just how many services SquirrelMail provided. Best, John Hinton ------------------------------------------------------------------------- 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
