Standards and client support
Ration supports the following standards for customers who need to use a familiar desktop, mobile, or specialist client alongside the Ration web application.
| Standard | What it connects | Best for |
|---|---|---|
| Exchange ActiveSync | Mail, contacts, calendar, tasks, and notes | Built-in mobile apps and compatible Exchange clients. |
| CalDAV | Calendars, events, invitations, and availability | Calendar applications that support CalDAV. |
| CardDAV | Address books and contacts | Contact applications that support CardDAV. |
| IMAP | Mail folders and messages | Desktop and mobile mail readers. |
| POP3 | Mail download | Clients that require POP3 retrieval. |
| SMTP | Sending mail | Mail clients and approved outbound integrations. |
Use one connection method per client. For a phone that needs Mail, Contacts, Calendar, Tasks, and Notes together, choose Exchange ActiveSync rather than configuring separate IMAP, CalDAV, and CardDAV accounts.
Connection details
For Ration-hosted accounts, use the managed endpoints below. Use your full Ration email address as the username and require TLS/SSL for every connection.
If your organisation runs Ration on-premises or through a managed service provider (MSP), use the hostname, port, and certificate requirements supplied by that provider instead. The provider’s values replace the managed-cloud defaults in this guide.
| Service | Discovery or endpoint | Authentication |
|---|---|---|
| Exchange ActiveSync | https://mail.ration.works/Microsoft-Server-ActiveSync | Full email address and Ration password. |
| ActiveSync Autodiscover | https://autodiscover.ration.works/Autodiscover/Autodiscover.xml | Usually detected automatically. |
| CalDAV | https://app.ration.works/.well-known/caldav | Full email address and Ration password. |
| CardDAV | https://app.ration.works/.well-known/carddav | Full email address and Ration password. |
| IMAP / POP3 / SMTP | imap.ration.works, pop.ration.works, and smtp.ration.works | Full email address and Ration password, or an application-specific password after 2FA is enabled. |
Ration supports automatic discovery for compatible clients, including ActiveSync Autodiscover and mail-client autoconfiguration. Start with automatic account setup whenever the client offers it. Use manual details only when the client asks for them or your administrator directs you to do so.
When two-factor authentication is enabled, IMAP, POP3, and SMTP clients must use an application-specific password created in Settings → Security. Do not enter a time-based verification code in a mail client's password field.
Choosing the right protocol
| Your need | Recommended method |
|---|---|
| A phone with one account for mail and personal-information management | Exchange ActiveSync mobile setup |
| A desktop mail app | IMAP for mail retrieval plus SMTP for sending |
| A client that only supports download-style mail retrieval | POP3 plus SMTP |
| A desktop calendar app | CalDAV |
| A desktop contacts app | CardDAV |
| A single event or contact, without ongoing sync | Download the .ics or contact file from Ration instead |
Security requirements
- Use the full email address as the account username.
- Require TLS/SSL and accept the certificate only when it matches the approved mail hostname.
- Use an application-specific password for IMAP, POP3, and SMTP after 2FA is enabled; create a separate credential for each client or device.
- Do not share passwords, application-specific passwords, QR setup data, or recovery codes with support. Support can request an error screenshot and your email address, but never your credential.
- Remove an application-specific password when a device is lost, replaced, or no longer uses Ration.
Help with client setup
If automatic setup fails, collect the client name and version, device/operating-system version, your Ration email address, and a screenshot of the error. Do not include passwords or authentication codes. For an on-premises or MSP deployment, the administrator can confirm the correct hostname, which protocols are enabled for the tenant, and any organisation-specific network requirements.