Hi Christian,
I have the similar behavior with CalDAV.
Most probably that is an issue with CalDAV and TB/Lightning but I can
not confirm it now.
If I use the following example:
c_uid = c_name = user1
mail = [email protected]
TB/Lightning creates email [email protected] as organizer. So, I have
decided to use full email as c_uid = c_name
As I can see from the docs, it say that:
Parameter used to control if SOGo should hideor not the system email
address(UIDFieldName@SOGoMailDomain). This iscurrently limited to CalDAV
(calendar-useraddress-set).Defaults to NO when unset.
Could we use safely email address as c_uid and c_name? Or it is also
recommended to put additionally SOGoHideSystemEMail to YES?
Thanks,
Igor
Christian Mack wrote, On 04/10/2012 11:18:
Hello Bruno Lingner
On 2012-10-02 14:44, Bruno Lingner (Hugo) wrote:
hi list
I fond a strage misbehaviour with iCal on sogo. iCal sometimes creates
meetings where the ORGANIZER is like [email protected] instead of
[email protected] which is the correct email address in our
company. this is ok for most of the meetings, but it makes accepting the
meetings impossible for a meeting that's been created by another user
with read/write rights on the calendar in question (iCal then thinks
that the meeting doesn't belong to the calendar owner).
anyone has seen this behaviour?
I've seen it happen in ical 4 (OSX 10.6.x) and 6 (OSX 10.8.x).
would a sogo bug report help?
In order to prevent this to happen, set option SOGoHideSystemEMail to YES.
Kind regards,
Christian Mack
--
[email protected]
https://inverse.ca/sogo/lists
