> Hello Terry, > On Tuesday, February 24, 2004, Terry Griffin wrote... > >> This problem was 100% repeatable for me on a Red Hat 7.0 box (Apache 1.3.27-3.71, PHP 4.1.2-7.0.6). It kept me from upgrading to >> SquirrelMail 1.4.x from 1.2.11. Now I have a temporary Red Hat 9 box in it's place while the original box is being serviced and upgraded. This problem with 1.4.x has gone away (Apache 2.0.40-21.9, PHP >> 4.2.2-17.2.). > > Their are two issues you now have. You have no way of telling if it was a newer apache, or even a rebuild of the existing apache (that doesn't mean just reinstalling the RPMs), or the new PHP (or rebuild of existing one). In the past I had suggested a rebuild of PHP, or upgrade of PHP, and either/both have worked (from memory). >
Well, it's not really *my* issue. For me the problem is solved. The fellow who started this thread is running Red Hat 7.3 and he still has the problem AFAIK. I was just contributing to the thread by giving my observation of what happened with a recent OS upgraded. This upgrade happened well before the thread started, and not for the purpose of fixing the SquirrelMail 1.4.x issue. That fact that it did fix 1.4.x was just something I discovered afterwards. One more small data point: I think the final PHP and Apache on my Red Hat 7.0 box might have been Red Hat 7.1 updates. I had been consistently applying 7.1 security updates (except for the kernel) to 7.0 after Red Hat ceased support for 7.0. Terry -- Terry Griffin Axian Inc. http://www.axian.com/ ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
