Home›Guides›Email

Email · Understand

What features to expect from a business email service

A business email service is judged less by its webmail than by the ordinary situations it handles without incident: a shared address, an absence, a replaced phone, a deleted message, a departure. Here is a short checklist for a requirements document, in five blocks, each line with the failure it prevents. To compare European providers with one another, the guide choosing a European business email service goes further.

Updated October 20267 minOfficial sources cited

How to read this list

Each line describes a feature, then the everyday failure it prevents. If a line matches no situation you actually face, it has no place in your requirements document. If it does, ask the provider to demonstrate it on a test mailbox, not to tick it on a brochure.

Features that are truly secondary for an SME are grouped at the end. They are not useless: they address a specific risk that not everyone has.

1. Identity: addresses that belong to you

  • A domain in your name. Your addresses end with your domain, and that domain is registered in your name. Failure prevented: a provider that keeps control of the domain also keeps control of your mail the day you want to leave.
  • Aliases. Another address that delivers into an existing mailbox: firstname.lastname@ and initials@, or the former address of an employee who changed their name. Failure prevented: a message rejected because the address the customer typed no longer exists.
  • Multiple domains. A group with several brands or companies manages all its domains in one place, each with its own addresses. Failure prevented: two email systems to administer, two departure procedures, two invoices.

2. Everyday use: what teams do every day

  • Shared mailboxes with delegation. A common mailbox, contact@ or invoices@, read by several people, with separate rights: read, reply, manage. Failure prevented: the shared mailbox password circulating between offices and still known to people who have left.
  • Sending on behalf of someone else. An assistant writes “on behalf of” a partner, or “as” the department mailbox. Failure prevented: a customer receiving a reply signed by a name they do not know.
  • Distribution lists. One address that delivers to several mailboxes. Failure prevented: a message addressed to “the team” that reaches only half of the team.
  • Synchronized calendars and contacts. Shared calendars, colleagues’ availability, meeting rooms, the company address book, in webmail, Outlook and on the phone. IMAP carries only mail; calendars and contacts go through other protocols, such as Exchange ActiveSync. Failure prevented: the appointment booked on the phone that does not appear in Outlook.
  • Out-of-office reply. Set by the user, and by the administrator when the user can no longer do it. Failure prevented: a customer left without a reply during three weeks of sick leave.
  • The tools already in place. Browser, Outlook for Windows, Outlook for Mac, iPhone, Android. Run the demonstration on each one separately. Failure prevented: discovering after the switchover that management, equipped with Macs, no longer has its calendars.

3. Basic security

  • SPF, DKIM and DMARC configured for your domain. These three records state who is allowed to send in your name and make it possible to check that a message has not been altered. Failure prevented: your invoices landing in your customers’ spam folders. How they work is explained in SPF, DKIM and DMARC.
  • Two-factor authentication. Failure prevented: a password stolen by phishing that is enough to open the mailbox and send fake bank details to your customers.
  • Encrypted connections. Webmail, apps and synchronization all go through encrypted connections. Failure prevented: a password read over hotel Wi-Fi.
  • Remote wipe of a device. Failure prevented: a lost phone that still holds three years of readable mail.
  • Inbound mail filtering. Anti-spam and antivirus at a minimum. CEO fraud and malicious links require a higher level, which not every plan includes. The details are in the Email security section.

4. Recovery after an error

  • Users can recover a deleted message. A recovery folder, beyond the emptied trash. Failure prevented: a support ticket for every mistake.
  • A backup independent of the server. Copies outside the platform that a deletion or ransomware cannot reach. Failure prevented: a deletion that replicates to every copy.
  • A documented restore process. Who starts it, how far back it goes, for a message, a folder or a mailbox. Failure prevented: learning during the incident that the backup exists but nobody knows how to restore it.

The differences between trash, backup and platform failover are covered in backup, deletion and continuity.

5. Exit

An email service you cannot leave is only under your control in appearance. Standard protocols are the best insurance. For example, IMAP gives access to messages and folders on the server, CalDAV to calendars in iCalendar format, CardDAV to contacts in vCard format. A service that exposes them, or provides an equivalent full export, lets you take your history to another operator.

Also ask about the export lead time, how long data is kept after termination and the deletion procedure. Failure prevented: ten years of history that now exists only in webmail at a provider you are leaving.

What is secondary for many SMEs

These features address a specific risk. Take them if you have that risk, not because they appear in a comparison chart.

FeatureUseful when
Dedicated IP addressYou send a lot, or your sending reputation must not depend on other customers of the platform.
Custom hostnameYou want servers, webmail or device settings to carry your name rather than the provider’s.
Legal archivingAn obligation, a dispute or a major client requires you to retain messages long-term, out of reach of deletions.
S/MIME signing and encryptionSome exchanges must be signed, or remain unreadable to any intermediary, including the operator.
Built-in video conferencingYou do not already have a meeting tool, or you want it with the same operator.

Retention period itself is not an email feature: it is a policy. The guide retaining and archiving documents sets out the method.

Frequently asked questions

Should a business email service include calendar and contacts?

For a team, yes. Appointments, rooms and the company address book live alongside mail. Check that they sync on every type of device.

Is IMAP enough?

For reading and filing mail, often. Not for shared calendars and contacts. The difference is explained in the guide to choosing a European email service.

Is legal archiving mandatory?

There is no single rule for all companies. It becomes necessary when an obligation or a litigation risk requires you to prove what was exchanged. See archiving messages.

How should shared addresses be managed?

Alias, list or shared mailbox, depending on the need. The choice and the setup in Klytic Mail are described in shared mailboxes, aliases and multiple entities.

Where Klytic stands

Klytic Mail comes in two plans, Standard and Pro, which offer the same features: only the storage space differs, 5 GB or 15 GB per mailbox, expandable on request. Both plans can be mixed within the same organization.

BlockIncluded in Standard and ProOptional or on quote
IdentityAddresses on your domain, aliases, multiple domains in one administration console, custom hostnameDedicated IP address (option)
Everyday useWebmail, distribution lists, shared folders, delegation, calendars and contacts, global address book, tasks, automatic replies, chat; Exchange ActiveSync and EWS, Outlook for WindowsOutlook for Mac connector, video chat and online meetings (options)
SecurityFront-end anti-spam and antivirus, SPF, DKIM and DMARC, two-factor authentication, remote device wipeS/MIME, certificate supplied on quote (option)
RecoveryDumpster folder, encrypted hourly backup retained for 30 days, restore by support in the event of a service malfunction, a deliberate deletion by an employee or a mailbox deleted too early during a departure (3 requests per month), or an attack despite protected workstationsLegal archiving (option); restore after an accidental deletion, a user error or with insufficiently protected workstations (paid support ticket)
InfrastructureHosting in Klytic’s shared architectureExtensions and dedicated server (on quote)

For exit, Klytic relies on open standards, including IMAP, CalDAV and CardDAV, and assists with data retrieval before deleting the data on request. Migration from another email service is carried out on quote; advice on preparing it is free. Prices are on the Pricing page, and offer details on the Klytic Mail page.

What the offer does not claim: to reproduce every feature of Microsoft 365 or Google Workspace. Advanced filtering against CEO fraud is handled by Klytic MTA, described in the Email security section.

This page offers a general checklist. It does not replace a trial on your own mailboxes.

Sources

Consulted in October 2026.

  • Klytic, Email: included features, options and items on quote for the Standard and Pro plans. klytic.com
  • Klytic, Frequently asked questions: data retrieval based on open standards (IMAP, CalDAV, CardDAV). klytic.com
  • RFC 9051, IMAP4rev2: protocol that allows a client to access and manipulate messages on a server. ietf.org
  • RFC 4791, CalDAV: access, management and sharing of calendars in iCalendar format. ietf.org
  • RFC 6352, CardDAV: access, management and sharing of contacts in vCard format. ietf.org

Check the list on your own mailboxes

Try Klytic Mail for 30 days, no commitment: aliases, shared mailbox, Outlook and mobile, restore.

Start the free trial →

See the Klytic Mail offer

Welcome offer

30 days free trial, migration support included

No-commitment trial. An advisor calls you back to understand your needs and prepare your Klytic workspace.