-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add calendar and address book sync parameters for CalDAV and CardDAV #20
Comments
I need help here. Can people please give me the CardDAV and CalDAV URLs for all ISPs that support them? |
@jobisoft Could you please give me the CardDAV and CalDAV URLs, for all ISPs that support these protocols, based on your experience with TbSync? |
@darktrojan Do you know a list of CardDAV and CalDAV URLs, for all ISPs that support these protocols? |
I have none, I use RFC 6764 discovery |
I do not. |
Thanks to both of you for the swift answer. |
This should be wontfix. There's RFC 6764 for it, which is what Thunderbird uses. It's the standard way to do the discovery - no point in adding a non-standard way for it. |
@benbucksch I added some in #129 , and there will be another pull request from me containing CalDAV & CardDAV urls for Yahoo Mail & Mail.com Also , I might upload some CalDAV & CardDAV URLs for some others domains, if I am able to find those URLs. But it would be better if those who published the original ispdb files contribute. |
UPDATE: Added CalDAV & CardDAV settings for , , , , , & @ #131 |
The latest official spec of the config file format supports adding CalDAV and CardDAV setup parameters, so that a client can automatically configure the calendard and address book sync.
This adds the server URLs for the major ISPs that provide CalDAV and CardDAV services for their freemail users.
Note: In order to add it to the configuration, all email users of the ISP should have access to these features. We should only add it, if most of the users of that ISP have access to the CalDAV and CardDAV services.
The text was updated successfully, but these errors were encountered: