View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006236SOGoActiveSyncpublic2026-08-11 07:132026-08-22 17:10
Reportermikal Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformAppleOSiOSOS Version26.5.2
Product Version5.12.9 
Summary0006236: Support structured calendar locations for iOS
Description

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
Additional Information

SOGo has confirmed that ActiveSync will be maintained in SOGo 6 because of mobile-client compatibility:
https://www.sogo.nu/support/faq/sogo6-activesync.html
This request is therefore particularly relevant to the continued iOS ActiveSync experience.

Tagsactive sync, calendar, eas, iOS, mailcow

Activities

mikal

mikal

2026-08-22 17:10

reporter   ~0018530

I would like to clarify the expected behavior and suggest some measurable acceptance criteria.
The main objective is structured-location round-trip support and Apple Maps integration, rather than necessarily controlling the autocomplete UI shown by Apple Calendar while the user is typing. That autocomplete behavior may be client-specific.
Suggested test cases:

  1. Create an event on iOS using a recognized place or address.
  2. Synchronize it through SOGo using ActiveSync.
  3. Verify that the structured location survives an iOS → SOGo → iOS round trip, including the address components, coordinates and LocationUri where supplied.
  4. Verify that an event received from SOGo is recognized by iOS as a map location rather than only as plain text.
    It would also be useful to inspect the OPTIONS response or SOGo ActiveSync logs to confirm which EAS version is negotiated with the iPhone. Structured AirSyncBase:Location was introduced with EAS 16.0, so if SOGo currently advertises only EAS 14.1, version negotiation is probably part of the required implementation.
    Possible acceptance criteria:
    • SOGo advertises and negotiates an EAS version supporting AirSyncBase:Location.
    • Structured location data received from an EAS client is preserved in the corresponding calendar object.
    • Available iCalendar location, address and geographic data is mapped to the EAS structured-location fields.
    • Missing coordinates or address components do not prevent synchronization.
    • The structured data survives synchronization in both directions without being reduced to plain text.
      This distinction should make it possible to test the server-side functionality independently of Apple Calendar’s autocomplete behavior.

Issue History

Date Modified Username Field Change
2026-08-11 07:13 mikal New Issue
2026-08-11 07:13 mikal Tag Attached: active sync
2026-08-11 07:13 mikal Tag Attached: calendar
2026-08-11 07:13 mikal Tag Attached: eas
2026-08-11 07:13 mikal Tag Attached: iOS
2026-08-11 07:13 mikal Tag Attached: mailcow
2026-08-22 17:10 mikal Note Added: 0018530