-
I believe this is a preference/package issue, rather than a SquirrelMail bug. Looking at the error, you somehow got "CET/1.0/no DST" set as your timezone in your user preferences. This shouldn't be possible with the standard SquirrelMail timezones we provide (you can see we've not changed it in over 6 years [...
2010-01-04 03:08:40 UTC in SquirrelMail
-
Thanks for your submission. We've applied a slightly modified fix to both stable, and devel branches. This should be available from SVN now.
2009-12-22 17:17:25 UTC in SquirrelMail
-
jangliss committed revision 13880 to the SquirrelMail SVN repository, changing 2 files.
2009-12-22 17:15:34 UTC in SquirrelMail
-
jangliss committed revision 13879 to the SquirrelMail SVN repository, changing 2 files.
2009-12-22 17:14:48 UTC in SquirrelMail
-
Plugin specific issues should be submitted to the plugin maintainer, rather than the SquirrelMail team, unless the plugin is maintained by us (newmail, fetchmail etc).
2009-11-22 17:31:03 UTC in SquirrelMail
-
I've recently gone through and fixed several bugs on the filters plugin. This may have resolved this issue already. Marking this bug as pending to auto-close if no response is sent. Please submit a note if you still see this issue occuring.
2009-11-22 17:28:39 UTC in SquirrelMail
-
jangliss committed revision 13874 to the SquirrelMail SVN repository, changing 2 files.
2009-11-22 16:19:52 UTC in SquirrelMail
-
Thanks for the report. I've fixed it a slightly different way, as this would introduce a redundant if statement. Changes committed to SVN.
2009-11-22 16:12:30 UTC in SquirrelMail
-
jangliss committed revision 13873 to the SquirrelMail SVN repository, changing 2 files.
2009-11-22 16:10:35 UTC in SquirrelMail
-
As an additional note, you could also try doing a full dump of the message being returned... Inside the if (DB::isError($res)) statement, you can do:
var_dump($res);.
2009-11-22 05:31:51 UTC in SquirrelMail
