mail.langmail.me. Any client that speaks CalDAV can subscribe to them for two-way sync, so events stay consistent across every client — including the invitations your agent sends.
Before you start
Interactive sign-in for Langmail happens in the browser, so calendar clients authenticate with an app password instead of your account password — the same credential mail clients use. Open webmail, go to Settings → Security, and generate an app password. The secret is shown once, so copy it right away. One app password works for both mail and calendar; you can create one per device and revoke each independently from the same page.Clients discover your calendars automatically from your
you@langmail.me address — the _caldavs SRV record on the domain points them at mail.langmail.me, and RFC 6764 (/.well-known/caldav) does the rest — so you shouldn’t need a full calendar URL. Apple’s setup screens still show a Server field; entering mail.langmail.me there is all the discovery needs. If your client insists on a complete URL, your default calendar is https://mail.langmail.me/dav/cal/you%40langmail.me/default/ — replace you@langmail.me with your own address, percent-encoding the @ as %40. (The parent /dav/cal/you%40langmail.me/ holds all your calendars; each additional one has its own /dav/cal/you%40langmail.me/<id>/ URL.)Connect your client
Use your fullyou@langmail.me address as the username and the app password as the password everywhere below.
- Apple Calendar (Mac)
- Apple Calendar (iPhone/iPad)
- Thunderbird
- Android (DAVx⁵)
- Open System Settings → Internet Accounts → Add Account → Add Other Account.
- Choose CalDAV account.
- Set Account Type to Manual and fill in:
- Select Sign In. Your Langmail calendars appear in Calendar.
Connection details
For any other CalDAV client, these are the settings:
An OAuth bearer token works too, over the same endpoint — that’s what the MCP calendar tools use — but app passwords are the practical choice for desktop and mobile calendar apps.
Troubleshooting
When the server rejects the sign-in, iPhone and iPad show “CalDAV account verification failed”; Apple Calendar on the Mac words it differently but fails the same way. The connection itself is rarely the problem — check the credentials first:- Use an app password, not your account password. Signing in to Langmail happens in the browser, so the password you use there (or your Google password) is never accepted by CalDAV. Generate an app password in webmail under Settings → Security and paste that instead.
- Don’t leave the password empty. iOS lets you save the account form without a password, but verification then fails immediately.
- Username is your full address —
you@langmail.me, not justyou. - The app password may have been revoked. App passwords are shown once and can be revoked per device in webmail. If in doubt, generate a fresh one and try again.
https://mail.langmail.me/dav/cal/you%40langmail.me/ — the parent collection that lists all your calendars; replace you@langmail.me with your own address, percent-encoding the @ as %40 — with SSL enabled on port 443.
Google Calendar and Outlook
Neither Google Calendar nor classic Outlook can subscribe to a third-party CalDAV server for two-way sync — they only sync calendars within their own accounts. You can still invite people on those systems to your events: invitations go out as standard iMIP emails they can accept from Google Calendar, Outlook, or anything else that speaks iCalendar (see Calendar workflows). For two-way access from an Android phone, use DAVx⁵ as shown above.Scheduling tools
Scheduling platforms that speak CalDAV can use your Langmail calendar the same way — reading it for conflicts and writing bookings back. See Connect Cal.com for the Cal.com setup.Next steps
Calendar workflows
Schedule meetings, recurring series, and RSVPs through an agent.
Connect Cal.com
Use your Langmail calendar as a Cal.com scheduling source.
Use a mail client
Read the same mailbox from Apple Mail, Thunderbird, or Outlook.
Open protocols
The full endpoint map for JMAP, CalDAV, IMAP, and SMTP.