According to the CalDAV standard, is server supposed to send all emails
or just primary?
I am trying to figure out where the problem resides. SOGo side or
Lightning side?
Thanks,
Igor
Igor Vitorac wrote, On 18/04/2013 16:22:
It seems that latest Lightning (1.9.1) has again problem with Invitee
email address. Or could it be SOGo (2.0.4b)?
I can remember that there was such problem in previous Lightning
versions.
- I have 2 emails defined in TB:
my_n...@example.be (this one is primary and defined as email in
Calendar properties)
my_n...@example.com
- I have both email defined in SOGo SQL user source, so SOGo is aware
of both.
- My SOGo is installed at sogo.example.com
- Email address defined in calendar properties in Lightning is
my_n...@example.be
Problem:
- When I create event and I want to invite somebody, I can see that my
address is displayed as my_n...@example.com (last email) in invitee list.
- When I receive email invitation from somebody else, Lightning will
respond again with wrong email my_n...@example.com (last one)
New test:
- Then I removed my_n...@example.com (last email) from my profile in
sogo user source, so only one has left my_n...@example.be. Cleared
memcached; started TB/Lightning and Lightning was showing correctly
email address (my_n...@example.be) !
So, seems that SOGo is sending both emails (my_n...@example.be and
my_n...@example.com ) to Lightning and Lightning is using only the
last one (for sending invitations and for responding to invitations).
These are very similar bugs that :
https://bugzilla.mozilla.org/show_bug.cgi?id=539916
https://bugzilla.mozilla.org/show_bug.cgi?id=540410
but seems that Lightning now displays always option to Accept/Decline
invitation, however behavior with invitee email address is back again.
Does anybody have the similar scenario?
Thanks,
Igor
--
users@sogo.nu
https://inverse.ca/sogo/lists
