CiviCRM Community Forums (archive)

Seems this topic has been discussed several times. IMO, when a mailing is submitted to be processed "immediately", the server's time should be used and not the user's local time. Likewise, the user's local time should be translated into the server's time for scheduled mails.

I've been doing some testing from Australia. The server is in Houston. When the mail is submitted, it gets submitted with the user's local time and is not processed until the server catches up.

The time a mail is sent should be in the mail headers relative to UTC, so on the receiver's end it would be displayed with appropriate adjustment for the receiver's UTC offset - is that not happening?

One easier solution for now, is to let your server in Houston set the local timezone to Sydney and that should solve the issue. This can be done via the hook_civicrm_config, with something like:

    // set the timezone                                                                                                                     
    date_default_timezone_set('America/Los_Angeles');

The longer term solution would be for CiviCRM to be "timezone aware" with regard to all time operations. This is a bit more involved, and ideally should be "user specific" and all times in the DB are stored as UTC (and then converted as needed). Would be great if the DA developers could look into this issue and potentially fix it

lobo

If you could publish the use cases, I'd be interested - the org I work with also has administrators around the world.