Skip to content

Newsletters sent through Bird Cloud Email Service or the JungleMail mail server reach Exchange Online from outside your organization, even when they come from your own domain. Exchange can mark them as external in two ways:

  • a mail flow rule your organization created, which for example adds [EXTERNAL] to the subject or a warning to the body;
  • Outlook’s own External tag, if your organization turned on external sender identification.

Add an exception for JungleMail 365 to whichever you use. Newsletters sent through a Microsoft 365 sending account come from inside your organization and aren’t marked (Choose a sending account type).

Both markings warn people about mail that only pretends to come from a colleague, so keep each exception as narrow as it can be: JungleMail’s mail servers in the mail flow rule, your newsletters’ sending addresses in Outlook’s tag.

  • You need permission to manage mail flow rules in Exchange Online, for example the Exchange Administrator role.
  • You need the IP addresses of JungleMail’s mail servers for your cloud (IP addresses and domains) and the sending address of your newsletters, for example news@enovapoint.com.
  1. In the Exchange admin center, go to Mail flow > Rules.
  2. Select the rule that marks external email, anywhere in its row but the checkbox.
  3. Select Edit rule conditions.
  4. Under Except if, select The sender > IP address is in any of these ranges or exactly matches, and enter the IP addresses for your cloud. If the rule already has an exception, select Add exception first. Use the IP addresses rather than the sender’s address or domain: anyone can write your domain in a From address, but the IP address a message arrives from can’t be forged.
  5. Select Save.

A changed rule can take 30 minutes or more to apply (Manage mail flow rules in Exchange Online).

The same exception in Exchange Online PowerShell:

Set-TransportRule -Identity "<rule name>" -ExceptIfSenderIPRanges <IP address>,<IP address>

<rule name> is the name of your rule. List every IP address for your cloud, and any the exception already has: the command replaces them.

Exempt your sending address from the External tag

Section titled “Exempt your sending address from the External tag”

If your organization uses external sender identification, add your newsletters’ sending address to its allow list, in Exchange Online PowerShell:

Set-ExternalInOutlook -AllowList @{Add="news@enovapoint.com"}

The allow list matches the From address. Add the sending address rather than your whole domain, so the exception stays as narrow as it can (Set-ExternalInOutlook).

  • Send from one shared address. The allow list needs every From address your newsletters use. With a From of Specified email address, such as news@enovapoint.com, that is one entry; with JungleMail newsletter author, it is every editor’s address, and the list holds at most 200 entries (Add and manage sending addresses, Set-ExternalInOutlook).
  • Never exempt your own domain from the mail flow rule. An exception for enovapoint.com as the sender’s domain lets mail forged from outside arrive without the warning, which is what the rule is there to catch. Microsoft warns against using your own domains as conditions in mail flow rules (Create allowlists).
  • Check whether you use both markings. Microsoft advises turning off subject-line rules before turning on Outlook’s tag, to avoid marking mail twice. If both are on, newsletters need both exceptions.
  • Test before the first large newsletter. Once the rule has had time to apply, have a site administrator send a test to a few colleagues, and check that it arrives without [EXTERNAL] and without the External tag.