What mccs gives your users

Address, device, app, then a step-by-step guide with copyable values.

Outlook (new and classic), CalDAV Synchronizer, Thunderbird, Apple Mail, Gmail, Samsung apps and DAVx5.

A one-tap Apple configuration profile (.mobileconfig, without password) and Thunderbird autoconfig.

On a computer, a QR code lets the customer continue on a phone. It is generated locally in the browser.

Name, logo, accent colour, servers and support contact.

mdaemon (default, MDaemon WebDAV paths and shared folders) or generic (standard .well-known discovery), with URL templates to override either.

An internal /support page (HTTP Basic) that builds a link for one customer, with QR code, PNG or SVG export and a ready-made email or SMS text.

It never asks for a password, stores nothing and sets no cookies. Users type their password only in their own mail client.

Nothing is stored on disk, so there is nothing to back up except your .env.

A strict Content-Security-Policy, a read-only filesystem, all capabilities dropped and no third-party requests.

The interface and the guides are in French. Translating means editing public/js/guides.js, public/js/app.js and the HTML files by hand.

The profile is not signed. iOS and macOS show "Not signed" when installing it, and the server does not sign it for you.

No image is published, and there are no automated tests and no CI yet. Docker builds it from the repository.

The guides were written for one MDaemon instance, and the generic preset has had less use.

It does not check that your mail server answers. The settings are only as right as your configuration.

The guides describe third-party apps as they look today. A new version of Outlook or Thunderbird can make a step out of date.

The /support lock-out keys on the CF-Connecting-IP header when present, so only expose the app behind a proxy that controls it.