A step-by-step guide to connecting MCMail, hosting email on your company domain and giving employees work mailboxes like name@company.uz. The whole process takes anywhere from 30 minutes to a couple of hours — most of that is waiting for DNS records to update.
What you will need
- A company domain, for example
company.uz. If you don't have one yet, start with our article on choosing and registering a domain. - Access to DNS management — the control panel of the registrar or DNS hosting provider that serves the domain. If a contractor registered the domain for you, ask them for access in advance.
- A list of employees: names and the addresses they need. For a large team, a CSV spreadsheet is the most convenient option.
- Sign up
- Top up your balance
- Add your domain
- DNS records
- Check DNS
- Create mailboxes
- Sign in to email
- Test sending
1Sign up in the customer portal
Go to mcvps.uz and create an account. This is the shared portal for all MYCLOUD services: it holds your balance, your services and the domain connection wizard.
New customers get a 7-day trial, so you can try email on your own domain before paying.
2Top up your balance
You pay in UZS from a single balance: Payme, Click, Uzum, Rahmat, bank transfer under a contract for legal entities, or procurement via xarid.uzex.uz. Charges are made once a day at 00:00 and only for what is connected: mailboxes, storage and domains.
You can top up by any amount; to order a new service, your balance must cover at least 7 days of it. Rahmat payments are credited immediately; Payme, Click, Uzum and bank transfers within 1 business day. Any fee, if there is one, is shown by the payment system on its payment page.
Use the calculator to see what your setup costs and how many days a given amount will last.
When the balance reaches zero, the service is suspended and incoming mail may not be delivered. Keep an eye on the remaining balance — especially in the first month.
3Add your domain
Add your domain in the customer portal to launch the domain connection wizard. It shows exactly which DNS records your domain needs and checks them at the click of a button.
If your company already has a website on this domain, that's fine: the website and email work independently on the same domain because they use different DNS records.
4Add the DNS records
Open the DNS control panel at your registrar or DNS hosting provider and add the records from the table, replacing company.uz with your domain. The wizard shows the exact values, including your unique DKIM key — if anything differs from this table, follow the wizard.
| Type | Name (host) | Value | Purpose |
|---|---|---|---|
| MX | @ | mail.mcmail.uz, priority 10 | Where to deliver incoming mail |
| TXT | @ | v=spf1 mx a:mail.mcmail.uz ~all | SPF: who may send mail for the domain |
| TXT | dkim._domainkey | v=DKIM1; k=rsa; p=… — copy it from the wizard | DKIM: digital signature of messages |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:dmarc@company.uz | DMARC: what to do with spoofed mail |
| CNAME | autodiscover | mail.mcmail.uz | Automatic setup for Outlook and phones |
| CNAME | autoconfig | mail.mcmail.uz | Automatic setup for Thunderbird and other apps |
Things to watch out for:
- The
@symbol means the domain itself. Some panels ask you to leave the name field empty instead, or to type the full domain. - Delete the old MX records. If records of your previous email provider remain, some mail will keep going there.
- There must be only one SPF record. If a CRM, website or newsletter service also sends mail for your domain, merge everything into a single record — see our article on SPF.
- Leave website records alone (A, AAAA,
www) — email doesn't need them. - Start DMARC with
p=none: messages are not blocked, and you receive reports. After 2–4 weeks, once you're sure all mail passes the checks, tighten the policy toquarantine— see the DMARC article.
If email on the domain already runs with another provider, don't change the MX right away. First create the mailboxes in MCMail (step 6) and move the messages if needed, and switch the MX last — that way no message gets lost. It helps to lower the TTL of the records to 300–600 seconds in advance. For a detailed plan, see the article on email migration.
5Check DNS
Go back to the wizard and click the check button. New records usually become visible within minutes, but in some cases the update takes up to 24 hours — it depends on the TTL and on DNS server caches.
You can also check the records yourself. On Windows:
nslookup -type=mx company.uz
nslookup -type=txt company.uz
nslookup -type=txt dkim._domainkey.company.uzOn macOS and Linux:
dig MX company.uz +short
dig TXT company.uz +short
dig TXT _dmarc.company.uz +shortThe MX lookup should return mail.mcmail.uz. For more on checking records, see the article on MX records.
6Create employee mailboxes
There are two ways to create mailboxes:
- Manually, one at a time: address, employee name, password and quota.
- By CSV import, in bulk — including an export from Active Directory. Employees receive temporary passwords that must be changed at first sign-in. There is no live sync with AD: staff changes after the import are made separately.
This is also where you set up aliases such as info@ and sales@, forwarding and auto-replies — see aliases, forwarding and filters.
Turn on two-factor authentication right away for management and accounting mailboxes — it is the best protection against break-ins with a stolen password.
7Sign in to email
Webmail. Open mail.mcmail.uz. The login is the full email address, the password is the mailbox password. Mail, calendar and contacts work right in the browser — learn more about SOGo webmail.
Email apps. Thanks to the autodiscover and autoconfig records, Outlook, Thunderbird and phones usually configure themselves: just enter the address and password. If you need to set things up manually:
| Setting | Value |
|---|---|
| Incoming mail server (IMAP) | mail.mcmail.uz, port 993, SSL/TLS |
| Outgoing mail server (SMTP) | mail.mcmail.uz, port 465, SSL/TLS |
| Alternative SMTP port | 587, STARTTLS |
| Username | full email address |
Step-by-step guides: Outlook, Thunderbird, iPhone, iPad and Mac, Android.
8Test sending and receiving
- Send a message from the new mailbox to an external address, such as Gmail, and reply to it.
- In Gmail, open the message and choose Show original from the ⋮ menu.
- Make sure SPF, DKIM and DMARC all show PASS.
If a check fails, go back to step 4 and compare the record with the wizard. If messages land in spam, see why emails go to spam.
Common problems
| Symptom | What to check |
|---|---|
| The wizard can't see the records | Not enough time has passed — wait and check again. Make sure the records were added where the domain's DNS is actually served (its NS servers), not in a different panel |
| Mail still arrives at the old provider | Old MX records remain, or DNS caches haven't expired yet. Delete the extra MX records and wait for the TTL to run out |
| SPF: fail or permerror | The domain has two SPF records, or the record has a typo. Merge everything into a single v=spf1 … record |
| DKIM: fail | The key was copied incompletely or with extra spaces and quotes. Copy it from the wizard again |
| An app won't configure automatically | Check the autodiscover and autoconfig CNAME records, or set it up manually using the table in step 7 |
| Email stopped working for everyone | Check the balance: the service is suspended when it reaches zero |
Final checklist
- Account created on mcvps.uz and balance topped up
- Domain added in the connection wizard
- MX, SPF, DKIM, DMARC, autodiscover and autoconfig added; old MX records deleted
- The wizard confirmed all records
- Mailboxes created and employees have their passwords
- A test message passed SPF, DKIM and DMARC
- After 2–4 weeks, DMARC tightened to
quarantine
If something doesn't work, message support at @mycloudsupport or in the chat in your mcvps.uz client area with your domain and a screenshot of the wizard or the error text — we'll help you finish the setup.