Setting Up Mail.ru Email for Your Custom Domain: A Complete Technical Guide

A custom domain email address — such as contact@yourdomain.com — routes all mail through servers you control via DNS, rather than through a shared provider namespace. To configure Mail.ru for Business with a custom domain, you must verify domain ownership via a DNS TXT or CNAME record, point your domain's MX records to mxs.mail.ru, and configure IMAP/SMTP credentials in your mail client. The entire process typically completes within 24–48 hours, depending on DNS propagation speed across global resolvers.

This guide covers every technical step in full detail, including DNS record syntax, mail client configuration, common failure modes, and security hardening — information that goes well beyond the standard setup walkthrough.

Prerequisites and Architecture Overview

Before touching a single DNS record, understand what you are actually building. Mail.ru for Business acts as a managed mail exchanger: it accepts inbound SMTP connections on behalf of your domain, stores messages on its infrastructure, and exposes them to end users via IMAP, POP3, or its web interface. Your domain's DNS is the control plane that tells the global mail routing system where to deliver messages.

The components involved are:

• MX records — direct inbound SMTP traffic to Mail.ru's servers
• TXT record (SPF) — authorizes Mail.ru's outbound servers to send on your domain's behalf
• DKIM — cryptographically signs outgoing messages to prevent spoofing
• DMARC — policy record that instructs receiving servers what to do with messages that fail SPF/DKIM
• Domain verification record — a one-time TXT or CNAME record that proves ownership to Mail.ru's provisioning system

Skipping SPF, DKIM, or DMARC is one of the most common mistakes administrators make. Without them, your outbound mail will frequently land in spam folders or be outright rejected by strict receivers like Google Workspace and Microsoft 365.

You will also need:

• An active registered domain with access to its DNS management panel
• A Mail.ru account (personal or new business account)
• Administrative access to your DNS zone (TTL edit rights)

If you have not yet registered a domain, AlexHost Domain Registration provides full DNS zone control, which is essential for the record modifications described throughout this guide.

Step 1: Register and Access Your Domain's DNS Zone

Log in to your domain registrar or DNS provider and locate the DNS management or Zone Editor panel. You need the ability to create, modify, and delete the following record types: TXT, MX, and CNAME.

Before making any changes, note the current TTL values on your existing records. Temporarily lowering TTL to 300 seconds (5 minutes) before you begin will dramatically reduce the time you spend waiting for propagation during each configuration step. Remember to restore TTL to a sensible value (3600 or higher) after the setup is complete.

If your domain is currently serving live email through another provider, do not remove existing MX records until Mail.ru is fully verified and tested. Run both configurations in parallel during the transition window.

Step 2: Create a Mail.ru for Business Account

Navigate to biz.mail.ru and sign in with an existing Mail.ru account or create a new one. The business platform is separate from the consumer Mail.ru interface — it provides a domain management dashboard, user provisioning, and administrative controls.

Once authenticated:

1. Click "Connect domain" or the equivalent option in your language setting.
2. Enter your domain name exactly as registered — for example, yourdomain.com — without any subdomain prefix or trailing slash.
3. The system will present you with a verification method.

Step 3: Verify Domain Ownership

Mail.ru will offer one or both of the following verification methods:

Method A: TXT Record

Add a TXT record to your DNS zone with the value provided by Mail.ru. The record will look similar to this:

Name/Host: @  (or yourdomain.com)
Type:       TXT
Value:      mailru-verification: <unique-token>
TTL:        300

Method B: CNAME Record

Name/Host: mailruverify  (or as specified)
Type:       CNAME
Value:      <unique-value>.mail.ru.
TTL:        300

Add the record your DNS provider supports most cleanly. Some providers handle TXT records on the apex domain (@) more reliably than CNAME records at the root. Once the record is saved, return to the Mail.ru dashboard and click "Verify". Mail.ru's system will perform a DNS lookup to confirm the record exists.

Propagation reality check: DNS changes do not take effect instantly. Use a tool like dig to monitor propagation from your terminal before clicking verify:

dig TXT yourdomain.com +short

Or query a specific public resolver to see what it currently returns:

dig TXT yourdomain.com @8.8.8.8 +short

Once the token appears in the output, the verification check will succeed. Do not click verify before the record resolves — repeated failed attempts can temporarily throttle the verification endpoint.

Step 4: Configure MX Records

MX records are the core routing mechanism for inbound email. After domain verification, Mail.ru will display the MX records you must add. The standard configuration is:

Add this record in your DNS zone:

Name/Host: @
Type:       MX
Priority:   10
Value:      mxs.mail.ru.
TTL:        300 (raise to 3600 after testing)

Critical detail: The trailing dot after mxs.mail.ru. is significant in DNS syntax — it denotes an absolute (fully qualified) domain name. Most web-based DNS panels add it automatically, but if you are editing a raw zone file, omit it only if the panel normalizes it for you.

If you are migrating from another mail provider, remove the old MX records only after you have confirmed that Mail.ru is receiving test messages correctly. Running two sets of MX records simultaneously during migration is acceptable — the lower priority number wins, so set Mail.ru at priority 10 and your old provider at priority 20 temporarily.

Verify the MX record has propagated:

dig MX yourdomain.com @8.8.8.8 +short

Expected output:

10 mxs.mail.ru.

Step 5: Configure SPF, DKIM, and DMARC

This is the step most tutorials omit, and it is the primary reason custom domain email ends up in spam.

SPF Record

SPF (Sender Policy Framework) specifies which servers are authorized to send email from your domain. Add the following TXT record:

Name/Host: @
Type:       TXT
Value:      v=spf1 include:_spf.mail.ru ~all
TTL:        3600

The ~all qualifier means "soft fail" — messages from unauthorized servers are marked suspicious but not rejected. If you want a strict policy and are certain all legitimate mail flows through Mail.ru, use -all (hard fail). Do not use +all under any circumstances — it authorizes every server on the internet to send as your domain.

Important constraint: A domain can have only one SPF TXT record. If you already have an SPF record for another service, merge the include statements into a single record:

v=spf1 include:_spf.mail.ru include:other-service.com ~all

DKIM Record

Mail.ru for Business generates a DKIM key pair. The public key is provided as a TXT record you must publish in your DNS zone. Retrieve it from the Mail.ru Business dashboard under domain settings. It will look like:

Name/Host: mailru._domainkey
Type:       TXT
Value:      v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GN...
TTL:        3600

The selector (mailru) may vary — use exactly what the dashboard provides. Verify it after propagation:

dig TXT mailru._domainkey.yourdomain.com +short

DMARC Record

DMARC ties SPF and DKIM together and gives receiving servers a policy to enforce. Start with a monitoring-only policy:

Name/Host: _dmarc
Type:       TXT
Value:      v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
TTL:        3600

Once you have confirmed legitimate mail is passing SPF and DKIM checks (review the aggregate reports sent to rua), tighten the policy:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com; pct=100

Eventually move to p=reject for maximum protection against domain spoofing and phishing.

Step 6: Create Mailboxes in the Mail.ru Business Dashboard

With DNS fully configured and verified, provision your mailboxes:

1. Open the Mail.ru for Business admin dashboard.
2. Navigate to Users or Mailboxes.
3. Click Add user and enter the desired local part of the address — for example, contact, support, admin, info.
4. Set a strong password (minimum 12 characters, mixed case, digits, and symbols).
5. Assign storage quota if the plan allows per-user limits.

Each created mailbox becomes accessible immediately at username@yourdomain.com. The web interface is available at mail.ru — users log in with their full domain email address and the password you set.

Step 7: Configure Mail Clients via IMAP and SMTP

For users who prefer desktop or mobile clients (Thunderbird, Outlook, Apple Mail, K-9 Mail), configure the following server settings:

Mail.ru Server Configuration Reference

Username: Always use the full email address — you@yourdomain.com — not just the local part.

Authentication: Mail.ru requires password-based authentication. If the account has two-factor authentication enabled on the consumer platform, you may need to generate an app-specific password from the security settings page.

POP3 vs. IMAP: Use IMAP unless you have a specific reason not to. IMAP synchronizes message state (read, flagged, deleted) across all devices and keeps messages on the server. POP3 downloads and typically removes messages from the server, which breaks multi-device workflows.

Thunderbird Configuration Example

Account type:       IMAP
Incoming server:    imap.mail.ru
Port:               993
Connection security: SSL/TLS
Authentication:     Normal password
Username:           you@yourdomain.com

Outgoing server:    smtp.mail.ru
Port:               465
Connection security: SSL/TLS
Authentication:     Normal password
Username:           you@yourdomain.com

Step 8: Test the Complete Mail Flow

Do not assume the configuration is correct — verify every direction of mail flow explicitly.

Test inbound delivery:

Send a message from an external address (Gmail, Outlook.com) to you@yourdomain.com. Confirm it arrives in the Mail.ru inbox within a few minutes.

Test outbound delivery:

Send a message from you@yourdomain.com to an external address. Check that it arrives and inspect the message headers to confirm SPF and DKIM pass:

Authentication-Results: mx.google.com;
   dkim=pass header.i=@yourdomain.com;
   spf=pass (google.com: domain of you@yourdomain.com designates ... as permitted sender)

Test SPF/DKIM alignment using MXToolbox:

# Check SPF record syntax
curl "https://mxtoolbox.com/api/v1/lookup/spf/yourdomain.com"

Or use the web interface at mxtoolbox.com to run SPF, DKIM, DMARC, and MX lookup checks simultaneously.

Test SMTP connectivity from the command line:

telnet smtp.mail.ru 465

If port 465 is blocked by your local firewall or ISP, try port 587 with STARTTLS instead.

Common Failure Modes and How to Fix Them

Mail Not Being Received

• Confirm MX records have propagated: dig MX yourdomain.com +short
• Check that old MX records from a previous provider have been fully removed
• Verify the domain status in the Mail.ru Business dashboard shows "Active"

Outbound Mail Landing in Spam

• SPF record is missing or contains a syntax error — validate with dig TXT yourdomain.com +short
• DKIM record is not yet propagated or was entered incorrectly — check for line breaks introduced by copy-paste
• DMARC policy is absent — even a p=none record improves deliverability signals

Authentication Failures in Mail Clients

• Ensure you are using the full email address as the username, not just the local part
• If 2FA is enabled on the Mail.ru account, generate and use an app-specific password
• Confirm the port and encryption type match exactly — mixing SSL/TLS with STARTTLS ports causes connection resets

Domain Verification Keeps Failing

• The DNS record has not propagated yet — wait and re-check with dig before retrying
• The TXT record value was entered with extra spaces or quotes — most DNS panels add quotes automatically; do not add them manually
• Some providers require the @ host to be entered as the bare domain name — check your registrar's documentation

Mail.ru for Business vs. Alternative Providers

Mail.ru for Business is a practical choice for organizations operating in Russian-speaking markets or those with existing Mail.ru infrastructure. For teams requiring deep integration with productivity suites or operating under strict data sovereignty requirements outside Russia, evaluate the alternatives in the table above carefully.

Hosting Considerations for Custom Domain Email

If you are running a website alongside your custom email, the hosting environment affects your DNS management workflow. On a VPS Hosting plan, you have direct access to DNS zone files and can manage records via command-line tools or a control panel without waiting for a registrar's web interface to propagate changes internally.

For teams managing multiple domains and email configurations, a VPS with cPanel provides a graphical Zone Editor that simplifies TXT, MX, and DKIM record management without requiring raw zone file editing. cPanel also includes a built-in Email Deliverability tool that automatically checks SPF and DKIM alignment for hosted domains.

If you need a fully managed email infrastructure rather than routing through Mail.ru, AlexHost Email Hosting provides dedicated mailbox hosting with full DNS control, eliminating the dependency on a third-party mail platform entirely.

For high-traffic business environments where email is mission-critical, a Dedicated Server gives you the option to run your own MTA (Postfix, Exim) with complete control over mail queues, delivery policies, and logging — an architecture that Mail.ru for Business cannot replicate.

Technical Key-Takeaway Checklist

Use this checklist to confirm your setup is production-ready before considering the configuration complete:

• Domain verified in Mail.ru Business dashboard (status shows "Active")
• MX record points to mxs.mail.ru with priority 10, old MX records removed
• SPF TXT record published at apex domain with include:_spf.mail.ru
• DKIM TXT record published at mailru._domainkey.yourdomain.com
• DMARC TXT record published at _dmarc.yourdomain.com (start with p=none, tighten later)
• Inbound test message received from an external address
• Outbound test message headers show dkim=pass and spf=pass
• Mail client configured with IMAP port 993 (SSL/TLS) and SMTP port 465 or 587
• TTL values restored to 3600 after testing is complete
• App-specific password generated if 2FA is active on the Mail.ru account

Frequently Asked Questions

How long does Mail.ru domain verification actually take?

In practice, if you lower your DNS TTL to 300 seconds before adding the verification record, Mail.ru can confirm ownership within 5–15 minutes. The stated 24–48 hour window applies when TTL is left at the default (often 3600 or higher), because resolvers cache the old (empty) response for that duration before re-querying.

Can I use Mail.ru for Business alongside another mail provider on the same domain?

Yes, but only one provider can be the primary MX destination. You can route specific subdomains (e.g., notifications.yourdomain.com) to a different provider, but for the root domain, only one set of MX records should be active at a time to avoid unpredictable delivery splitting.

Why is my outbound mail from Mail.ru going to spam at Gmail or Outlook?

The most common causes are a missing or misconfigured SPF record, absent DKIM signature, or no DMARC policy. Run your domain through mail-tester.com to get a scored report identifying exactly which authentication mechanisms are failing.

What happens to my email if I stop using Mail.ru for Business?

Mail delivery stops as soon as your MX records are changed away from mxs.mail.ru. Existing messages stored on Mail.ru's servers remain accessible via the web interface until the account is closed, but you should export them via IMAP (using a client like Thunderbird) before making the switch to avoid data loss.

Is it possible to configure Mail.ru email on a domain managed through AlexHost?

Yes. If your domain is registered through AlexHost Domain Registration, you have full access to the DNS zone editor. Add the Mail.ru verification TXT record, MX record, SPF TXT record, and DKIM TXT record directly from the AlexHost control panel. The process is identical to any other registrar — only the interface differs.