The problem I am experiencing is that whenever I enable the squirrel_logger
Logging plugin then the SM web app blanks the web page and becomes
non-responsive when a user opens a new or logs out of an existing SM session.
Server version: Apache/2.2.15 (Unix) Server built: Jul 23 2014 14:17:29
allow from all
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
. . .
This script will try to check some aspects of your SquirrelMail configuration
and point you to errors whereever it can find them. You need to go run conf.pl
in the config/ directory first before you run this script.
SquirrelMail version: 1.4.22-4.el6
Config file version: 1.4.0
Config file last modified: 08 September 2014 17:09:38
Checking PHP configuration...
PHP version 5.3.3 OK.
Running as N/A(N/A) / N/A(N/A)
variables_order OK: GPCS.
PHP extensions OK. Dynamic loading is disabled.
ERROR: You have configured PHP not to allow short tags
(short_open_tag=off). This shouldn't be a problem with SquirrelMail or any
plugin coded coded according to the SquirrelMail Coding Guidelines, but if
you experience problems with PHP code being displayed in some of the pages
and changing setting to "on" solves the problem, please file a bug report
against the failing plugin. The correct contact information is most likely
to be found in the plugin documentation.
Data dir OK.
Attachment dir OK.
Default language OK.
Base URL detected as: https://webmail.harte-lyne.ca/src (location base
Checking outgoing mail service....
SMTP server OK (220 inet08.hamilton.harte-lyne.ca ESMTP Postfix)
Checking IMAP service....
IMAP server ready (* OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=LOGIN
AUTH=PLAIN SASL-IR COMPRESS=DEFLATE] inet07.hamilton.harte-lyne.ca Cyrus
IMAP v2.3.16-Fedora-RPM-2.3.16-6.el6_2.5 server ready)
Capabilities: * CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=LOGIN
AUTH=PLAIN SASL-IR COMPRESS=DEFLATE ACL RIGHTS=kxte QUOTA
MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN
MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT
THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE LISTEXT
LIST-SUBSCRIBED X-NETSCAPE URLAUTH
Checking internationalization (i18n) settings...
gettext - Gettext functions are available. On some systems you must have
appropriate system locales compiled.
mbstring - Mbstring functions are available.
recode - Recode functions are unavailable.
iconv - Iconv functions are available.
timezone - Webmail users can change their time zone settings.
Checking database functions...
not using database functionality.
Congratulations, your SquirrelMail setup looks fine to me!
On 9/8/14, James B. Byrne <[hidden email]> wrote:
> The problem I am experiencing is that whenever I enable the squirrel_logger
> Logging plugin then the SM web app blanks the web page and becomes
> non-responsive when a user opens a new or logs out of an existing SM
On Tue, September 9, 2014 03:08, Paul Lesniewski wrote:
> On 9/8/14, James B. Byrne <[hidden email]> wrote:
>> The problem I am experiencing is that whenever I enable the squirrel_logger
>> Logging plugin then the SM web app blanks the web page and becomes
>> non-responsive when a user opens a new or logs out of an existing SM
> This is a FAQ in the list archives. See:
Adding the error reporting flags to /etc/php.ini produces the following error
Running the configtest script results in this error as well:
PHP Warning: date(): It is not safe to rely on the system's timezone
settings. You are *required* to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those methods
and you are still getting this warning, you most likely misspelled the
timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead
in /usr/share/squirrelmail/src/configtest.php on line 80
However, if the logging plugin is enabled and I try and login then the page
goes blank and nothing whatsoever is logged in any file that I can detect.
Other than listing the logging plugin as well the debugging plugin yields the
following output whether the logging plugin is enabled or not:
Notice: A session had already been started - ignoring session_start() in
/usr/share/squirrelmail/functions/global.php on line 473
> PHP Warning: date(): It is not safe to rely on the system's timezone
> settings. You are *required* to use the date.timezone setting or the
> date_default_timezone_set() function. In case you used any of those methods
> and you are still getting this warning, you most likely misspelled the
> timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST'
> in /usr/share/squirrelmail/src/configtest.php on line 80
This is self-explanatory; otherwise Google is your friend.
> However, if the logging plugin is enabled and I try and login then the page
> goes blank and nothing whatsoever is logged in any file that I can detect.
Things don't go blank without an error somewhere. Increase your
logging verbosity? Go back to default configuration file for the
plugin? Keep digging.
On Tue, September 9, 2014 13:22, Paul Lesniewski wrote:
> Things don't go blank without an error somewhere. Increase your
> logging verbosity? Go back to default configuration file for the
> plugin? Keep digging.
The problem was, as you suggested, with the config.php file. The statement
$sl_dateformat = 'M j H:i:s'; had a trailing ":" after the terminal ";"
character. Everything seems to work now.
I have downloaded the add_address replacement for the abook_take plugin and
will get around to testing that once the fail2ban configuration is working.
I have also added the default timezone to /etc/php.ini.
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:[hidden email] Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
Couldn't an easy command like "php -l config.php" be added to the configtest? I have just tested it for a trailing colon like it happened and it will complain. Should someone add a bug or request or patch for this?
Further, it will complain about many other simple mistakes we could probably miss when quickly skimming the config.php file. And James did, from the beginning, what I would do: "Does configtest complains? No? So the problem is not on configuration". Which is not what we've found.