What professional technical support is (and why it matters)
Professional technical support isn’t just “someone to call when something breaks.” It means having specialists who plan, configure, document and monitor your company’s technology — website, servers, systems and communication — so problems are prevented, not just fixed.
Think of support as preventive maintenance for a car: you can drive without servicing for a while, but when trouble hits, it’s usually on the road, at the worst possible moment, with a costlier repair.
⏱️ Less downtime
Failures resolved quickly — or prevented before they affect customers.
🔐 More security
Protected accounts, controlled access and a domain shielded against fraud.
📚 Documented knowledge
Your company isn’t held hostage by a single employee or a former vendor.
Professional email: the perfect example
Few tasks show the value of support as clearly as setting up an email with your own domain, such as sales@yourcompany.com. It looks like just “creating an account,” but it involves choosing a service, changing DNS, authenticating the domain, migrating messages and testing everything.
Done right, the result is credibility, company control over accounts and messages reaching the inbox. Done wrong, the result is disappearing emails, proposals stuck in spam and scammers impersonating your brand. Here’s the complete step-by-step.
Choosing an email service
The first step is deciding where your mailboxes will live. There are three main options:
| Criterion | Productivity suites | Hosting email | Specialized providers |
|---|---|---|---|
| Examples | Google Workspace, Microsoft 365 | Email included with cPanel, Plesk and similar | Zoho Mail, Proton and others |
| Cost | Per user/month | Usually included | Varies, generally mid-range |
| Features | Calendar, drive and meetings | Limited to the plan | Good, email-focused |
| Antispam and security | Very robust | Depends on the server | Generally robust |
| Risk of blocking caused by others | Low | Higher on shared servers | Low |
| Best for | Highly collaborative teams | Few accounts and light use | Reliable email without a full suite |
General assessment. Features, limits and pricing change frequently; check each service’s current terms.
Website and email don’t need to be in the same place
It’s common to host the website on one server and email on another service. The domain’s DNS points each one to the right place — and keeping them separate prevents a website issue from taking down your email.
Before you start
- Domain registered in the company’s name (for .com.br domains, at Registro.br), not in the name of a former vendor or employee.
- Access to the active DNS panel, which may be at the registrar, the hosting provider or services like Cloudflare. It’s identified by the domain’s DNS servers (nameservers).
- A list of the accounts to create and who will use each one.
- A migration plan, if you already have email elsewhere.
nslookup -type=NS yourcompany.com # Sample responses: # nameserver = a.sec.dns.br → DNS at Registro.br # nameserver = ana.ns.cloudflare.com → DNS at Cloudflare
Every change in this guide must be made in the panel indicated by the nameservers. Changing records anywhere else will have no effect.
Verifying the domain and creating accounts
When you sign up, the service will ask you to add and verify the domain. Verification proves you own it and is usually done with a temporary TXT (or CNAME) record containing a code provided by the service.
👤 Personal accounts
Adopt a single pattern, such as first.last@ or first@.
🏷️ Aliases and groups
contact@ and billing@ can be aliases or groups that deliver to several people, with no extra account cost.
🔑 Passwords and 2FA
Require strong passwords and enable two-step verification. A hacked mailbox is a gateway to scams.
📮 Technical addresses
Reserve accounts like postmaster@ and a mailbox for DMARC reports.
Understanding email DNS
DNS works like the internet’s phone book: it translates names into addresses and stores information about the domain. For email, it answers two questions: where to deliver incoming messages and how to tell whether an outgoing message is legitimate.
TTL is the time, in seconds, that other servers cache the information before checking again. Propagation is the time until everyone sees the change — from minutes to a few hours and, rarely, up to 48 hours.
Configuring MX, SPF, DKIM and DMARC
The values below are illustrative
Each service provides its own servers, priorities and keys, usually on screens like “DNS settings” or “Domain authentication.” Field names also vary: “Name,” “Host” or “Entry” usually mean the same thing. Always use your provider’s values.
1. MX: where emails are received
The MX record points to the server that receives the domain’s messages. The priority sets the order: the lowest number is tried first; the others act as backups.
# Type Name Priority Value TTL
MX @ 10 mx1.provedor-exemplo.com 3600
MX @ 20 mx2.provedor-exemplo.com 3600
- @ represents the domain itself; some panels ask for an empty field or the full domain.
- Remove old MX records: mixing records sends some emails to one place and some to another.
- The MX value must be a server name, never an IP address.
2. SPF: who can send on behalf of the domain
SPF is a TXT record listing the servers authorized to send email from your domain. If your website, a system or an email marketing tool also sends messages, they all need to be in the same record.
TXT @ "v=spf1 include:_spf.provedor-exemplo.com ~all"
# Provider + marketing tool:
TXT @ "v=spf1 include:_spf.provedor-exemplo.com include:spf.marketing-exemplo.com ~all"
- ~all flags anyone not on the list as suspicious; -all recommends rejection. Start with ~all.
- Only one SPF record per domain. Two v=spf1 records invalidate both.
- 10 DNS lookup limit: too many include entries can exceed it.
3. DKIM: the digital signature of your messages
DKIM adds a cryptographic signature to every email. The receiving server uses a public key published in your DNS to confirm the message really came from your domain and wasn’t altered. Generate the key in the service’s panel, publish it in DNS and then enable signing in the panel — a step that’s often forgotten.
TXT seletor1._domainkey "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A..." CNAME seletor1._domainkey seletor1.dkim.provedor-exemplo.com
The selector is a name that identifies the key and lets you have several at once, one for each service that sends email.
4. DMARC: the policy for failures
DMARC ties SPF and DKIM together and tells servers what to do when a message fails verification. It also sends reports on who is using your domain — including fraud attempts.
# Phase 1 — monitor only (2 to 4 weeks) TXT _dmarc "v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com" # Phase 2 — send failures to spam TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:dmarc@yourcompany.com" # Phase 3 — reject failures TXT _dmarc "v=DMARC1; p=reject; rua=mailto:dmarc@yourcompany.com"
Move to the next phase only after reviewing the reports and confirming that SPF or DKIM is aligned with the sender’s domain on all legitimate mail.
Records summary
| Record | Type | Name | Purpose |
|---|---|---|---|
| MX | MX | @ | Points to the receiving server |
| SPF | TXT | @ | Lists who can send |
| DKIM | TXT or CNAME | selector._domainkey | Publishes the signing key |
| DMARC | TXT | _dmarc | Sets policy and reporting |
| Verification | TXT or CNAME | Specified by the provider | Proves ownership |
Accessing email on desktop and mobile
Besides webmail, you can use Outlook, Gmail, Apple Mail or Thunderbird. Prefer IMAP, which keeps messages synced across all devices; POP3 downloads to a single device and is less suitable today. Sending uses authenticated SMTP.
IMAP imap.provedor-exemplo.com port 993 SSL/TLS POP3 pop.provedor-exemplo.com port 995 SSL/TLS SMTP smtp.provedor-exemplo.com port 465 SSL/TLS or 587 STARTTLS Username: full address (e.g., maria@yourcompany.com)
With two-step verification enabled, some apps require an app password, generated in the service’s panel.
How to test
1. Check the published records
nslookup -type=MX yourcompany.com nslookup -type=TXT yourcompany.com # SPF nslookup -type=TXT seletor1._domainkey.yourcompany.com # DKIM nslookup -type=TXT _dmarc.yourcompany.com # DMARC dig MX yourcompany.com +short # Linux/macOS
2. Send, receive and read the header
Exchange messages with an external account. In Gmail, open the received email and click “Show original”:
dkim=pass header.d=yourcompany.com spf=pass smtp.mailfrom=maria@yourcompany.com dmarc=pass header.from=yourcompany.com # Warning signs: spf=softfail → server not in SPF dkim=none → signing not enabled dmarc=fail → no alignment
3. Use diagnostic tools
DNS checkers and spam testers flag missing records, duplicate SPF, DKIM failures and blocklist listings. Test again after every change.
Common problems and solutions
📭 Emails stopped arriving after the switch
An old MX is still published, or the change was made in the wrong DNS panel. Check the nameservers, remove old MX records and wait for the TTL.
Wrong MX or DNSnslookup🗑️ Sent messages land in spam
Missing SPF, DKIM not enabled or DMARC without alignment. Content with lots of links or only images also hurts.
Incomplete authenticationRead header🧾 Website form doesn’t send
The site uses the server’s built-in mail function, outside SPF and without DKIM. Configure sending via authenticated SMTP or a transactional service included in SPF.
Unauthenticated sendingAuthenticated SMTP⚔️ Two SPF records
When adding a tool, someone creates another v=spf1 and both become invalid. Merge them into one.
Duplicate SPFOne record☁️ Cloudflare proxy on email subdomains
Subdomains like mail. stop working with the orange cloud enabled. Use “DNS only.”
Proxy enabledDNS only✂️ Truncated DKIM key
Long keys can get cut off when pasted or may need to be split into chunks of up to 255 characters. Compare with the original value.
Incomplete valueDouble-check🔁 Forwarded emails fail SPF
The intermediate server isn’t in the sender’s SPF. DKIM survives forwarding and keeps DMARC passing.
SPF limitationDKIM fixes itWhat about the website?
Changing email records doesn’t affect the website, as long as the A, AAAA and CNAME records are preserved. Export or write down all records before you start.
When to call in professional support
Setting things up is one step; maintaining them is another. New tools need to be added to SPF, DMARC should progress to reject, reports need reviewing and former employees’ accounts must be deactivated. This is where professional technical support pays for itself.
🚩 Signs you need it
Emails in spam, a provider migration on the horizon, nobody knows where the DNS is, forms that don’t send or suspected scams using your brand.
✅ What good support delivers
The right service choice, authenticated DNS, loss-free migration, documented access and continuous monitoring.
WD Seven works on exactly these points: guiding the choice of service based on company size, configuring DNS with full authentication, migrating messages without disrupting communication and integrating website forms with authenticated sending.
Are your emails landing in spam?
With Maintenance & Support and Cloud & DevOps, WD Seven reviews your DNS and fixes your authentication.
Frequently asked questions
Yes, with time and attention to detail. The risk lies in DNS mistakes, which can stop incoming mail or send messages to spam. Professional support reduces that risk and speeds up the process.
From a few minutes to a few hours after the DNS change and, rarely, up to 48 hours. Lowering the TTL a few days before a migration speeds up the switch.
Not if the migration is planned: import via IMAP before switching the MX and run a final sync afterward.
Technically no, but in practice yes. Major providers like Gmail, Yahoo and Outlook already require these records from higher-volume senders, and without them the chance of landing in spam rises sharply.
Yes. Virtually every service works with these apps, via IMAP/SMTP or through the provider’s own app.
Conclusion and checklist
Professional email isn’t complicated, but it demands order and precision — and it’s a good illustration of why professional technical support matters: invisible details determine whether your communication reaches the customer or not.
Choose the email service
Consider users, storage, security and budget.
Locate the active DNS
Check the nameservers and save the current records.
Verify the domain and create accounts
Address pattern, aliases, strong passwords and 2FA.
Migrate old messages
Via IMAP, before switching the MX.
Configure the MX
Use the provider’s values and remove the old ones.
Publish a single SPF record
Include every service that sends, starting with ~all.
Publish and enable DKIM
Record in DNS and signing turned on in the panel.
Create DMARC with p=none
Move to quarantine and reject after reviewing reports.
Test sending, receiving and headers
Confirm spf=pass, dkim=pass and dmarc=pass.
Fix forms and keep monitoring
Authenticated SMTP on the website and periodic reviews with specialized support.