In the properties screen, you will see
{urn:ietf:params:xml:ns:caldav}calendar-home-set
/begenda/dav/00000000-0000-0000-0000-000000000000 (the number is unique to each account)
This will sync all the calendars in your GMX account.
One small problem with time zones. You can create an all day event, no problem. If you create a timed event and set the zone to UTC (nothing else) it works fine. If you leave the Time Zone as your local as set in Windows, or choose any other zone, you get the following error:
Also the properties section looks a little bit different:
I could find the proper link name only at this placew {DAV:}owner
/begenda/dav/users/00000000-0000-0000-0000-000000000000
time zones:
I can confirm that creating a timed event and setting the zone to UTC only it is possible to sync an event.
Yes, I think there is a slight difference in the implementation between the different domains, so gmx.com, gmx.de, gmx.at etc may all be slightly different.
It took me a while to figure out because most of what is on the Internet deals with the gmx.net/gmx.de accounts.
With the latest version of eM Client, 7.1.32088, Automatic Setup of accounts for GMX now adds all its services: Mail, CalDAV and CardDAV at one time. These work successfully.
I run 7.1.32088.0 Free on Windows 10. I can confirm that it does automatically set up the calendars from GMX. But, I still get the same error (“forbidden”) as shown by Gary Curtin, regardless of whether I change the local time zone to plain UTC or not.