I am using Thunderbird 45.8.0 (current) on Win-10.
There are 2 different calendars on 2 separate accounts on the same server (provider: 2 free mail & calendar acocunts on web.de), which a friend and I would like to share and incorporate in Thunderbird. Simple "merging" into one calendar is not an option, since we both share this calendar also with other (not completely overlapping) people.
Incorporating either calendar works nicely, but the second one does not work in parallel (no matter which is first/second; error: the calendar entry is shown, but pale and not working, when clicking properties - "switch this calendar on", this does not cheange the status).
To me, it seems that the problem might be (I am not sure), that Thunderbird cannot distinguish the 2 calendars because they are on the same provider, address ist: https://firstname.lastname@example.org/calendar (as per help on https://hilfe.web.de/kalender/synchronisieren/thunderbird.html).
I found and tried the following suggestions (https://sys4.de/en/blog/2014/07/11/multiple-caldav-calendars-thunderbird-lightning-auth-problem/):
- "Adding 'username@' before the URL should also work, e.g. http(s)://username@myserver/owncloud/..." -> does not work (address not accepted, same with username:password@...) (might I need to place username:password somewhere els in this address (tried, but did not help so gfar)
- set calendar.network.multirealm to TRUE -> still does not work.
In Thunderbird password manager, the two (different) usernames and (different) passwords for the zwo calendars are correctly included (and work if either calendar is used separately).
Is there any solution to handle 2 calendars on the same provider/server? We would prefer
- stay on the same existing providers if possible, otherwise
- a solution that does not simply rely on using different providers for each calendar, since we might become more people/calendars and there is a limited number of trusted providers.
Update 2017-03-12: I found these two bug reports. They are quite old, but seem to be difficult (13 years!) and still unsolved - I'd be happy if someone could disprove this or come up with a workaround...
reported 5 yr ago, modified 7 months ago: https://bugzilla.mozilla.org/show_bug.cgi?id=799184
reported 13 yr ago, modified 3 yr ago: https://bugzilla.mozilla.org/show_bug.cgi?id=247486