Menu
▾
▴
squirrelmail-users
|
From: Jason B. <jas...@mi...> - 2007-03-08 15:58:27
|
I've been trying to figure out a Squirrelmail problem. First one customer mailbox, and now a second, is having a problem where people can't read messages. (They get an error when they click the subject of a message) When I test the server using IMAP, with something like Outlook Express or Thunderbird, the mailbox and messages can be accessed normally. I tried setting up a test server with a new, clean Squirrelmail install, but it made no difference. (No extra plugins for Squirrelmail on the test install) SERVER: * CentOS 4.4 * Kernel 2.6.9-42.0.10.EL * Apache 2.0.52-28.ent * Postfix 2.2.10-1.RHEL4.2 * Dovecot 0.99.11-4.EL4 * Squirrelmail 1.4.8-4.el4 SYMPTOMS: * User can log in normally * Message subjects are listed normally * When you click on a subject to read the message, you get an error... 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). Click here to return to INBOX ----- Testing the same mailbox with Squirrelmail 1.4.9a and 1.5.1 showed no improvement. Copying the mail file to a test server, with a new test account, also showed no improvement. For whatever reason, Squirrelmail seems completely unhappy with the contents of this mail file. But it still responds fine through IMAP and a non-web-based email client. What can I do to take care of this problem? Is this a Squirrelmail bug, or what? As far as I can tell, it seems like it is. -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 |
|
From: Jason B. <Jason@MicroLnk.net> - 2007-03-08 15:55:48
|
I've been trying to figure out a Squirrelmail problem. First one customer mailbox, and now a second, is having a problem where people can't read messages. (They get an error when they click the subject of a message) When I test the server using IMAP, with something like Outlook Express or Thunderbird, the mailbox and messages can be accessed normally. I tried setting up a test server with a new, clean Squirrelmail install, but it made no difference. (No extra plugins for Squirrelmail on the test install) SERVER: * CentOS 4.4 * Kernel 2.6.9-42.0.10.EL * Apache 2.0.52-28.ent * Postfix 2.2.10-1.RHEL4.2 * Dovecot 0.99.11-4.EL4 * Squirrelmail 1.4.8-4.el4 SYMPTOMS: * User can log in normally * Message subjects are listed normally * When you click on a subject to read the message, you get an error... 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). Click here to return to INBOX ----- Testing the same mailbox with Squirrelmail 1.4.9a and 1.5.1 showed no improvement. Copying the mail file to a test server, with a new test account, also showed no improvement. For whatever reason, Squirrelmail seems completely unhappy with the contents of this mail file. But it still responds fine through IMAP and a non-web-based email client. What can I do to take care of this problem? Is this a Squirrelmail bug, or what? As far as I can tell, it seems like it is. -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 |
|
From: Paul L. <pa...@sq...> - 2007-03-27 16:37:12
|
On 3/8/07, Jason Byrns <Ja...@mi...> wrote: > I've been trying to figure out a Squirrelmail problem. First one > customer mailbox, and now a second, is having a problem where people > can't read messages. (They get an error when they click the subject of > a message) > > When I test the server using IMAP, with something like Outlook Express > or Thunderbird, the mailbox and messages can be accessed normally. I > tried setting up a test server with a new, clean Squirrelmail install, > but it made no difference. (No extra plugins for Squirrelmail on the > test install) > > SERVER: > * CentOS 4.4 > * Kernel 2.6.9-42.0.10.EL > * Apache 2.0.52-28.ent > * Postfix 2.2.10-1.RHEL4.2 > * Dovecot 0.99.11-4.EL4 > * Squirrelmail 1.4.8-4.el4 > > SYMPTOMS: > * User can log in normally > * Message subjects are listed normally > * When you click on a subject to read the message, you get an error... > > 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). > > Click here to return to INBOX > ----- > > Testing the same mailbox with Squirrelmail 1.4.9a and 1.5.1 showed no > improvement. Copying the mail file to a test server, with a new test > account, also showed no improvement. If you've found the offending message, you should strip it of private details and send it with your help request. Also include as much of your config.php file as seems appropriate. > For whatever reason, Squirrelmail seems completely unhappy with the > contents of this mail file. But it still responds fine through IMAP and > a non-web-based email client. > > What can I do to take care of this problem? Is this a Squirrelmail bug, > or what? As far as I can tell, it seems like it is. |
|
From: Paul L. <pa...@sq...> - 2007-03-27 19:28:16
|
---------- Forwarded message ----------
From: Paul Lesniewski <pa...@sq...>
Date: Mar 27, 2007 8:37 AM
Subject: Re: [SM-USERS] Squirrelmail error on two mailboxes ("The
server couldn't find the message you requested")
To: Jason Byrns <Ja...@mi...>
Cc: squ...@li...
On 3/8/07, Jason Byrns <Ja...@mi...> wrote:
> I've been trying to figure out a Squirrelmail problem. First one
> customer mailbox, and now a second, is having a problem where people
> can't read messages. (They get an error when they click the subject of
> a message)
>
> When I test the server using IMAP, with something like Outlook Express
> or Thunderbird, the mailbox and messages can be accessed normally. I
> tried setting up a test server with a new, clean Squirrelmail install,
> but it made no difference. (No extra plugins for Squirrelmail on the
> test install)
>
> SERVER:
> * CentOS 4.4
> * Kernel 2.6.9-42.0.10.EL
> * Apache 2.0.52-28.ent
> * Postfix 2.2.10-1.RHEL4.2
> * Dovecot 0.99.11-4.EL4
> * Squirrelmail 1.4.8-4.el4
>
> SYMPTOMS:
> * User can log in normally
> * Message subjects are listed normally
> * When you click on a subject to read the message, you get an error...
>
> 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).
>
> Click here to return to INBOX
> -----
>
> Testing the same mailbox with Squirrelmail 1.4.9a and 1.5.1 showed no
> improvement. Copying the mail file to a test server, with a new test
> account, also showed no improvement.
If you've found the offending message, you should strip it of private
details and send it with your help request. Also include as much of
your config.php file as seems appropriate.
> For whatever reason, Squirrelmail seems completely unhappy with the
> contents of this mail file. But it still responds fine through IMAP and
> a non-web-based email client.
>
> What can I do to take care of this problem? Is this a Squirrelmail bug,
> or what? As far as I can tell, it seems like it is.
|
|
From: Tomas K. <to...@us...> - 2007-03-09 05:36:09
|
> I've been trying to figure out a Squirrelmail problem. First one > customer mailbox, and now a second, is having a problem where people > can't read messages. (They get an error when they click the subject of > a message) > > When I test the server using IMAP, with something like Outlook Express > or Thunderbird, the mailbox and messages can be accessed normally. I > tried setting up a test server with a new, clean Squirrelmail install, > but it made no difference. (No extra plugins for Squirrelmail on the > test install) > > SERVER: > * CentOS 4.4 > * Kernel 2.6.9-42.0.10.EL > * Apache 2.0.52-28.ent > * Postfix 2.2.10-1.RHEL4.2 > * Dovecot 0.99.11-4.EL4 > * Squirrelmail 1.4.8-4.el4 > > SYMPTOMS: > * User can log in normally > * Message subjects are listed normally > * When you click on a subject to read the message, you get an error... > > 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). > > Click here to return to INBOX > ----- > > Testing the same mailbox with Squirrelmail 1.4.9a and 1.5.1 showed no > improvement. Copying the mail file to a test server, with a new test > account, also showed no improvement. > > For whatever reason, Squirrelmail seems completely unhappy with the > contents of this mail file. But it still responds fine through IMAP and > a non-web-based email client. > > What can I do to take care of this problem? Is this a Squirrelmail bug, > or what? As far as I can tell, it seems like it is. Have you tried removing dovecot index files? Have you checked newer dovecot version? Some dovecot 1.0 versions returned invalid responses to UID FETCH command. 0.99.14 works correctly. I don't know if issue is present in other 0.99.x versions. |
|
From: Jason B. <jas...@mi...> - 2007-03-09 17:58:51
Attachments:
testuser
|
First, thanks for the reply! > Have you tried removing dovecot index files? Unfortunately, that didn't help. > Have you checked newer dovecot version? Some dovecot 1.0 versions returned > invalid responses to UID FETCH command. 0.99.14 works correctly. I don't > know if issue is present in other 0.99.x versions. It was on my list of server specs. It's the standard Dovecot that comes with Redhat Enterprise 4 (CentOS 4). The version is 0.99.11-4.EL4. I have removed all existing messages from the account, sent one new test message, and it still has the same problem. I'm attaching a copy of the mail file in question, as the problem can be easily reproduced just with this one file. Steps to reproduce: 1) Set up new user account 2) Copy "testuser" mail file to your mail spool directory 3) Update file name or ownership, as necessary 4) Check with Squirrelmail You'll see one test message, but you should get the error when you try to read it. If it is indeed a Dovecot problem, why does regular IMAP work fine but not Squirrelmail? If necessary, I suppose I can install a newer Dovecot, but I'd much rather stick with the packages that come from the OS repository. (Otherwise, it makes it harder to keep the software up to date) -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 |
|
From: Tomas K. <to...@us...> - 2007-03-10 06:00:46
|
> First, thanks for the reply! > > > Have you tried removing dovecot index files? > > Unfortunately, that didn't help. > > > Have you checked newer dovecot version? Some dovecot 1.0 versions returned > > invalid responses to UID FETCH command. 0.99.14 works correctly. I don't > > know if issue is present in other 0.99.x versions. > > It was on my list of server specs. It's the standard Dovecot that comes > with Redhat Enterprise 4 (CentOS 4). The version is 0.99.11-4.EL4. > > I have removed all existing messages from the account, sent one new test > message, and it still has the same problem. I'm attaching a copy of the > mail file in question, as the problem can be easily reproduced just with > this one file. > > Steps to reproduce: > > 1) Set up new user account > 2) Copy "testuser" mail file to your mail spool directory > 3) Update file name or ownership, as necessary > 4) Check with Squirrelmail > > You'll see one test message, but you should get the error when you try > to read it. > > If it is indeed a Dovecot problem, why does regular IMAP work fine but > not Squirrelmail? If necessary, I suppose I can install a newer > Dovecot, but I'd much rather stick with the packages that come from the > OS repository. (Otherwise, it makes it harder to keep the software up > to date) Standalone imap clients can do processing locally. They don't use IMAP same way SquirrelMail does. SquirrelMail uses IMAP server to parse messages, because it is faster than parsing message structure in PHP. >From dovecot changelogs. v.0.99.14 - If UID FETCH notices and skips an expunged message, don't return a NO reply. It's not needed and only makes clients give error messages. If issue is specific to UID FETCH and FETCH is not broken, you can turn off uid support in SquirrelMail 1.4.x configuration. Also make sure that server side sorting is turned on in SquirrelMail configuration. v0.99.12 - FETCH BODYSTRUCTURE sometimes gave a wrong reply (eg. with FETCH (BODYSTRUCTURE RFC822.SIZE) if it wasn't cached) |
|
From: Jason B. <jas...@mi...> - 2007-03-15 16:46:48
|
> If issue is specific to UID FETCH and FETCH is not broken, you can turn off uid > support in SquirrelMail 1.4.x configuration. Also make sure that server side > sorting is turned on in SquirrelMail configuration. Server-side sorting has not been disabled, so that should be okay. I don't see any mention of UID support in the Squirrelmail config. What am I missing? (I looked both using conf.pl as well as the Administrator plugin) I tried updating to the latest available Dovecot (1.0 RC 26), but unfortunately that did not help. I'm starting to wonder about mail file corruption? I've seen a few examples on our server lately where people can't get their email. Then I have to go open their mail file with vi, and snip off a few extra blank or garbage lines from the top of the file. Perhaps that corruption is causing this problem as well. I've been meaning to get on to the latest version of Postfix for those servers, hoping that would eliminate the mail file corruption. (Or could it be Dovecot doing that?) Ever see the problem of mail files getting random lines of crap up top? -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 |
|
From: Jason B. <jas...@mi...> - 2007-03-15 18:22:44
Attachments:
test_mailfile
|
> I'm starting to wonder about mail file corruption? I've seen a few > examples on our server lately where people can't get their email. Then > I have to go open their mail file with vi, and snip off a few extra > blank or garbage lines from the top of the file. For further testing, I added IMP (and Horde) to the test server. It has the same problem, and is unable to show the body of the test message. What's wrong with the file, then?? Here it is again, a single test message in a mail file. IMAP client programs can get to the message okay, but Webmail programs don't like it! ........WHY? ;) Thanks again for the help! -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 |
|
From: Tomas K. <to...@us...> - 2007-03-16 14:47:04
|
>> If issue is specific to UID FETCH and FETCH is not broken, you can turn >> off uid >> support in SquirrelMail 1.4.x configuration. Also make sure that server >> side >> sorting is turned on in SquirrelMail configuration. > > Server-side sorting has not been disabled, so that should be okay. > > I don't see any mention of UID support in the Squirrelmail config. What > am I missing? (I looked both using conf.pl as well as the Administrator > plugin) > > I tried updating to the latest available Dovecot (1.0 RC 26), but > unfortunately that did not help. > > I'm starting to wonder about mail file corruption? I've seen a few > examples on our server lately where people can't get their email. Then > I have to go open their mail file with vi, and snip off a few extra > blank or garbage lines from the top of the file. > > Perhaps that corruption is causing this problem as well. I've been > meaning to get on to the latest version of Postfix for those servers, > hoping that would eliminate the mail file corruption. (Or could it be > Dovecot doing that?) > > Ever see the problem of mail files getting random lines of crap up top? Yes. I see incorrectly parsed messages, when I modify messages stored in maildir. It looks like Dovecot (Debian Etch package) caches file information and does not detect header size changes. Removal of dovecot cache files fixes the issue. -- Tomas |
|
From: Jason B. <jas...@mi...> - 2007-03-16 15:29:25
|
>> Ever see the problem of mail files getting random lines of crap up top? > > Yes. I see incorrectly parsed messages, when I modify messages stored in > maildir. It looks like Dovecot (Debian Etch package) caches file > information and does not detect header size changes. Removal of dovecot > cache files fixes the issue. All our accounts are in mbox format (all messages in one big file). But it certainly sounds like Dovecot is our problem, now. http://wiki.dovecot.org/MboxProblems Too bad Dovecot is buggy, I guess? That sucks. Especially as the standard POP/IMAP daemon for Redhat Enterprise (and CentOS). Any way to prevent these problems with Dovecot?? (I'll probably go looking for a Dovecot mailing list soon) -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 |
|
From: Wm M. <mus...@cs...> - 2007-03-16 16:40:55
|
On Fri, March 16, 2007 8:29, Jason Byrns said: >>> Ever see the problem of mail files getting random lines of crap up top? >> >> Yes. I see incorrectly parsed messages, when I modify messages stored in >> maildir. It looks like Dovecot (Debian Etch package) caches file >> information and does not detect header size changes. Removal of dovecot >> cache files fixes the issue. > > All our accounts are in mbox format (all messages in one big file). But > it certainly sounds like Dovecot is our problem, now. > > http://wiki.dovecot.org/MboxProblems > > Too bad Dovecot is buggy, I guess? That sucks. Especially as the > standard POP/IMAP daemon for Redhat Enterprise (and CentOS). > > Any way to prevent these problems with Dovecot?? (I'll probably go > looking for a Dovecot mailing list soon) > > -- > Jason Byrns > Production Manager > System Administrator > http://www.MicroLnk.com/ > 402-328-8600 ext. 653 > any reason not to switch to Maildir format? Occasionally I saw a disconnect between the message header's that SM reported and the body. It would resolve itself when I logged out and back into SM. We are on debian Sarge and use SquirrelMail 1.4.4 (debian patched version). I haven't seen this issue in about six months. We switched between mbox and maildir using a script mb2md and 2md.pl Basically we used the first to convert /var/spool/mail (or /var/mail depending on your setup) and then applied the 2md.pl to each of the mboxes in the user's IMAP store. We use procmail so we also added a MAILDIR=... line to the top of the .procmailrc file for each user. That way we converted each user, one at a time to the Maildir format. Vast speed increase. ------ William R. Mussatto Systems Engineer http://www.csz.com 909-920-9154 |
Thanks for helping keep SourceForge clean.
X