0004614: ActiveSync dispatcher Settings -> UserInformation -> Get response unimplemented - SOGo | BTS

ID	Project	Category	View Status	Date Submitted	Last Update

0004614	SOGo	ActiveSync	public	2018-12-03 10:21	2018-12-20 18:36

Reporter	pdf	Assigned To	ludovic
Priority	normal	Severity	feature	Reproducibility	always
Status	new	Resolution	fixed
Platform	[Server] Linux	OS	Ubuntu	OS Version	16.04 LTS
Product Version	4.0.4

Summary	0004614: ActiveSync dispatcher Settings -> UserInformation -> Get response unimplemented
Description	Support for retrieving a user's email addresses/aliases via EAS is not implemented, per the docs a Settings/UserInformation/Get request should return a UserInformation element containing the user's email addresses, however support appears to be unimplemented in the dispatcher.
Steps To Reproduce	When an EAS client performs a POST with the (binary) content: `<Settings> <UserInformation> <Get/> </UserInformation> </Settings>` It expects to receive a list of the user's email addresses, however SOGo simply returns the following, omitting the requested element: `<Settings> <Status> '1' </Status> </Settings>`
Tags	No tags attached.

pdf 2018-12-03 10:23 reporter ~0013207	Possibly related to [0004604]

pdf 2018-12-03 11:30 reporter	eas-userinformation-current.xml (1,317 bytes) <!-- Protocol version >= v14.1 --> <Settings> <Status> 1 </Status> <UserInformation> <Get> <Accounts> <Account> <AccountId/> <!-- [string] account identifier (optional) --> <AccountName/> <!-- [string] account human-friendly name (optional) --> <UserDisplayName/> <!-- [string] name field for the user (optional) --> <SendDisabled/> <!-- [bool] set based on whether the user has send permission for this account (optional) --> <EmailAddresses> <!-- [container] list of users email addresses (optional) --> <PrimarySmtpAddress> <!-- [string] primary mail field for the user (optional) --> users_primary@email.address.com </PrimarySmtpAddress> <SMTPAddress> <!-- [string] mail field for the user (required: 1 or more) --> users_primary@email.address.com </SMTPAddress> <SMTPAddress> <!-- [string] mail field for the user (required: 1 or more) --> users_alternate@email.address.com </SMTPAddress> <SMTPAddress> <!-- [string] mail field for the user (required: 1 or more) --> users_other_alternate@email.address.com </SMTPAddress> </EmailAddresses> </Account> </Accounts> </Get> </UserInformation> </Settings> eas-userinformation-current.xml (1,317 bytes)

pdf 2018-12-03 11:30 reporter	eas-userinformation-old.xml (712 bytes) <!-- Protocol version >= v12.0, <= v14.0 --> <Settings> <Status> 1 </Status> <UserInformation> <Get> <EmailAddresses> <!-- [container] list of users email addresses (optional) --> <SMTPAddress> <!-- [string] mail field for the user (required: 1 or more) --> users_primary@email.address.com </SMTPAddress> <SMTPAddress> <!-- [string] mail field for the user (required: 1 or more) --> users_alternate@email.address.com </SMTPAddress> <SMTPAddress> <!-- [string] mail field for the user (required: 1 or more) --> users_other_alternate@email.address.com </SMTPAddress> </EmailAddresses> </Get> </UserInformation> </Settings> eas-userinformation-old.xml (712 bytes)

pdf 2018-12-03 11:33 reporter ~0013209	From my reading of the docs, the responses should look something like the attached XML structures (current.xml for recent protocol versions, and old.xml for previous versions, if SOGo bothers to have any support forthose). Ideally we'd populate the additional optional fields too, where we have the relevant data, for best client feature coverage.

Date Modified	Username	Field	Change
2018-12-03 10:21	pdf	New Issue
2018-12-03 10:23	pdf	Note Added: 0013207
2018-12-03 11:30	pdf	File Added: eas-userinformation-current.xml
2018-12-03 11:30	pdf	File Added: eas-userinformation-old.xml
2018-12-03 11:33	pdf	Note Added: 0013209
2018-12-20 18:36	ludovic	Changeset attached	=> sogo master af70306d
2018-12-20 18:36	ludovic	Assigned To	=> ludovic
2018-12-20 18:36	ludovic	Resolution	open => fixed