Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Thunderbird Version 78 - CalDav calender not working with error PROPFIND "405 Method Not Allowed".

  • 5 réponses
  • 1 a ce problème
  • 1 vue
  • Dernière réponse par rde

more options

Since the update to Thunderbird 78 my CalDav calender cannot be activated anymore. It appears grey in the calendar list. I checked on multiple computers and my colleagues have the same problem. Is there a way to fix this?

Since the update to Thunderbird 78 my CalDav calender cannot be activated anymore. It appears grey in the calendar list. I checked on multiple computers and my colleagues have the same problem. Is there a way to fix this?

Modifié le par Wayne Mery

Solution choisie

It turns out that it was indeed related do the UserAgent being rejected by the CalDav-Server after the update to version 78. In that version Lightning is part of Thunderbird and not shown in the user-agent string.

A workaround would be to manually override the general.useragent.locale string in settings with an old one.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (5)

more options

Hi, It didn't worked for me either and I have switched back to 6.8 version. You should wait till the authors update that add-on or you might switch back to an old version.

more options

The error-message ist PROPFIND "405 Method Not Allowed". Is it possible that it has something to do with the user agent that differes in version 78 from version 68 and therefore the client ist no longer accepted?

more options

Solution choisie

It turns out that it was indeed related do the UserAgent being rejected by the CalDav-Server after the update to version 78. In that version Lightning is part of Thunderbird and not shown in the user-agent string.

A workaround would be to manually override the general.useragent.locale string in settings with an old one.

more options

actually that's not a solution. but since your topic is marked solved i opened a new topic for the problem: https://support.mozilla.org/en-US/questions/1323344