Feature Request: Own mailaddress not for foreing calendars

[c-schwamborn]

Subscribing to any calendars, even the ones owned by someone else, which may also be write protected, results in calendars linked to ones own mailaddress. This results in a quite strange behavior regarding invitations withing Thunderbird. Maybe TBSync should not configure Mailaddresses at all in subscribed calendars in the first place and let the user configure this afterwards. Usually the number of calendars, linked to a mailaddress is rather small and more specific addresses for each calendar, not always the same primary standard ad.dress.

[vsessink]

I'm not sure feature request is the right category here - as current behaviour results in a bad - if not unusable - user experience.

The bug report is a bit convoluted because you need so many steps to actually see it. But in simple terms, the bug goes like this:

1. have a Caldav calendar, for example on Owncloud; your colleagues share their calendar with you
2. you have used TbSync to setup your calendar in Thunderbird
3. now one of your colleagues invites you to an event: they make a new event in their calendar, click on invite attendees and enters your mail address.

What actually happens is:

• your calendar synchronizes with the server and your colleague's event shows up in their calendar (good)
• you get an e-mail in Thunderbird, telling This message contains an event that has already been processed. (bad)
• ... which in turn results in your presence for the event is unknown and will stay that way (because no method of responding)
• the event never shows up in your own calendar and you won't get noticed should you want to

What should happen is:

• your calendar synchronizes with the server and your colleague's event shows up in their calendar (good)
• you get an e-mail in Thunderbird, telling This message contains an event that you have not yet responded to. [Accept] [Tentative] [Decline] [More]
• you can click any of these buttons to respond to your colleague
• event shows up in your calendar

Analysis

Now to know why this happens, you need to know that:

• a calendar that has your own e-mail address' identity set in imip.identity.key is considered your own agenda.
• a calendar that does not have any id setup, is considered to have id1 (your first mail address) as identity

Now TbSync does not set a value for imip.identity.key. Thus, all agendas are seen as having id1 for identity, i.e. being your own agendas.

Thus, your colleagues' invitation has already processed - i.e. already is in one of "your" agendas.