The ORGANIZER is managed by Android (which uses the account name when no organizer has been set) and/or the calendar app. DAVdroid only takes the values which it receives from the calendar provider, see the image at https://www.davdroid.com/faq/system-integration/
You could create multiple accounts with various account names (= ORGANIZERS) and then use the calendars accordingly.
I wanted ro report a Problem with adding an account which is hosted on my own Baikal server. This may be just a server issue, but I suggest you may update the documentation if you find it appropriate.
Officially the Base-URL stated in your FAQ is /dav.php/ (e.g. https://server.example/baikal/dav.php/)(https://www.davdroid.com/tested-with/baikal/)
It only finds my account however when I type the principal URL https://dav.pascalpieper.de/dav.php/principals/NAME/.
When looking at the error log, it actually finds the principals path even when leaving out the /dav.php/-part, but somehow reports an internal server error upon request of that site. If I type directly the principal-URL, it finds the services of my user and succeeds.
DavDroid Error log: https://paste.fedoraproject.org/paste/OWimfyX2IAqbVcfdoj0P~Q
Webserver log: https://paste.fedoraproject.org/paste/SJTfzTIz1jHzU4gGPA7img
PS.: DavDroid is a great app and I enjoy using it otherwise.
What about leaving quering of the DNS to the OS, but doing the validation of the answers in the application?
When openssh is linked with libldns is does DNSSEC validatation (evaluation of the SSHPF records). So has openDmarc to be linked with libunbound to do DNSSEC validation.
If an application wants nowadays to do DANE/DNSSEC is has to use the right libraries.
sorry for digging up this old topic, but I just stumbled over this problem myself.
Can someone tell me if contacting the calendar developers lead to any calendar app handling this correctly with EXDATE now. I already tried aCalendar hoping that they might have fixed this after two years, but it doesn't seam like it.
Does anyone have any tips on this?
I think the problem is Apache2 on my PI does not allow direct IPs to connect and is namebased : https://superuser.com/questions/875941/accessing-a-website-through-its-ip-address-instead-of-hostname#875943
I run some other things on my PI.
I cannot access the public IP from a browser either but this is not a problem as my Duckdns.org FQDN works fine there.
When I manually sync with Davdroid it works fine, it is only the automated syncs that fail, there are notifications saying they failed.
If the automatic syncing was forced to use the namebase / FQDN; https://XXX.duckdns.org/nextcloud instead of resolving it to XX.XXX.XX.XX:443 I'm sure it would successfully work as the main activity does.
Please can you look into this.
I'm french (English is difficult) and write here
If you have ideas....
I see this page :
In advance thank you
The iCalendar is invalid:
A calendar object on a CalDAV server must not have a METHOD property. (Doesn't matter here)
PRIORITY must be an integer between 0 and 9
Your iCalendar contains PRIORITY:80, which is not valid and cannot be synchronized. Please fix your iCalendars.
Does that help?
@devvv4ever I solved it. My DAVDroid account was named the same as my email ID on one occasion and "DAVDroid" on another occasion. I just changed it to just "Droid" and synced it again. Everything has started working now. Thank you.
@rfc2822 Ich werde mich mal an den eM Client Support wenden. Mal sehen, was die sagen.
Melde mich wieder, wenn ich eine Antwort habe. Sollte dabei nichts rauskommen, kann ich ja mal noch die Debug-Logs, etc schicken.
Erstmal vielen Dank!
@rfc2822: "I think the only solution is to give DAVdroid all required permissions and to turn off functions that block DAVdroid."
That's for sure. My request was about DAVdroid beeing able to defect that permissions are missing and warn. But when implementation of "privacy protection" is like you say, I think it's the exact intention of that feature that the app does not know there is anything blocked.
So please close this thread.
Can you please provide
steps to reproduce,
DAVdroid debug info (DAVdroid / Settings / Debug info) and
if possible, verbose DAVdroid logs etc as described in [READ BEFORE POSTING] What's required to diagnose a problem?
We'd have to be able to reproduce the problem to have a look at that.