Hello

Am 15.01.2018 um 13:55 schrieb Tobias Brunner ([email protected]):
>> We're having no issues whatsoever with several SFOS devices. Autodetection 
>> works too. In our settings, we use https://sogo.example.com as 'server 
>> address' with '/SOGo/dav/<USER>/Calendar' and '/SOGo/dav/<USER>/Contacts' 
>> for 
>> CalDAV and CardDAV paths.
> 
> Thanks. I've tried it again this way and now Calendars are detected
> properly. I don't know what I did wrong when trying it few days ago.
> 
>> We're not using full email addresses as usernames; thus this might have 
>> something to do with it... Did you try to use %40 instead of @ already?
> 
> @ works...
> 
> The only thing now: Umlauts are not displayed properly. A "ü" f.e. is
> displayed as &#252; on SFOS. Any idea how to solve this?
> 

As you only get one byte displayed for that umlaut, your original
content seems to be in an ISO character set, but it should be in UTF-8.

Could you check that, by creating a new event with umlaut via SOGo web
frontend?


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to