Suped

How to set up DMARC/DKIM/SPF for MailCore

Published 22 Nov 2026
Updated 22 Nov 2026
10 min read
Summarize with
MailCore email authentication setup with SPF, DKIM, and DMARC.
Set up MailCore by provisioning your sending domain, publishing the operator-supplied SPF and DKIM settings, and adding a DMARC TXT record at _dmarc. Start a new DMARC deployment with p=none and a working report address. Keep an existing quarantine or reject policy, then verify a real message sent through MailCore.
I check the envelope sender and DKIM signing domain before changing DNS. MailCore provides hosting for ISPs and web portals, so the operator managing your account must confirm the settings for your deployment. A passing SPF or DKIM result must also have domain alignment with the visible From address for DMARC to pass.

Add your domain

Use the MailCore Backoffice supplied by your hosting operator, or have the operator provision the domain for you. Webmail access alone does not establish administrator access.
MailCore's public product information describes Backoffice administration and support tickets, but does not document a universal domain-verification wizard. Obtain the account-specific DNS instructions before publishing records.
  1. Open your account. Sign in to your operator's MailCore Backoffice. If domain administration is unavailable, open a support ticket through the operator.
  2. Request the domain. Supply the exact domain used in your From addresses, such as example.com. Ask the operator to provision it and confirm which sending subdomains need separate setup.
  3. Verify ownership. Complete the operator's ownership check. If a DNS challenge is required, publish its exact TXT or CNAME name and value, then request verification.
  4. Collect the settings. Request the outbound SPF mechanism, envelope sender domain, DKIM selector, DNS record type, and public key or CNAME target. Ask for DKIM signing with your domain.
  5. Confirm activation. Have the operator confirm the domain and a test mailbox are active. Save the current DNS records before editing them.
Keep inbound routing separate
MX records control incoming delivery. Change them only as part of a planned mailbox migration using your operator's instructions. Adding SPF, DKIM, or DMARC does not require an MX change.

Set up SPF

MailCore supports return path alignment. Ask your operator to send with an envelope sender under your domain, then authorize MailCore at that envelope sender domain. SPF checks this address, not the visible From address or Reply-To.
Check the current SPF policy before editing it. For From addresses at example.com, an envelope sender at example.com matches directly; bounce.example.com works under relaxed SPF alignment. Strict SPF alignment requires an exact domain match.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
Use the SPF checker above on the actual envelope sender domain. Check for duplicate SPF policies and the 10-term DNS lookup limit, including nested includes. A subdomain does not inherit its parent's SPF record.
A valid SPF record alone does not prove that MailCore uses the intended envelope sender. Verify smtp.mailfrom in a receiving server's Authentication-Results header after sending a fresh message.
  1. Confirm authorization. Ask your MailCore operator for the current SPF include or outbound IP authorization. Use include:spf.mailcore.net only if the operator confirms it for your service.
  2. Edit one policy. At the envelope sender hostname, update the existing TXT value beginning v=spf1. If none exists, create one using the operator's instructions.
  3. Preserve other senders. Merge MailCore's approved mechanism before the final all mechanism. Keep other authorized senders and retain a single final all mechanism.
  4. Check the result. Recheck DNS after the previous TTL expires, then send through MailCore and confirm spf=pass with the expected smtp.mailfrom domain.
The example below authorizes only MailCore. Publish it only if your operator confirms spf.mailcore.net, the envelope sender is at example.com, and no other service sends at that hostname. Replace example.com with your domain.
Conditional MailCore-only SPF exampledns
example.com. 3600 IN TXT "v=spf1 include:spf.mailcore.net -all"
Check domain alignment
If smtp.mailfrom uses a provider-owned domain, adding an include to your own domain does not fix SPF alignment. Ask the operator to enable the matching return path. A message still passes DMARC when DKIM passes with a matching signing domain, even if SPF alignment fails.

Set up DKIM

MailCore must sign outgoing messages with your domain and hold the corresponding private key. Publishing an unrelated DKIM public key does not enable signing.
I use the selector supplied for the account rather than guessing a selector such as default. A received DKIM-Signature also identifies the selector in s= and the signing domain in d=.
  1. Request signing. Ask your MailCore operator to enable DKIM for your sending domain and supply the exact selector, record type, and DNS value.
  2. Publish the record. Create the supplied TXT or CNAME at the supplied selector._domainkey hostname. Paste the complete public key or CNAME target. Keep the private key with MailCore.
  3. Confirm DNS. Check the exact hostname without duplicating your domain suffix. For a CNAME, verify both the alias and the public key at its destination.
  4. Activate and test. Ask the operator to confirm signing is active. Send a new message and require dkim=pass with header.d matching the From domain under your DMARC alignment mode.
Replace SELECTOR below with the operator-issued selector and example.com with the signing domain. A DNS response proves publication; the receiving server's dkim=pass result proves that the message signature verifies.
Check the supplied DKIM selectorbash
dig +short CNAME SELECTOR._domainkey.example.com dig +short TXT SELECTOR._domainkey.example.com
Preserve the full public key
A long TXT record can contain multiple quoted character strings within one DNS record; DNS joins them. Do not create separate competing key records or add whitespace inside the key. Retain an old selector during rotation until messages signed with it have cleared delivery queues.

Set up DMARC

Publish DMARC in your authoritative DNS, even when MailCore manages the mailboxes. For From addresses at example.com, the record name is _dmarc.example.com, often entered as _dmarc in the DNS panel.
Check for an existing policy first. If the domain already uses p=quarantine or p=reject, keep it and fix MailCore's authentication within that policy. For a new deployment, p=none requests monitoring without DMARC-based enforcement.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
Use the DMARC checker above to inspect the current policy and report destinations. Publish a single DMARC TXT record at each policy hostname. If an existing record is present, edit it rather than adding another.
Use our DMARC record generator to build the record. The example below uses a placeholder report mailbox: replace dmarc@example.com with your working report destination before publishing it.
  1. Create the destination. Choose a mailbox or reporting destination that accepts aggregate DMARC reports. For a destination on another domain, confirm external reporting authorization is configured.
  2. Publish the policy. For a domain without DMARC, add a TXT record at _dmarc using the monitoring value below, with your real reporting address.
  3. Preserve existing settings. Keep an established enforcement policy and existing reporting destinations. Do not overwrite intentional subdomain or alignment settings with a generic example.
  4. Verify publication. Check the policy hostname after the previous TTL expires. Send a fresh MailCore message and confirm the receiving server reports dmarc=pass.
Initial DMARC TXT value at _dmarc.example.comdns
v=DMARC1; p=none; rua=mailto:dmarc@example.com
DMARC passes when either SPF passes with SPF alignment or a DKIM signature passes with DKIM alignment. Both mechanisms are useful, particularly because forwarding often breaks SPF while leaving an unchanged DKIM signature valid.

Verify and troubleshoot

I verify the complete sending path before treating a DNS change as finished. Send through the MailCore webmail or SMTP route used in production, using your actual From domain.
The email tester below supplies a test address. Send a message to it through MailCore, then open the diagnosis to inspect authentication and domain matching. Repeat the test for each distinct sending route, including applications that use MailCore SMTP.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
Look for dmarc=pass and identify which mechanism provides it. For SPF, inspect smtp.mailfrom; for DKIM, inspect header.d. Neither a matching Reply-To nor a valid signature from an unrelated provider domain establishes DMARC alignment.
A passing test covers that message and sending route. Repeat after changing DNS or MailCore settings, and use aggregate reports to find failures across the rest of your traffic. Authentication success does not guarantee inbox placement.
  1. SPF errors. For permerror, remove duplicate SPF policies or reduce excessive lookup terms. For fail, confirm the sending IP is authorized at the smtp.mailfrom domain.
  2. DKIM missing. If the result is dkim=none, ask MailCore to confirm signing is enabled on the route you tested. DNS publication alone does not turn signing on.
  3. DKIM invalid. Compare the message's s= and d= values with DNS. Check for a truncated key, a wrong CNAME target, or message changes after signing.
  4. DMARC failures. If authentication passes but DMARC fails, compare the authenticated domains with the visible From domain and the policy's alignment settings.
  5. Escalate precisely. Give the operator the timestamp, sending IP, message ID, and relevant authentication headers. Request a new test after the operator fixes the outbound route.

Result

Next check

SPF permerror
Duplicates / lookups
SPF fail
Outbound authorization
DKIM none
MailCore signing
DKIM fail
Selector / key / changes
DMARC fail
Domain alignment
Use the receiving server's results to choose the next check.

Get alerted when it breaks

Suped is our DMARC platform. Its DMARC monitoring connects MailCore authentication failures with source details and steps to fix them, so ongoing checks do not depend on manually opening report files.
Aggregate reports usually arrive daily rather than with each message. Suped's alerts depend on received reporting data; use a fresh email test for immediate verification after a change.
  1. Enable issue notifications. Configure Suped's Issues detected notifications for the people responsible for MailCore and DNS changes.
  2. Review unfamiliar sources. Enable Sending sources need verification notifications. Confirm ownership of a source before marking it verified; an rDNS match alone is insufficient.
  3. Investigate the failure. Filter DMARC records by MailCore source, sending IP, or reporter. Open the detail view to compare SPF and DKIM results with domain alignment.
  4. Check recent changes. Use Suped's DNS history to compare record values around the failure, then follow the issue's steps to fix the configuration.
  5. Confirm recovery. Send another MailCore test message and review subsequent aggregate reports. Configure DMARC summary emails to keep recurring failures visible.

Secure your domain with p=reject

Move to p=reject after every legitimate sender has a reliable DMARC pass path. I base that decision on source-level results across a complete business sending cycle, including infrequent invoices or notifications.
Suped supports that work through source verification, authentication diagnostics, and policy management. Review legitimate MailCore traffic separately from unauthorized traffic; a high overall pass rate alone does not establish readiness.
  1. Inventory every sender. Review MailCore alongside every other service using your From domain. Confirm legitimate sources with the people who operate them.
  2. Fix legitimate failures. Require working DKIM with a matching domain on MailCore, and configure the matching return path for SPF. Review forwarding and indirect delivery cases before enforcement.
  3. Stage enforcement. Once authorized traffic is understood, move a monitoring policy to p=quarantine and review the results before p=reject. Keep an existing enforcing policy during MailCore setup.
  4. Keep reporting active. Retain a working rua destination and Suped alerts after enforcement. Check subdomains and intentional policy overrides before assuming the parent policy covers every sending domain.
Change the policy in your existing record while preserving its other intentional settings. The minimal example below is for a verified deployment; replace the placeholder reporting address before use.
DMARC TXT value after authentication is verifieddns
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Choose how to manage the policy according to who owns DNS. Suped's Hosted DMARC lets the team manage policy in the dashboard after its initial DNS configuration, while continuing to inspect MailCore's authentication results.
Direct DNS management
Edit the TXT policy at your DNS provider. Coordinate policy changes with the DNS owner and verify each published value.
Suped Hosted DMARC
After initial DNS setup, manage policy in Suped without repeated DNS edits. Use monitoring data to decide when to enforce.
A reject policy requests rejection when DMARC fails; receiving systems retain their own handling decisions. It addresses unauthorized use of your From domain, not lookalike domains or misuse of an authenticated mailbox.

Frequency asked questions

Get the current authorization from your MailCore operator. If it confirms spf.mailcore.net for your deployment, add include:spf.mailcore.net to the single SPF policy at the envelope sender domain. Preserve other authorized senders; the MailCore-only example is unsuitable for a hostname used by additional services.

Use the selector issued by your MailCore operator. A received message also identifies its selector in s= and its signing domain in d= within DKIM-Signature. Do not assume one selector applies to every MailCore deployment.

DMARC needs one passing mechanism with domain alignment. If DKIM passes with the correct signing domain, DMARC passes even when SPF alignment fails. This occurs with provider-owned return paths or some forwarding routes. For MailCore, ask the operator to configure its supported return path alignment rather than expecting an SPF include alone to change the envelope sender.

Suped associates the .mailcore.net rDNS suffix with MailCore infrastructure. Treat it as a source-identification clue, then confirm the sending IP and authentication results against your account. Shared infrastructure or forwarded mail does not prove that your organization authorized the original message.

Keep an existing p=reject or p=quarantine policy while configuring MailCore. Fix its SPF and DKIM settings, then verify a fresh message passes DMARC. The p=none starting record is for domains without an established enforcing policy.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing