Skip to main content

Nectar Comms Email Setup for IT Teams

Written by Marisa Crowder

Nectar Comms sends email through our own delivery infrastructure, so a few settings in your email environment help every Comm land in the inbox, display correctly, and report accurate analytics. This guide brings every step into one place, with one checklist your team can work through.

Most teams only need a few of the sections below. Answer three questions first, then skip anything that doesn't apply.


Before you start

Question

If yes

If no

Do you use an inbound security gateway (Mimecast, Proofpoint, Barracuda)?

Complete Step 3 for your gateway

Skip Step 3

Is your email hosted on Google Workspace or Microsoft 365?

Complete Step 4 for your provider

Skip Step 4

Will Comms send from your company's domain (for example, [email protected])?

Complete Step 2

Skip Step 2. Comms will send from [email protected]

Everyone completes Step 1 (safelisting) and Step 5 (verification).

Who's involved: Your Comms admin starts the custom domain setup in Nectar. Your IT or email security team makes the changes in your DNS, gateway, and email provider. A quick kickoff conversation between the two usually saves time later.

Timing: Most changes take minutes to make. Many IT teams run changes like these through an internal review, so we recommend starting a couple of weeks before your first company-wide send.


Quick reference

Every value you'll need is here. The steps below point back to this table.

Item

Value

Used in

Sending IP

159.183.82.50

Steps 1, 3 and 4

Sending address

[email protected], or your own address once your custom domain is verified

Steps 1 and 3

Image hosts

comms-email-editor-storage.s3.amazonaws.com and *.cloudinary.com

Steps 1, 3 and 4

Link domains

app.nectarhr.com, nectarhr.com

Step 3

SPF include

include:sendgrid.net

Step 2, only if your SPF record ends in -all

For the full list of addresses and IPs used across all of Nectar (Recognition, rewards and support mail), see What emails and IPs should I whitelist for Nectar?


Setup checklist

Work top to bottom and skip any group that doesn't apply. Each item links to its step below.

Step 1: Safelist Nectar (everyone)

  • Safelist the sending IP and sending address

  • Trust both image hosts so images and open tracking load

Step 2: Custom domain (only if sending from your own domain)

  • Comms admin adds the domain in Nectar

  • IT publishes the four DNS records in your public DNS zone

  • IT checks whether your SPF record ends in -all, and adds include:sendgrid.net if it does

  • Comms admin clicks Verify DNS Records in Nectar

Step 3: Security gateway (only the one you use)

  • Mimecast: Permitted Senders

  • Mimecast: Anti-Spoofing bypass (custom domain only)

  • Mimecast: Impersonation Protection bypass

  • Mimecast: URL Protection bypass

  • Mimecast: CyberGraph bypass

  • Mimecast: Message Sanitization (content) bypass

  • Proofpoint: Safe Sender or Organizational Safe List

  • Proofpoint: Non-Throttled Hosts

  • Barracuda: IP exemption

  • Barracuda: Microsoft 365 backup connector (if Microsoft 365 is your fallback)

Step 4: Email provider (only the one you use)

  • Google Workspace: confirm your gateway is set as the inbound gateway (gateway users only)

  • Google Workspace: add the sending IP to the email allowlist (optional)

  • Microsoft 365: allow the sending IP on your inbound connector (gateway users only)

  • Microsoft 365: allow images from both image hosts

  • Microsoft 365: add a mail flow rule to remove the "External" tag (custom domain only)

  • Microsoft 365 (if signatures show up on Comms): scope any automatic signature rule so it skips Comms (custom domain only)

Step 5: Verify (everyone)

  • Send the test template, then a small real send

  • Confirm SPF, DKIM and DMARC show PASS

  • Confirm your gateway delivered the message without holding or rewriting it

  • Check images, links and special characters on desktop, web and mobile

  • Check that analytics look realistic


Step 1: Safelist Nectar

Safelisting tells your email security that Comms mail is expected. Everyone completes this step.

  1. Add the sending IP (159.183.82.50) and sending address ([email protected], or your own address) to your allowed senders. If you use a security gateway, you'll do this inside Step 3. If you don't, add them in your email provider (Step 4).

  2. Trust both image hosts (comms-email-editor-storage.s3.amazonaws.com and *.cloudinary.com). Images in Comms, including the tiny image used to count opens, load from these hosts.

Using a VPN? Allow the image hosts on your VPN too. Otherwise images may not load for employees connected to it.


Step 2: Set up your custom domain

Only needed if Comms will send from your company's domain. Until your domain shows Verified, Comms sends from [email protected].

Before you begin

  • Root domain only. Comms sends from your root domain (yourcompany.com). Subdomains like comms.yourcompany.com aren't supported.

  • Public DNS. Records must be in a public DNS zone so they can be verified from the internet. Records added only to an internal zone (for example, BlueCat) won't verify.

  • Check your SPF record. SPF changes are optional for most teams, because DKIM confirms that Comms is allowed to send for your domain. The one exception: if your SPF record ends in -all, add include:sendgrid.net or receiving servers will reject Comms mail.

    • Before: v=spf1 include:spf.protection.outlook.com -all

    • After: v=spf1 include:spf.protection.outlook.com include:sendgrid.net -all

Steps

  1. Comms admin: In Nectar, go to Workspace Settings > DNS Settings and click Add Custom Domain.

  2. Comms admin: Select your DNS provider, enter your domain in the From Domain field, and click Continue. Nectar generates four records.

  3. IT: Publish all four records in your public DNS zone: three CNAME records (including your DKIM keys) and one DMARC TXT record. If your domain already has a _dmarc record, keep yours and skip ours. You only need one.

  4. IT: If your SPF record ends in -all, add include:sendgrid.net (see above). SPF changes usually take effect within 1 to 2 hours.

  5. Comms admin: Back in Nectar, check I have installed the records below and click Verify DNS Records.

Verification usually completes within minutes but can take up to 72 hours. Keep the records in place and check back rather than deleting them and starting over.

If verification doesn't complete

What you see

What to try

Records look right but won't verify

Some DNS providers (such as Squarespace and BlueCat) add your domain to the end of each hostname. Add a trailing period to the hostname, for example em1234.yourdomain.com.

A DKIM conflict

If your organization already uses SendGrid for another tool, contact Nectar Support so we can assign unique keys.

Still unverified after 72 hours

Double-check each record against Nectar line by line, or use a public DNS lookup tool to confirm the records are visible.


Step 3: Configure your security gateway

Gateways scan, rewrite and sometimes hold incoming mail. These settings let Comms arrive as designed. Open only the section for the gateway you use. No gateway? Skip to Step 4.

Mimecast

Each Mimecast policy is separate, so allowing Nectar in one doesn't carry over to the others. Create all six.

Settings shared by every policy below. Under Validity, set:

  • Enable/Disable: Enable

  • Set Policy as Perpetual: Always On

  • Policy Override: checked, so this policy is applied ahead of broader policies of the same type

  • Source IP Ranges: 159.183.82.50

For the five Gateway policies, go to Administration > Gateway > Policies, select the policy type, and click New Policy. Name each one something easy to find, such as "Nectar Comms bypass."

Policy

Why it matters

Option

Emails From

Emails To

Permitted Senders

Lets Comms through spam checks

Permitted Sender Policy: Permit Sender

Addresses Based On: The Return Address (Email Envelope From); Applies From: External Addresses

Applies To: Internal Addresses

Anti-Spoofing (custom domain only)

Keeps Mimecast from blocking Comms sent from your own domain

Select Option: Take No Action

Addresses Based On: Both; Applies From: Everyone

Applies To: Everyone

Impersonation Protection Bypass

Prevents impersonation warnings and tags

Create a new policy (no option to set)

Addresses Based On: The Return Address (Email Envelope From); Applies From: External Addresses

Applies To: Internal Addresses

URL Protection Bypass

Stops link rewriting and pre-scanning, which can register clicks no one made

Select Option: Disable URL Protection

Addresses Based On: The Message From Address (Message Header); Applies From: Everyone

Applies To: Internal Addresses

Message Sanitization

Prevents broken formatting and garbled characters (like ? or é), especially in translated Comms

Select Option: Take No Action

Addresses Based On: The Return Address; Applies From: External Addresses

Applies To: Internal Addresses

If the Anti-Spoofing policy asks for a hostname instead of an IP, use o1.ptr3807.nectarhr.com. This is rarely needed.

CyberGraph lives in a different menu. It removes tracking images and adds banners, which hides opens and can affect images.

  1. Go to Administration > Services > CyberGraph and click Create New Policy.

  2. Name the policy, set Dynamic Banners to Disabled and Trackers to Disabled, and enable Policy Override.

  3. Under Sender and Recipient Rule, set From to Everyone and To to Everyone.

  4. Under Source IP Ranges, enter 159.183.82.50.

  5. Confirm Policy Status is Enabled and click Create Policy.

Proofpoint

Proofpoint needs two settings. A safelist stops Comms from being blocked, and the Non-Throttled Hosts setting stops large sends from being delayed for hours.

1. Safelist the sending IP

Proofpoint Essentials:

  1. Expand Security Settings and click Sender Lists.

  2. Add 159.183.82.50 to the Safe Sender List and click Save.

Proofpoint Enterprise (Hosted):

  1. Go to Email Protection > Spam Detection > Organizational Safe List and click Add.

  2. Set Filter Type to Sender Hostname, Operator to Equals, and Value to 159.183.82.50.

  3. Click Save Changes.

2. Add Nectar to Non-Throttled Hosts

  1. Go to Email Firewall > SMTP Rate Control > Non-Throttled Hosts and click Add.

  2. Enter 159.183.82.50 and click Save.

  3. If your Proofpoint deployment has more than one server (shown at the top of the page), apply the rule to each one.

Already seeing delayed sends? Go to Email Firewall > SMTP Rate Control > Connections, search for 159.183.82.50, and add that hostname and IP to Non-Throttled Hosts. Delayed messages retry automatically for up to 72 hours, so there's no need to resend.

Barracuda

Barracuda Email Security Service (cloud):

  1. In Barracuda Cloud Control, go to Email Security > Inbound Settings > IP Address Policies.

  2. Under IP Blocking / Exemption, enter 159.183.82.50 with netmask 255.255.255.255.

  3. Add a comment such as "Nectar Comms" and click Add.

Barracuda Email Security Gateway (on-premises):

  1. Go to BLOCK/ACCEPT > IP Filters.

  2. Under Allowed IP/Range, enter 159.183.82.50 with netmask 255.255.255.255.

  3. Add a comment and click Add.

If Microsoft 365 is your backup mail route: Some setups send mail straight to Microsoft 365 when Barracuda is briefly unreachable. Add 159.183.82.50 to the allowed list on your Microsoft 365 partner connector so Comms still delivers if that happens.

Other gateways or no gateway

Using a different gateway? Look for equivalent settings: an IP or sender allowlist, a link-rewriting or URL-scanning bypass, a tracking-pixel or banner bypass, a content-rewriting bypass, and a rate-limit exemption. Apply each to 159.183.82.50.

No gateway? Complete Step 4 for your email provider.


Step 4: Configure your email provider

Open the section for the provider that hosts your mailboxes.

Google Workspace

If you use a gateway (gateway users only). When a gateway sits in front of Gmail, Gmail needs to know about it. Otherwise Gmail checks the gateway's IP instead of Nectar's, and authentication can fail.

  1. In the Google Admin console, go to Apps > Google Workspace > Gmail > Spam, Phishing and Malware.

  2. Under Inbound gateway, confirm your gateway's IP addresses are listed. If they aren't, add them and save.

Email allowlist (optional). On the same page, add 159.183.82.50 under Email allowlist. This is a useful backup, but not required once Step 1 and Step 3 are done.

Gmail loads images through its own image proxy, so no image setting is needed.

Microsoft 365

1. Inbound connector (gateway users only). If your gateway delivers to Microsoft 365 through a partner connector that only accepts certain IPs, add 159.183.82.50 to that connector's allowed list in the Exchange admin center under Mail flow > Connectors. If you use Enhanced Filtering for Connectors, confirm it's set up for your gateway so Microsoft 365 sees Nectar's real sending IP.

2. Allow images. If Outlook is set to block automatic image downloads, add both image hosts as trusted sources, or adjust the automatic download setting through Group Policy. Without this, recipients see blank images and opens aren't counted.

3. Remove the "External" tag (custom domain only). Comms is delivered through Nectar's infrastructure rather than your own mail server, so Microsoft 365 labels it external even when it comes from your domain.

  1. In the Exchange admin center, go to Mail flow > Rules.

  2. Open the rule that adds the External tag or banner.

  3. Add an exception: The sender IP address is in the range 159.183.82.50.

  4. Save the rule.

If your organization uses Outlook's built-in External tag instead of a mail flow rule and Comms still shows the tag, you can add your Comms sending address to its allow list (Set-ExternalInOutlook -AllowList).

4. Signature rules (custom domain only). If your organization uses a mail flow rule that adds a signature to outgoing mail from your domain, you can add the same exception (sender IP 159.183.82.50) to help keep signatures off Comms.


Step 5: Verify your setup

A quick test confirms everything is working before your first company-wide Comm. Include at least one IT contact and a few admins on different devices.

  1. Send the test template. In Nectar, open the Comms Template Library and send the Nectar Communications Content & Delivery Test template. It includes nearly every content type Comms uses. Send it once as a test send and once as a small real send, since the two can be handled differently.

  2. Check authentication. Open the email and view its headers. In Gmail, use the three-dot menu > Show original. In Outlook, use File > Properties (Internet headers) or View > View Message Source. SPF, DKIM and DMARC should all show PASS.

  3. Check your gateway's logs. Confirm the message was delivered without being held, rewritten or sanitized (for example, in Mimecast's Message Center or Proofpoint's message logs).

  4. Check how it looks. Open the email on desktop, in a web browser and on mobile. Images should load, links shouldn't be rewritten to a scanning address, and special characters should display correctly.

  5. Check translations (if your plan includes them). Have a couple of admins temporarily change their preferred language in their Nectar profile, then repeat the send.

  6. Check your analytics. A few minutes after sending, open the Comm's analytics. Opens and clicks should reflect what your test recipients actually did. A click rate near 100% right after sending usually means links are still being scanned, so revisit your gateway's link-scanning bypass.


About your Comms analytics

We recommend click-through rate (CTR) as your main engagement measure. Clicks reflect a reader acting on your message, and Nectar filters out known automated clicks from security scanners. Some scanner activity can still get through, which is why the link-scanning bypass in Step 3 matters.

Open rates are a useful directional signal, but across the email industry they're no longer a reliable measure on their own. Opens are counted when a tiny image in the email loads, and many mail clients and security tools now decide for themselves when, or whether, images load. We've taken the measures available to us to make opens as accurate as possible, including placing the open-tracking image at the top of every Comm so it's never cut off in long emails. How each mail client or security tool handles images is outside any sender's control, so no email platform can report opens with full accuracy. You may see:

  • Lower than actual: when images are blocked (common in Outlook), opens aren't recorded.

  • Higher than actual: Apple Mail Privacy Protection and some security tools load images automatically on delivery, which can register opens before anyone reads the email.

That's why CTR is the better measure of engagement. Completing the steps in this guide gives you the most accurate picture of both.


Need help?

If something still isn't working after Step 5, contact Nectar Support and include:

  • A screenshot or short description of what you're seeing

  • The email clients and devices involved (for example, Outlook desktop or Gmail mobile)

  • Whether it affects everyone or only some recipients

  • The email's headers or raw source, if you can share them

For common delivery and formatting questions, see Troubleshooting email delivery in Nectar Comms.

Did this answer your question?