Bug 350499 – www-apps/postfixadmin-2.3.2: Wrongly displays dates stored in a postgresql database

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Diane Gagne 2011-01-03 22:24:09 UTC]

With a working postgresql database, when the virtual list page is selected the error an error is displayed for each mail address and virtual address stored.  As well, the date 1969-12-31 17:00 is displayed as the last modified date for all the alias addresses.

Reproducible: Always

Steps to Reproduce:
1.Log into postfixadmin
2.select Virtual List
3.

Actual Results:  
The warning:

Warning: strtotime() [function.strtotime]: 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/Denver' for 'MST/-7.0/no DST' instead in /var/www/postfixadmin/htdocs/postfixadmin/list-virtual.php on line 186

Warning: date() [function.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/Denver' for 'MST/-7.0/no DST' instead in /var/www/postfixadmin/htdocs/postfixadmin/list-virtual.php on line 186

is displayed for each alias address listed.

Expected Results:  
There should be no warnings.

This is running php5.3, and postgresql 8.4.  In the postgresql database, the time is correctly displayed for all modified and created dates of the tables.  Switching back to postfixadmin 2.3 produces the same results.

[Comment 1 Peter Volkov (RETIRED) 2011-01-05 06:03:21 UTC]

To avoid warning do what what message tells to do: set date.timezone in php.ini. Will this fix the problem?

[Comment 2 Diane Gagne 2011-01-05 17:01:06 UTC]

This does remove the warnings problems, however the modified date is still set at 1969-12-31 17:00 for all mail aliases.  This includes a test alias I just created.  Email addresses do not have this problem, and a true date is stored in the database.

[Comment 3 Peter Volkov (RETIRED) 2011-04-30 19:19:16 UTC]

Do you have same issue with 2.3.3?

[Comment 4 Peter Volkov (RETIRED) 2011-04-30 19:20:38 UTC]

Ah well, this should be fixed. At least ChangeLog has the following entry:

  - list-virtual: fix displaying of 'modified' column for aliases when using
        postgres

Please, test it and reopen bug if this is still an issue for you.

[Comment 5 Diane 2011-05-03 22:58:34 UTC]

It is working now