When using SOGo Calendar through Exchange ActiveSync on iOS, calendar event locations are synchronized as plain text.
As a result, Apple Calendar does not provide its normal location/map suggestions when entering a location in an event.
The same iOS device provides location suggestions correctly when using an iCloud calendar.
Since ActiveSync is being retained in SOGo 6 specifically to provide native mobile-client compatibility, improved calendar-location support for iOS would be particularly useful.
EAS protocol details:
The EAS AirSyncBase namespace defines structured location properties beginning with EAS 16.0.
Relevant elements include:
- AirSyncBase:Location
- AirSyncBase:Street
- AirSyncBase:City
- AirSyncBase:State
- AirSyncBase:Country
- AirSyncBase:PostalCode
- AirSyncBase:Latitude
- AirSyncBase:Longitude
- AirSyncBase:Accuracy
- AirSyncBase:Altitude
- AirSyncBase:AltitudeAccuracy
- AirSyncBase:LocationUri
Microsoft protocol specification:
https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-aswbxml/aa548cbc-b15f-4dc1-8bda-82b35d9d41c4
Current behavior:
For an event containing, for example:
Location: Oslo S, Jernbanetorget 1, 0154 Oslo
SOGo/EAS appears to expose the location primarily as a conventional text location.
Apple Calendar consequently treats it as text rather than as a structured location that can be resolved through Apple Maps.
Requested behavior:
Could SOGo’s ActiveSync implementation expose the structured AirSyncBase:Location properties when synchronizing calendar events?
At minimum, it would be useful to investigate mapping SOGo/iCalendar location data to:
Location
Street
City
State
Country
PostalCode
Latitude
Longitude
LocationUri
Where coordinates are not available in the calendar data, the server could potentially provide the textual address fields without latitude/longitude, or leave those fields empty.
EAS version negotiation:
It would also be useful to clarify whether iOS requires the server to advertise/negotiate EAS 16.x before it will consume the structured AirSyncBase:Location elements.
If so, could the relevant EAS 16.x capability/version negotiation be implemented independently of the rest of the EAS 16 feature set?
In other words, this request does not necessarily require a complete EAS 16 implementation if the structured Location functionality can be added independently.
Expected result on iOS:
When creating or editing an event in an SOGo calendar on iOS, entering an address or place in the Location field should provide the native Apple Calendar location suggestions/map integration, in the same way as an iCloud calendar.
Environment:
- SOGo 5.x / planned SOGo 6
- Mailcow
- Exchange ActiveSync
- Apple Calendar on iOS
| 