A Collegue tested it with accepting invites directly in iCal 4 and that
worked!
ill try this with iCal 5 after the lunch - tried it over Mail (doesnt
work) - maybe it works when i directly
accept invites in iCal 5. So iCal 4 seems to work great here in my
environment!
Am 4/17/12 12:43 PM, schrieb Martin Seener:
Hi,
@Burkhart
i can confirm this, set up a meeting at 1 today and added this to my
iCloud Calendar via Apple Mail by double-clicking the attached .ics
whereas it was then added one hour later again :(
i had Time Zone Support disabled and enabled (set to "Germany Time") -
the same problem.
maybe sogo misses to send correct .ics files (with correct time zone??)
Am 4/17/12 12:19 PM, schrieb Burkart Orlowski | Onlinehelp24:
Hi,
@Martin: in my Ubuntu 10.04 setup, I loaded the module substitute
"sudo a2enmod substitute" and added
RequestHeader unset Accept-Encoding
AddOutputFilterByType SUBSTITUTE text/calendar text/xml
Substitute
's|^RRULE:([A-Z].+[A-Za-z0-9]);?FREQ=([A-Za-z]*);?(.*)$|RRULE:FREQ=$2;$1$3|'
in the apache config file for DAV-SSL. After a restart of apache2,
memcached, sogo and a reload of the web interface everything worked
fine again.
But I just figured out that this solves only the problem when
creating new events in the SOGo web interface in your own calendar.
Invitations send via mail or through Thunderbird are still one hour
late in iCal.
Will there be a new release coming out solving these problems?
Thx, Burkart
On 17.04.2012, at 10:26, Martin Seener wrote:
Hi Christian,
we also have a lot of old one time and recurring events in wrong
timezone.
can you tell me how i can correct them?
Martin
Am 4/17/12 10:03 AM, schrieb Christian Mack:
Hello Burkart Orlowski
On 2012-04-16 11:11, Burkart Orlowski | Onlinehelp24 wrote:
...I am still having the issue that when saving an event in the
SOGo web interface the iCal event is shown +1 hour later (as
Western European Time instead of Middle European Time).
mod_substitute is loaded and the output filter is added in the
DAV-SSL configuration. When I restart apache and SOGo there are no
error messages but the event issue is the same.
This work around doesn't fix already wrong events.
It only prevents new events getting a bad timezone by synchronization
with iCal.
You have to move the already bad ones back into your desired timezone
manually.
Kind regards,
Christian Mack
--
[email protected] <mailto:[email protected]>
https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists
