0002576: Lightning not using the right Mail addresses - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0002576	SOGo	Backend Calendar	public	2014-01-15 09:26	2014-02-04 00:05

Reporter	tschaaf	Assigned To	ludovic
Priority	high	Severity	block	Reproducibility	always
Status	closed	Resolution	no change required
Platform	Microsoft	OS	Windows	OS Version	Vista

Summary	0002576: Lightning not using the right Mail addresses
Description	We're using SOGo in our company with LDAP for authentication and integrated in Thunderbird Lightning. We have a mixed environment and while we are not encounter any issues with Linux users, we have issues with Windows 7. Our user have login names like this "jdoe" and mail addresses like "j.doe@domain.com" When calendars are imported into Thunderbird Lightning as CalDAV calendars and a new event is generated in Lightning the event is generated with the wrong mail address "jdoe@domain.com" Which means the DOT is missing and it seems to use the user login to create the Mail address. This issue does not happen on the web calendar either. It's also present in 2.1.1b
Steps To Reproduce	Create a new event in Lightning Click on add attendees Check your own mail address in upper left corner of the window -> misses the point in mail address
Additional Information	Server: Debian Wheezy MySQL Backend-DB LDAP for user authentication Tested with current version of Thunderbird 24 and Lightning 2.6.4 as well as Thunderbird 17 ESR and Lightning 1.9.1 With and without SOGo Connector. All with the same result.
Tags	No tags attached.

Date Modified	Username	Field	Change
2014-01-15 09:26	tschaaf	New Issue
2014-01-16 14:46	Christian Mack	Note Added: 0006406
2014-01-16 16:08	tschaaf	Note Added: 0006407
2014-02-04 00:05	ludovic	Status	new => closed
2014-02-04 00:05	ludovic	Assigned To	=> ludovic
2014-02-04 00:05	ludovic	Resolution	open => no change required

Christian Mack 2014-01-16 14:46 developer ~0006406	Did you set the following option in sogo.conf? SOGoHideSystemEMail YES

tschaaf 2014-01-16 16:08 reporter ~0006407	It seems that was the issue with this settings it looks like it's working now. Thanks for the quick response.