A NOTE has been added to this issue. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=776 
====================================================================== 
Reported By:                dbakken
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   776
Category:                   IMAP daemon
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
target:                      
====================================================================== 
Date Submitted:             03-Mar-09 18:12 CET
Last Modified:              03-Mar-09 21:04 CET
====================================================================== 
Summary:                    INTERNALDATE is wrong time zone
Description: 
INTERNALDATE values returned by dbmail-imap are labeled with the wrong time
zone. Internal dates are stored in UTC. When displayed in IMAP,
INTERNALDATE is returned in UTC, but labeled as -0800. This confuses
clients like Mac Mail.app which use INTERNALDATE for the IMAP folder list.
====================================================================== 

---------------------------------------------------------------------- 
 (0002800) dbakken (reporter) - 03-Mar-09 19:54
 http://www.dbmail.org/mantis/view.php?id=776#c2800 
---------------------------------------------------------------------- 
The problem is that dbmail assumes MySQL is set to the same timezone as the
server. Dates are stored using the MySQL timezone but retrieved using the
server's system timezone. This would be fine if conversion was done, but
it isn't. 

---------------------------------------------------------------------- 
 (0002801) netvulture (developer) - 03-Mar-09 21:04
 http://www.dbmail.org/mantis/view.php?id=776#c2801 
---------------------------------------------------------------------- 
This issue was resolved in the 2.3.x branch with simply using the UTC +0000
timezone as the internal date is stored in the database as UTC when
inserted. I will look into making a patch for 2.2, but until then, as a
workaround you can set the dbmail server to UTC. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
03-Mar-09 18:12  dbakken        New Issue                                    
03-Mar-09 19:54  dbakken        Note Added: 0002800                          
03-Mar-09 21:04  netvulture     Note Added: 0002801                          
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Reply via email to