Professional Email

Yes, every hosting plan includes professional email accounts; their number increases with the plan. Details for each plan are on the Web Hosting page.

Yes, you can use our professional email addresses (e.g. [email protected]) without publishing a website.

Your mailboxes use IMAP/SMTP. The server settings (incoming/outgoing, ports, SSL) are provided in cPanel and can be configured on any email client.

Yes, a webmail (such as Roundcube) is accessible from cPanel to check your emails from a browser, with no configuration required.

Basic anti-spam filtering is included with every hosting plan. Advanced anti-spam is not a paid add-on: it is included in the Pro plan.

Correctly configure your domain's SPF, DKIM and DMARC records. Our support team can help you improve deliverability.

Email storage is shared with the disk space of your hosting plan. You can distribute quotas across your mailboxes according to your needs.

Since February 2024, Gmail, Yahoo, and increasingly Microsoft Outlook require a valid DMARC record for senders exceeding 5,000 messages per day to their users. Below that threshold, SPF and DKIM alone are usually sufficient, but setting up DMARC early is still recommended. Without a compliant DMARC policy above the threshold, providers may permanently reject your messages with an SMTP 550 error — a hard bounce, not a spam folder placement. Our support team can help you configure SPF, DKIM, and DMARC for your domain.

BIMI (Brand Indicators for Message Identification) lets Gmail, Yahoo Mail and Apple Mail display your brand logo next to your emails in the inbox. Your domain needs SPF, DKIM and a DMARC policy of `p=quarantine` or `p=reject`, then you publish a `default._bimi.` DNS TXT record pointing to an SVG file of your logo. Gmail additionally requires a VMC (Verified Mark Certificate, requires a registered trademark) or CMC (Common Mark Certificate, no trademark needed). Support is live in 2026 on Gmail, Yahoo Mail, Apple Mail and Fastmail.

Yes. Gmail introduced the Common Mark Certificate (CMC) as an alternative to the VMC: it does not require a registered trademark, but you must demonstrate that your logo has been publicly displayed on your domain for at least twelve months. Yahoo Mail, Fastmail and Apple Mail support BIMI without requiring a certificate, provided DMARC is set to `p=quarantine` or `p=reject`.

The safest approach is a parallel IMAP migration: your mailboxes are copied in the background (using imapsync or your panel's built-in tool) while your MX record stays with your current provider, so recipients experience zero downtime. Once all mailboxes are synced, you switch the MX record to ServOrbit — keep both accesses active for at least 72 hours to catch any emails in transit. Visit our web hosting page or reach our support team at [email protected] to get started.

In cPanel, an Email Alias lets an additional address deliver messages to the same mailbox as the primary address — for example, contact@ and info@ both land in [email protected]'s inbox. An Email Forwarder automatically sends messages received at one address to another address, which can be outside your hosting account. To create either one, go to the Email section in cPanel, choose Email Aliases or Forwarders, enter the source address and destination, then save. Changes take effect within a few minutes.

Yes, ServOrbit shared hosting plans enforce hourly sending limits to protect deliverability for all customers on shared servers. Depending on your plan, the limit is typically 500 to 1,000 emails per hour. These limits are suited for standard transactional emails such as order confirmations and customer replies, but if you need to send marketing campaigns or large volumes, it is recommended to use a dedicated SMTP service such as Mailgun, SendGrid, or Amazon SES. Using an external SMTP service does not affect your regular emails and ensures better deliverability.

Most self-hosted applications (n8n, Jitsi, Nextcloud…) let you set an external SMTP server in their settings. Use the credentials of a ServOrbit professional email address or a dedicated sending service (Brevo, Mailgun…); avoid sending directly from your VPS IP without proper SPF, DKIM and DMARC records, as ISPs routinely classify such messages as spam. Our support team is reachable at [email protected] if you need help configuring the DNS records.

Yes, no DNS records are imposed by default: you can point your MX, SPF, DKIM and DMARC records to your own server from the DNS manager in your client area. Make sure to correctly configure the PTR (rDNS) of your email server's IP address to maximise deliverability. Our support team is available at [email protected] to guide you on DNS settings.

**Email alias** and **forwarder** serve different purposes. An **alias** is an additional address on the same mailbox: emails sent to `[email protected]` and `[email protected]` land in the same mailbox if `info` is an alias of `contact`. You only have one mailbox to manage. A **forwarder** copies incoming emails to another external address: messages sent to `[email protected]` are automatically forwarded to `[email protected]`. Useful for consolidating multiple addresses into an existing mailbox, but emails are not stored with us. **Create an alias or a forwarder**: this is not done from the client area, but in your cPanel, with the Forwarders tool (an alias is a forwarder to your own mailbox). Note: a forwarder may trigger spam filters at the final destination if your domain is not properly configured with SPF, DKIM, and DMARC.

Mautic 5.x is compatible with MySQL 8.4, but the `ONLY_FULL_GROUP_BY` SQL mode enabled by default since MySQL 8.0 causes HTTP 500 errors on certain reports (notably 'Page hits' with grouping) — the page is blank with no visible error message (issue mautic#17092). Check with `SHOW GLOBAL VARIABLES LIKE 'sql_mode'`: if the value contains `ONLY_FULL_GROUP_BY`, disable it live with `SET GLOBAL sql_mode = (SELECT REPLACE(@@sql_mode, 'ONLY_FULL_GROUP_BY', ''))` then make the change permanent in `/etc/mysql/my.cnf`. Alternatively, migrate to MariaDB 10.x which does not enable this mode by default. Always take a full backup (`mysqldump`) before any engine upgrade.

Deliverability for a .ma domain follows the same rules as any other extension: add a SPF TXT record (`v=spf1 include:your-server ~all`), enable DKIM signing from cPanel (Email Authentication > DKIM) and publish a DMARC record (`v=DMARC1; p=none; rua=mailto:your@address`) to start receiving reports. The .ma specificity is that ANRT delegates the DNS zone to our name servers when you enable managed DNS: make sure the delegation is in effect before testing your records. Our support can verify your setup at [email protected].

JMAP (RFC 8620) is a modern HTTP/JSON protocol that replaces IMAP: it synchronises mailboxes incrementally (only changes are transmitted), supports native push, and manages multiple accounts in a single connection. Stalwart Mail Server, for instance, exposes JMAP, IMAP4rev2, and SMTP simultaneously, allowing a gradual migration without cutting off existing access. Clients that support JMAP (Thunderbird 128+, native iOS/macOS apps) benefit from significantly faster synchronisation; existing IMAP clients continue to work without any changes. To deploy a compatible server on your VPS, see the ServOrbit VPS page.

Migration happens in three stages: export Mailcow mailboxes as MBOX or via imapsync (account by account), install Stalwart on a VPS and configure your domains and accounts, then reimport messages via IMAP or Stalwart's built-in import tool. During the transition, keep Mailcow active and point a secondary MX at Stalwart: incoming mail reaches both servers during the switchover window. Once all messages have been copied and your DNS MX is updated to Stalwart, you can shut down Mailcow. Our team can support server migrations via the /contact form (Devis / Quote type).

Mailcow is a full suite (Postfix, Dovecot, Rspamd, SOGo, Redis, MariaDB…) that consumes around 1 to 2 GB of RAM at idle — ideal if you want an integrated webmail and admin interface. Stalwart Mail Server is a single Rust binary (SMTP, IMAP, JMAP) that starts under 100 MB of RAM, a clear advantage on a 1 to 2 GB VPS shared with other services. Choose Mailcow for an all-in-one setup, Stalwart if memory footprint is your main constraint. Both can be installed on ServOrbit.com VPS plans starting at 99 DH/month.

A self-hosted mail server on a VPS is suitable for moderate volumes (a few hundred emails per day) with proper SPF/DKIM/DMARC configuration. Once your application sends several thousand emails per day or deliverability is critical (e-commerce, alerts), a specialized SMTP relay (Resend, Brevo, Postmark) offers already de-listed sending infrastructure and deliverability dashboards that are hard to replicate on your own. In either case, your domain must be registered with ServOrbit or point to our servers so you can configure the necessary SPF and DKIM DNS records.

Yes, all email accounts included in your ServOrbit hosting plans benefit from server-side anti-spam filtering and real-time antivirus scanning, before messages reach your inbox. You can fine-tune spam filter sensitivity from the management panel, create whitelists and blacklists, and check the quarantine to recover a legitimate message incorrectly blocked. This protection is enabled by default and requires no additional configuration; for advanced needs (legal archiving, end-to-end encryption), contact our support team.

In your ServOrbit cPanel, go to Email > Authentication to enable DKIM and SPF automatically. For DMARC, add a TXT record `_dmarc.your-domain.com` with the value `v=DMARC1; p=none; rua=mailto:[email protected]`, then tighten the policy after checking reports. Verify all three records are propagated on mxtoolbox.com before sending emails.

From your VPS, run `telnet smtp.gmail.com 25` or `nc -zv smtp.gmail.com 25`: if the connection times out or is refused, your provider is blocking outbound port 25. This is standard practice to limit spam — most VPS providers do it by default. To send emails from a VPS, use port 587 (STARTTLS) or 465 (SMTPS) with a trusted SMTP relay, configure a PTR record for your IP, and set up SPF, DKIM and DMARC. Contact support if you need port 25 opened for a legitimate use case.

A PTR (reverse DNS) record maps your IP address to a domain name: recipient mail servers use it to verify that the sender is legitimate. Without a valid PTR, your emails frequently land in spam or get rejected. It must match exactly the name announced in your server's SMTP banner (`myhostname` in Postfix). On a ServOrbit VPS, configure it from the client area, Network section, Reverse DNS tab. Combine it with SPF, DKIM and DMARC for optimal deliverability.

In the Gitea admin panel (Site Administration → Settings → Email), enter your hosting SMTP server (available in your cPanel → Email → Email Accounts), port 587 with STARTTLS, and the credentials of a dedicated mailbox (e.g. `[email protected]`). Enable the test email feature to validate the configuration before saving. Make sure your domain's SPF and DKIM records include the sending server to ensure deliverability of issue and pull request notifications.

Yes, ServOrbit hosting includes a CalDAV (calendars) and CardDAV (contacts) server accessible from Thunderbird, Apple Mail, Outlook or any compatible mobile application. Configure your client with the server URL shown in cPanel under "Calendars and Contacts". This sync works with the same professional mailbox, with no third-party tool or additional subscription required.

In cPanel, go to the "Mailing Lists" section to create a list managed by Mailman. You can define members, moderators, and archiving options directly from the interface. For large-scale marketing sends, we recommend using a dedicated tool (such as Mautic self-hosted on a VPS) to follow deliverability best practices.

SPF and DKIM authenticate a message's origin and integrity, but they do not tell the recipient what to do when a check fails — DMARC fills that gap by publishing an explicit policy (none, quarantine, or reject). Without DMARC, a bad actor can spoof your domain and still pass spam filters, because mail providers have no instruction to follow. Start with `p=none` to collect reports, then tighten to `p=quarantine` or `p=reject` once your legitimate sending streams are stable.

Google and Yahoo treat a complaint rate above 0.10% as a warning sign and impose restrictions from 0.30%: your emails may be massively rejected or sent to the spam folder. To monitor this rate, register your domain in Google Postmaster Tools (postmaster.google.com) and check the Spam Rate dashboard; Yahoo offers a similar feedback loop through its FBL program. Each complaint typically corresponds to a recipient clicking 'Report as spam' — review your lists regularly and remove inactive or improperly acquired subscribers.

The `List-Unsubscribe: <mailto:…>, <https://…>` header lets mail clients show an 'Unsubscribe' button directly in their interface, without the recipient needing to open the message. Since 2024, Google and Yahoo require this mechanism for bulk senders (more than 5,000 messages/day), and the 'one-click' variant (`List-Unsubscribe-Post: List-Unsubscribe=One-Click`) processes the request with a single click and no intermediate page. Your email platform should handle this header automatically; if you send campaigns from your own server, verify that your sending software generates this header correctly.

On a ServOrbit VPS, port 25 is blocked outbound by default to limit spam risk; use port 587 (STARTTLS) or port 465 (SMTPS/implicit SSL) for authenticated sending from your application. If you use an external SMTP relay (Mailgun, Brevo, etc.), configure the port recommended by that service. For cPanel-managed mailboxes on shared hosting, webmail and email clients also rely on port 587 or 465.

The most common cause is missing or misconfigured SPF, DKIM and DMARC records in your DNS zone. Check these records in cPanel under 'Email Authentication' and ensure your domain is authorised to send from our servers. If the issue persists after correction, write to [email protected] and attach the full headers of a rejected email.

The most reliable method is to use imapsync or the migration tool built into cPanel (Accounts → Transfer Tool), which copies all IMAP folders without disrupting the address while it is still in use. First create the mailbox on your ServOrbit hosting, configure it for incoming mail in your mail client, then start the migration. Change the MX records only once synchronisation is complete so no messages are lost in transit. Our support team can assist you at [email protected].

On a cPanel shared hosting account, the default outgoing SMTP server is the one provided with your account, but most web applications (WordPress, Drupal, etc.) allow you to configure a third-party SMTP relay through their own plugin or configuration settings. You can therefore use an external service like Mailgun or Gmail SMTP directly from your application, without modifying the server configuration. Port 587 (STARTTLS) is recommended. For advanced transactional sending needs, our VPS plans give you full control over Postfix or Exim.

Yes. You simply need to point your domain's MX records to our servers from your current registrar's DNS zone. No domain transfer is required. If you do not yet have a ServOrbit hosting plan, you can subscribe to a web hosting plan and configure the MX records in minutes. Our getting-started guide or our team at [email protected] can assist you.

In cPanel, go to the 'Email' section then 'Default Email Address' (also called the default address or catch-all). Set it to forward to an existing mailbox or discard messages sent to non-existent addresses on your domain. This is useful to avoid missing any messages, but may increase spam if your domain is targeted by address-harvesting bots.

Yes, ServOrbit lets you deploy solutions like Nextcloud (mail + calendar + contacts) with one click from the marketplace; Mail-in-a-Box is not listed there, but you can install it yourself on your VPS. Your ServOrbit VPS includes a dedicated IP, essential for good email deliverability. Remember to configure SPF, DKIM and DMARC records in your ServOrbit DNS zone to maximize deliverability to Gmail, Outlook and other providers.

Several checks are necessary: ensure the rDNS (PTR) of your ServOrbit IP matches your domain name (configurable from the client area), check that your IP is not on a blacklist (MXToolbox), and publish a minimal DMARC policy (p=none) to receive reports. ServOrbit provides dedicated, non-shared IPs on VPS plans, eliminating the risk of contamination from other senders.

No, a ServOrbit VPS is a bare cloud server: it does not include a preconfigured mail server. You can install a mail server yourself (Stalwart, Mailcow, Postfix, etc.) or use our cPanel shared hosting which includes mailboxes. If you want a managed professional mail service, contact support through your client area to explore available options.

Yes. Our mail servers enforce TLS (Transport Layer Security) encryption for all outgoing connections and accept it for incoming connections: emails travel encrypted between compatible servers. The recommended configuration for your mail client — IMAP on port 993 (SSL/TLS) and SMTP on port 465 (SSL/TLS) or 587 (STARTTLS) — also ensures that the connection between your device and our servers is encrypted. This transit encryption protects against interception on the network, but is not end-to-end encryption: messages are accessible in plain text on the servers to allow spam detection and antivirus scanning. For full confidentiality of message content, consider S/MIME or PGP — solutions that work independently of the hosting provider.

Email mailboxes on ServOrbit shared hosting benefit from spam filtering enabled by default (SpamAssassin via cPanel); you can adjust the sensitivity level and create custom rules directly from cPanel → Spam Filters. Advanced anti-spam is not sold as an add-on: it is included in the Pro plan — contact our team from your client area to learn more. On a VPS, you can deploy solutions such as Rspamd or Amavis depending on your server configuration.

Yes, configuring SPF and DKIM is essential to prevent emails sent by Mautic from your VPS from landing in spam. SPF declares your sending IP in your DNS zone, and DKIM cryptographically signs each message — both records are verified by Gmail, Outlook, and most mail providers. Without them, your deliverability rate will be low and your campaigns risk being blocked. Also consider setting up a DMARC record and enabling reverse DNS (PTR) for your VPS from your client area.

Mailpit is a lightweight SMTP server that catches all outgoing e-mails and displays them in a web interface — no message is actually sent, making it the ideal tool for testing e-mail sending during development. Install it via Docker on your ServOrbit VPS, then point your application's SMTP settings to Mailpit's port 1025 and browse its web interface on port 8025 (protect it with a reverse proxy or an IP allowlist). Be careful never to expose SMTP port 1025 publicly, as it accepts any e-mail without authentication.

Yes, provided you request it from support: outbound port 25 is blocked by default on ServOrbit VPS plans to limit spam risk, but it can be opened for a legitimate use case (agency sending platform, mail hosting, etc.). Once open, install Postal yourself on your VPS (it is not listed in the ServOrbit Marketplace), configure your SPF, DKIM and PTR records, then serve multiple sender domains from the same instance. Open a ticket from your client area to request port 25 to be unlocked.

A Postfix relay is a mail transfer agent (MTA) configured to route outbound emails from an application to the internet via standard SMTP ports — with no management interface or sending statistics. Postal is a full-featured sending platform: it adds a web interface, sending queues, bounce tracking, per-domain deliverability statistics and a webhook system. For an application sending a few hundred transactional emails per day, a well-configured Postfix relay is sufficient; for an agency managing several campaigns or client domains, Postal provides the visibility and control needed.

Stalwart is a modern all-in-one solution written in Rust, particularly suited if you want a unified SMTP/IMAP/JMAP setup with minimal dependencies. Mailcow is a Docker-based suite ready to deploy, ideal if you prefer a full web administration interface without configuring components manually. Postfix+Dovecot offers maximum flexibility and integrates with most Linux distributions, but requires deeper configuration knowledge. To compare RAM and CPU requirements on ServOrbit VPS plans, see the dedicated article in our knowledge base or contact our support at [email protected].

DMARCbis (RFC 9989 to 9991) gradually replaces RFC 7489 in 2026 by clarifying subdomain handling, inherited policies and aggregate reporting. For a self-hosted mail server, migration is not yet mandatory today, but major gateways (Gmail, Microsoft 365) will progressively adopt the new rules: updating your DMARC record to include `sp=` and `rua=` tags is recommended to stay compliant. Refer to RFC 9989 or our DMARC configuration guide to prepare for a smooth transition.

On a ServOrbit hosting plan, the webmail shipped with cPanel is part of the platform: our team handles its updates, with no action on your side. If you installed Roundcube yourself on a VPS, keeping it up to date is up to you, backing up its database and configuration before each upgrade. To find out whether an announced fix concerns the platform, write to [email protected].

Go step by step. First publish `p=none` with a `rua` address to receive aggregate reports, and let them run for two to four weeks: they list every source sending on your behalf (hosting server, newsletter, CRM, invoicing). Bring each legitimate source into SPF or DKIM alignment with your domain, then move to `p=quarantine` with `pct=10` and raise that percentage in stages. Only switch to `p=reject` once the reports no longer show a legitimate sender failing; if you are unsure about a source, [email protected] can help you interpret your reports.