Before choosing a server or a hosting plan, ask who can help when the person who set up email is unavailable. A five-person business needs someone who can find the domain account, handle user access, and contact the right support team. A cheap server doesn't supply that cover by itself.
Compare the choices using the same incident: a customer says an important message is missing. Write down who investigates, what access they need, and how work continues while they do it.
What running your own server involves
After installation, you need to maintain the email software and operating system, watch storage capacity, and monitor delivery and errors. You also need backups and a recovery process that works.
Outgoing email has its own requirements. The server must identify the domain correctly, and sender settings must match the delivery setup. SPF defines authorized sending sources, DKIM is used to verify signatures, and DMARC connects authentication checks with the sender's domain.
Users will also need help. A missing message may be in another folder, may have failed because of an incorrect recipient, or may have been rejected by an external server. Diagnosing it takes access to logs and an understanding of the message's route.
List these jobs and assign responsibility. If everything depends on one person, arrange cover and document recovery procedures. The server's price doesn't reflect the time spent on ongoing support.
What to check with an email host
The provider manages its server infrastructure while you configure domains, mailboxes, access, and working processes. Check which tasks are actually included in the service.
Ask about storage limits, domains and users, email app connections, and sending restrictions. If you use shared addresses, check shared mailbox behavior. If you are moving providers, find out how to bring over your archive and retrieve your data if you move again later.
Discuss backups and recovery separately: what is saved, who can request a restore, and which conditions apply. The word “hosting” does not answer all of those questions.
TrekMail hosts mailboxes in a managed service. The email plan comparison lists account capabilities. Compare them with your actual employee count, archive size, and applications.
Can I choose a separate sending service?
Yes. Incoming mailbox storage and outgoing delivery can use different services. For example, TrekMail can provide mailboxes and webmail while outgoing messages use your external SMTP profile.
SMTP passes messages to the next stage of delivery. Connecting your own provider lets you keep an existing sending service, but it introduces separate settings, approved senders, and billing terms. That provider's limits still apply.
The custom SMTP guide explains this setup. Incoming mail stays in the hosted mailboxes; the outgoing route changes. Use this arrangement when you have a specific reason to choose another sending provider.
None of these options guarantees that every message reaches the inbox. A self-managed server, a hosted service, and external SMTP are all subject to recipient checks and the nature of the correspondence. Assess real working messages and delivery errors.
Compare the options against your own work
Take a typical week: new employees, attachments, shared addresses, forgotten passwords, and several external recipients. For each option, write down who sets things up, helps users, and investigates failures.
Add less frequent jobs such as data recovery, an administrator leaving, archive growth, and an email migration. Note what you can handle yourself and what help you expect.
Work through an absence before it becomes an incident
Ask the backup administrator to find the domain registrar, active DNS service, mailbox management page and outgoing provider using the handover record. They should be able to identify the correct accounts without relying on the original administrator's browser history. If recovery depends on an inaccessible work mailbox, resolve that dependency while the owner is available.
Give the backup person a realistic question: a customer says their reply never arrived. Ask what information they would collect and which provider they would contact. A useful record includes the sender, recipient, approximate time and any delivery error, without asking the customer to send passwords or unrelated private correspondence.
For a hosted mailbox, the backup person's first action may be to check the address and contact support with those details. For a self-managed server, someone may also need access to monitoring, logs and recovery procedures. Compare the actual responsibilities rather than treating both arrangements as the same task with different subscription prices.
Ask specific recovery questions
Check what “backup” covers in the service you are assessing. Is the question about a deleted message, an unavailable mailbox or an entire service outage? Who is authorised to request help, what information must they supply and what limits apply? Record the documented answer and its date. Do not turn a general statement about backups into an invented restore guarantee.
For your own server, consider where recovery copies are kept and who can use them if the primary server is unavailable. A backup job completing is not the same result as a successful recovery. Arrange a separate, authorised recovery exercise appropriate to your setup and record what was actually restored.
Also check how the team will retrieve or move its data if it later changes providers. Identify the available supported route, the person responsible for the export and the checks needed at the destination. Keeping these responsibilities explicit reduces dependence on whoever made the original purchase.
Account for tools outside the mailbox service
A website, booking system or invoicing platform may send mail using its own configuration. Put those senders on the responsibility sheet as well. A mailbox administrator may be able to read customer replies without having access to fix the application's SMTP settings.
If you use an external outgoing provider, keep its owner, renewal arrangements and sender-verification responsibilities clear. Hosted mailbox support and the external provider may each need different evidence to investigate a delivery problem. Know which route a sample message used before approaching either one. The useful result is a setup in which the backup person knows the next responsible contact, even when they cannot solve every issue personally.
Build a handover sheet before choosing
List the owner of the domain, DNS, mail service, outgoing provider, and recovery contacts. Name a backup person for each responsibility and store access using your normal secure process. The sheet should explain where to get help without containing a collection of shared passwords.
Ask a prospective host about the recovery and support conditions that matter to you. Record the answer rather than assuming a specific SLA or restore time. Choose the setup your team can keep operating after the initial administrator moves on.
Related reading
- Self-managed mail servers and hosted email
- Email Hosting for MSPs: Client-Domain Operations Without Margin Loss
- Three brands in one email account: who should see what?
- A colleague is leaving: keep incoming mail and close access
- Out of office: who handles replies while you are away?
