Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Sending email from OPS-COM is a key element of communicating with your clients.  This article offers information related to the setup of a mail sending domain on our preferred mail partner Mailgun

Table of Contents


titleSimple SPF Security

Add the following to your SPF record (in DNS) to allow OPS-COM servers to send email on your domains behalf.

Code Block

Please note that this is only first line generalized security.  More details here

Communicating with Clients

One of the key features of your OperationsCommander installation is the ease of communicating with your clients.  This communication may be outgoing messages related to purchases, notifications and even as part of the appeals process.

Why Mailgun

We selected Mailgun as our preferred email partner due to the ease of use of their APIs and their long standing success in the email space.  That together with their tools to track and report on sent emails made them an ideal candidate for email management.

What to Expect Without Mailgun

Within the OPS-COM system configuration, reply-to email addresses can be recorded.  One such email might be such that any email receipts sent will appear to come from this email address.

Due to the email being sent from a system, the email may be marked as spam or carry a "on behalf of" header to let the client know that the email was not sent from a system.

With a few simple DNS updates, it is possible to recognize the Mailgun server as a valid email sender for

Using your own API offers an even better level of service so that you can inspect emails sent by OPS-COM, and this is the recommended configuration

titleWhy Do I See On Behalf Of in My Email

Using Your Own Mailgun Account


This is the preferred method and allows you to self manage your email settings and communications.

You may create a new or use an existing Mailgun account.  Please send the associated API key to OPS-COM support.

API keys can be created and found in the Mailgun site under:   Domain settings  →  Sending API Keys

* To aid in technical support related to email please invite OPS-COM support ( as a Developer level user.

Integrating Mailgun to Your Installation

Within the OPS-COM administrative interface, select System Configuration → Third Party

Using the OPS-COM Mailgun Account

This setup will enable OperationsCommander to send email on behalf of your domain.  It will remove the "on behalf of" notation that may be seen in emails that are not setup properly.


This setup requires access to DNS records and some more advanced features related to email communication.

Required DNS Records

  1. Please send a copy of your domain DKIM to OPS-COM support. 
    1. please also include your domain 
  2. Add the following DNS records to your DNS server.
TXTmg.<your domain>v=spf1 ~allThis adds an SPF record for Mailgun
TXTsmtp._domainkey.<your domain>your DKIM keyThe DKIM key used with your domain

SPF = Sender Policy Framework

DKIM = Domain Key Identified Mail

Optional DNS Records

Mailgun recommends adding these values even if only sending emails.  If they are not included in your DNS records, everything should still work.

MXmg.<your domain>10mxa.mailgun.orgMX is a mail exchange (optional)
MXmg.<your domain>10mxb.mailgun.orgMX is a mail exchange (optional)

Tracking opens, clicks is not currently supported in OperationsCommander.  Once that feature is added, this entry will allow for reporting.

CNAMEemail.<your domain>mailgun.orgused for tracking opens, clicks

Related Pages

Content by Label
cqllabel in ("mail","email","communication","mailgun") and space = currentSpace()

Show If

titleSupport Agent Notes

Our preference is for clients to create their own API keys under their own Mailgun account.