X
X

Select Your Currency

₺ Türk Lirası $ US Dollar
X
X

Select Your Currency

₺ Türk Lirası $ US Dollar

Corporate Email Setup: A Secure Getting-Started Guide

HomepageArticlesTechnical GuidesCorporate Email Setup: A Secure Get...

Setting up corporate email involves more than creating an address with your domain. First, you need to configure the mail service’s sending and receiving servers, then correctly set up domain authentication records such as SPF, DKIM, and DMARC. These steps reduce the risk of messages landing in recipients’ spam folders and let you control which systems can send email on your behalf.

What is needed before setting up corporate email?

First, you must have permission to change the domain’s DNS records. If the domain is managed through a hosting panel, you need access to the relevant DNS or zone editor screen. If it is managed by a separate registrar, you need access to that company’s DNS panel. You also need an administrative account with the email provider to create mailboxes. A shared hosting panel may offer ready-made mailbox options; on a managed server, DNS, mail service, and security settings may be kept in different screens.

Before starting the setup, export the existing MX, TXT, and CNAME records or write their values down in a secure place. Randomly using MX records from multiple mail providers on the same domain can cause messages to be distributed across different systems. Therefore, first determine which service will accept incoming mail. If you need many users, shared calendars, or an archiving policy, verify that the provider supports these workflows instead of looking only at storage capacity.

How should corporate email DNS records be configured in order?

  1. Verify the domain with the mail service. Add your domain in the provider’s administration screen and enter the supplied verification TXT or CNAME record in the DNS panel. If verification does not complete, check whether the record name should be entered together with the domain name or in the format automatically added by the panel; do not move to the next step until the provider’s screen shows that verification is complete.
  2. Direct incoming mail through MX records. Add the MX server names and priority values supplied by the provider, taking the existing MX records into account. If you are migrating from an old service, first clarify the migration plan for existing mailboxes and messages; changing MX records affects which system receives new messages. Because DNS changes may take time to propagate, do not shut down the old system before verification is complete.
  3. Define sending authorization with SPF. SPF is a TXT record that identifies which sending servers are authorized to send on behalf of your domain. Add to the provider’s recommended existing SPF record; do not create a second SPF record for the same domain. If the website, newsletter service, or support application also sends messages, those sources must be included as authorized sources using the method described in the provider’s documentation.
  4. Publish the DKIM signing record. DKIM is a cryptographic signature that helps verify that an outgoing message was generated by a system authorized to act on behalf of your domain. The provider usually supplies a TXT or CNAME record with a selector name. After adding the record, wait for DKIM to become active in the administration screen. Changing the selector value or manually shortening the record’s content can break verification.
  5. Start the DMARC policy in a controlled manner. DMARC defines what the recipient server should do when SPF and DKIM results do not align with the domain. In the first stage, choosing a policy focused on collecting reports rather than enforcing an action can help reveal whether the website or third-party services have been overlooked. If an unexpected sender appears in the reports, investigate first whether the source genuinely belongs to you instead of immediately rejecting it.

Change only one record group at a time and wait for the result shown on the provider’s verification screen. For example, if the verification TXT record is visible but MX verification is failing, do not try to solve the problem by changing the SPF value; first examine the MX record names, priorities, and existing conflicts in the DNS panel. The expected result is for the domain to appear as verified and for the mail provider to report the relevant security record as active.

How can you test whether sending and receiving work?

First send a message between two mailboxes on the same domain, then send one to a test address at a different provider. It is not enough merely to see whether the message reaches the recipient; inspect the message headers for SPF and DKIM results, DMARC alignment, and whether the sender domain matches the domain you expect. The provider’s delivery report, the message-tracking screen in the administration panel, or the recipient service’s original message headers will normally show this evidence.

If receiving fails, first check whether an MX lookup points to the new provider. If the MX record is correct but a connection or mailbox error appears, verify that the user account has been created, the quota is not full, and the provider’s incoming-mail service is enabled. If messages land in the spam folder, assess the SPF and DKIM results separately, followed by DMARC alignment. Do not change multiple factors at once; otherwise, you will not be able to determine which correction was effective.

Suppose a company’s website and employee mailboxes use the same domain, but test messages show DKIM succeeding while SPF fails. In that case, instead of rebuilding DKIM, investigate whether the SPF record authorizes the website’s sending service. If the source genuinely belongs to the company, add the authorization recommended by the provider; otherwise, prevent the source from sending. Send the same test message again and confirm in the new time-stamped headers that the SPF result has changed.

Secure operation after setup and a rollback plan

After the initial configuration, repeat both an outbound message and an inbound message using a working mail account. Note the sending time so that the headers of the new message are not confused with those from earlier failed attempts. If the result has not improved, possible causes include the new DNS response not having propagated yet, a third-party sending tool not being included in the SPF or DKIM scope, or DMARC misalignment. Because these findings indicate different problems, target the relevant source instead of raising one general setting.

The old records you saved before making changes provide the basis for a safe rollback. If new messages are being routed incorrectly after an MX change and the old service is still accessible, you can temporarily restore the previous MX values by comparing the provider’s migration plan with the current records. However, during this process, be sure to check where newly arriving messages are being stored; reverting to the old setting may affect messages arriving at the new provider until the problem is resolved. If there is a problem with an SPF, DKIM, or DMARC record, restore only that record to its previous value; deleting or changing the entire DNS zone at once is not safe.

Before adding corporate email addresses to employees’ phones and desktop applications, enable strong passwords, multifactor authentication, and recovery methods to the extent offered by the provider. Applying a separate security policy to the administrative account is particularly important; changing a mailbox password alone is not enough to protect authority over the domain’s DNS. When comparing domain or hosting service options, you can also review the relevant service information on İyibirNet.

What should the next step be?

First create a test user and record the MX, SPF, DKIM, and DMARC statuses shown on the provider’s verification screen. Then check the headers of a new message sent to a different email service. If one of the four verification results fails, examine only the source of that record and its domain alignment; proceed according to the proven problem instead of changing all DNS settings.


Top