> Hello,
>
> I'm new to this list.
>
> We are having some trouble with a second installation of Squirrelmail and
> would like some pointers on how
> to get it working.
>
> We have been using Squirrelmail for a couple of years. We installed it on
> our main web server - an Intel box running Redhat Linux 7.1. It has
> become
> a very popular service, and many people in our departments have come to
> depend on
> it.
>
> We plan to replace the old web server with a newer system which will run
> Redhat Enterprise AS 3.0. Prior to making that change, we are testing
> some
> of our changes on a system running Fedora Core 2 ( we'll repeat the tests
> on the new host under RHEL-AS-3). The two systems are compared below:
>
> OS Fedora Core 2 Redhat Linux 7.1
> Kernel 2.6.8-1.521 2.4.20-28.7
> PHP 4.3.8-2.1 4.1.2-7.1.6
> PHP-MYSQL 4.3.8-2.1 4.1.2-7.1.6
> PHP-PEAR 4.3.8-2.1 none
> PHP-MBSTRING 4.3.8-2.1 none
> PHP-LDAP 4.3.8-2.1 4.1.2-7.1.6
> PHP-IMAP none 4.1.2-7.1.6
> LIBGHTTP_DEVEL none 1.0.8-2
> LIBGHTTP 1.0.9-9.1.1 1.0.8-2
> HTTPD (Apache) 2.0.51-2.7 1.3.27-3.7.1
> SQUIRRELMAIL 1.2.6-1 1.2.6-1
> DocumentRoot /var/www/html /usr/local/etc/httpd/htdocs/{dept}
>
> All packages were installed via rpm.
>
> The imap server is running on a different host, and shows
>
> PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT
> THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] IMAP4rev1 2001.315 at
> Thu, 4 Nov 2004 09:59:01 -0500 (EST)
>
> which should be the University of Washington imapd that comes with Pine.
>
> We tested using IE 6 SP1, Firefox 0.9.2 and Mozilla 1.8a1 Cookies are on,
> and these same browsers on the same host work with the Linux 7.1 and Sm
> 1.2.6-1 installation, and use the same iimap server host.
>
> Directory permissions, etc...
>
> Object Owner Group Mode
> /var/lib/squirrelmail root root drwxr-xr-x
> /var/lib/squirrelmail/prefs nbapach nbapach drwx------
> /var/spool/squirrelmail root root drwxr-xr-x
> /var/spool/squirrelmail/attach nbapach apache drwx------
>
> I know the docs recommend mode 0730 for the attachment directory, but
> setting the attachment directory to that value did not affect our results,
> nor did changing the group to nbapach. I made sure the Fedora 2 host had
> directories set up identically as they were on the Redhat 7.1 host that
> successfully runs Squirrelmail.
>
> Both hosts are in the same subdomain (different subnets), and are in the
> same NIS domain. On both hosts, httpd runs under the unprivileged account
> 'nbapach' (and under group 'nbapach').
>
> We initially tried the squirrelmail that comes with Fedora Core 2
> (1.4.2-3); on the test host. After editing the config.php file using
> conf.pl, pointing our browser at the correct URL resulted in the correct
> file (login.php) being accessed, but only a blank page was displayed. We
> would see
>
>
> <html><body></body></html>
>
> if we viewed the page source in the browser. I've looked for this problem
> on squirrelmail.org, but found nothing that seemed to deal with this
> problem. I'm just starting to learn php, and am not up to debugging this
> problem yet.
>
> The apache logs indicated that /var/lib/php/session (defined in php.ini as
> session.save_path) had incorrect permissions. Correcting that did not
> alleviate the problem with 1.4.2-3. When trying 1.2.6-1, no errors are
> logged. The session.save_path for the 7.1 host is set to /tmp.
>
> I looked at the Redhat Enterprise AS 3 distribution, and noticed it uses
> squirrelmail-1.2.11-1; since 1.2.6-1 works so well (and only took about 10
> minutes to get working originally under 7.1), I un-installed 1.4.2-3 and
> installed 1.2.6-1 on the Fedora 2 host, and copied the config.php from the
> working installation. This time, the initial squirrelmail login page
> would
> appear, but whenever I login, I get
>
> ERROR
> You must be logged in to access this page.
> Go to the login page
>
> and would be in a redirect page.
>
> The exact same setup works under 7.1 and apache 1.3.27. I've followed
> recommendations found in the squirrelmail archives (check/fix
> session_save.path, cookies on, etc.) but had no success.
>
> After turning on php debugging in php.ini and trying to use squirrelmail,
> I
> could see the error messages
>
> Warning: logout_error(/squirrelmail/functions/page_header.php): failed to
> open stream: No such file or directory in
> /home/copahee/www/html/squirrelmail/functions/display_messages.php on line
> 99
>
> Warning: logout_error(): Failed opening
> '/squirrelmail/functions/page_header.php' for inclusion
> (include_path='.:/usr/share/pear') in
> /home/copahee/www/html/squirrelmail/functions/display_messages.php on line
> 99
>
> That line (99) is:
> include_once($DOCUMENT_ROOT . $base_uri . 'functions/page_header.php' );
>
> However, correcting that with brute force (i.e., not trying to fix the php
> code, but simply creating a (temporary) symlink so that /squirrelmail ->
> /var/www/html/squirrelmail), the php error messages disappear, but the
> "You
> must be logged in" message from squirrelmail still appears.
>
> It does appear that display_messages.php may not have a valid
> $DOCUMENT_ROOT and that $base_uri is set (probably) to '/squirrelmail/'
>
> I'd like to have Squirrelmail tested and functional prior to cutting over
> to the new server.
>
> We're replacing the system hardware because it is old and failing. I do
> not wish to install 7.1 on the replacement system - we've been upgrading
> all our Linux hosts to Fedora 2 (and now 3) and RHEL AS/WS 3.
>
> While I could rename the current server and continue to run it to provide
> squirrelmail access only, I'd rather retire it; it is old and prone to
> hardware failures, and I really want to have no older, unsupported OSs
> running.
>
> While I'd like to run the latest version, it might be better to use the
> version that comes with RHEL AS-3 (1.2.11-1). Right now, neither 1.2.6-1
> nor 1.4.2-3 work, but fail in different ways.
>
> Any pointers, suggestions or help would be greatly appreciated.
php recommended configuration is to disable display_errors and set
error_reporting to E_ALL. If you have such configuration - check
webserver's logs or enable php display_errors.
SquirrelMail recommends creating configuration file with conf.pl utility.
Don't edit it manually unless you understand what you are doing.
Check php mbstring.func_overload setting. If your distribution enabled it,
you might have to disable it for squirrelmail.
--
Tomas
-------------------------------------------------------
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-users mailing list
Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: [EMAIL PROTECTED]
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
