Neruna Join the beta

Guides · For admins

Finding calendars and contacts automatically.

Neruna looks for CalDAV and CardDAV itself – provided your server says where they are. Usually two redirects are enough.

How Neruna searches

  1. First in the autoconfig file (<calendar> and <addressBook>, see “Automatic setup”).

  2. Otherwise Neruna asks https://domain/.well-known/caldav and …/carddav – first on the email address's domain, then on the IMAP server. A redirect, a login challenge (401) or a DAV answer (207) is enough.

  3. Neruna then finds the individual calendars and address books itself – including those others have shared with you. You never have to type the path of a single calendar.

Setting up the redirect

On the web server offering DAV, two permanent redirects to the DAV path – here using Nextcloud as an example:

nginx

location = /.well-known/caldav  { return 301 /remote.php/dav/; }
location = /.well-known/carddav { return 301 /remote.php/dav/; }

Apache

Redirect 301 /.well-known/caldav  /remote.php/dav/
Redirect 301 /.well-known/carddav /remote.php/dav/

Common targets: Nextcloud /remote.php/dav/, SOGo /SOGo/dav/, Radicale the root /. Nextcloud already ships the redirect for Apache.

To another server? If the redirect points to another host name (e.g. from example.com to dav.example.net), Neruna asks during setup, shows the exact target and only sends the password there once you agree. If the target is the IMAP server itself, there is no question. Neruna never uses redirects to unencrypted http://.

Testing

Without logging in, just check the redirect:

curl -si -X PROPFIND -H "Depth: 0" https://mail.example.com/.well-known/caldav | head -3

HTTP/2 301
location: https://mail.example.com/remote.php/dav/

301/302 with location, 401 or 207 are fine. 404 means Neruna finds nothing here.