Relevant Product: Exclaimer Cloud - Signatures for Office 365
Scenario
You have configured Exclaimer Cloud for your Microsoft 365 tenancy. When you send an email through Exclaimer's server, the email is rejected, and you receive a non-delivery report with a similar message:
Reported error: 501 5.1.8 Your message couldn't be delivered because the email has no mail from address. See https://go.exclaimer.com/334 for more information
Resolution
The resolution of this issue depends upon different scenarios; some of them are listed below.
Please click on the required options listed below to go through the detailed description:
Pre-requisites (if the email is sent to a group or an individual user)
Before you start working on the resolution for the NDR group or an individual user, make sure you have:
Installed Online PowerShell V2 module
Connected to Exchange Online
Installed Online PowerShell V2 module
Connected to Exchange Online
Install Exchange Online PowerShell V2 module:
- Open the Windows PowerShell and run this command as an Administrator:
Install-Module -Name ExchangeOnlineManagement - Confirm that you want to install this PowerShell module.
Note: For additional installation options, see ExchangeOnlineManagement.
Connect to Exchange Online:
- If you have Multi-Factor Authentication enabled, run this command:
Connect-ExchangeOnline -UserPrincipalName <UPN> -ShowProgress $trueIn <UPN> enter your username.
- If you don't have Multi-Factor Authentication enabled, run this command:
Connect-ExchangeOnline -Credential $UserCredential -ShowProgress $true
When prompted, enter your password (and the Multi-Factor Authentication verification code if required).
Once you have successfully installed the Exchange Online PowerShell module and connected to Exchange Online, please see what you need to do next if the email is sent to a group and if the email is sent to an individual user.
The email is sent to a group
This issue occurs when there is no sender specified in the message envelope. If the sender is blank, Signatures for Office 365 cannot identify the tenant to append for the email signature.
- If no on-premise Active Directory exists, then amend the distribution group properties in Microsoft 365 using Windows PowerShell.
NOTE: Please ensure that Windows PowerShell is connected to Microsoft 365 before running the following commands.
To do this, check the Pre-requisites section of this guide.To complete the steps described below, you will need:
Microsoft 365 Global Administrator credentials
Amending the distribution group properties:
- Run the following command:
Get-DistributionGroup <Group Email Address> | fl *ReportToOriginatorEnabled* - If the value returned is False then run this command to change it to True:
Set-DistributionGroup <Group Email Address> -ReportToOriginatorEnabled $true
- If an on-premise Active Directory exists and the distribution group is synchronized to Microsoft 365, then:
From the distribution group Properties, set the attribute ReportToOriginator to TRUE.
These changes will not take effect until the on-premises Active Directory domain has been synchronized and replicated in Microsoft 365.
The email is sent to an individual user
According to Microsoft, "Any mail to JournalingReportNdrTo mailbox will not be journaled and it will not honor transport and mailbox rules settings. It is recommended to create a dedicated mailbox for JournalingReportNdrTo setting or set it to an external address."
Note: For more information, see Transport and mailbox rules in Exchange Online or in on-premises Exchange Server don't work as expected.
Note: For more information, see Transport and mailbox rules in Exchange Online or in on-premises Exchange Server don't work as expected.
Note: The steps described below apply even if message journaling is not enabled.
- Specify a dedicated mailbox, as the recipient for Journal Report NDR messages, in Microsoft 365 using Windows Powershell.
NOTE: Please ensure that Windows PowerShell is connected to Microsoft 365 before running the following commands.
To do this, check the Pre-requisites section of this guide.To complete the steps described below, you will need:
Microsoft 365 Global Administrator credentials
Specifying a dedicated mailbox:
Run the following command:
set-transportconfig -JournalingReportNdrTo <insert mailbox address>Tip! Microsoft recommends that the JournalingReportNdrTo recipient be set to an external email address or a dedicated mailbox created, which has no transport or mailbox rules applied.
The email was an out of office email
To resolve this issue, you need to re-run the setup or upgrade the Transport Rule to prevent Out of Office emails from being sent to Exclaimer Cloud.
Warning: Please be aware of the following:
- If you re-run the Connector Setup wizard, then any existing Exclaimer transport rules will be removed in the process.
-If you upgrade your existing subscription, then any existing Exclaimer transport rules will not be removed in the process.
- If you re-run the Connector Setup wizard, then any existing Exclaimer transport rules will be removed in the process.
-If you upgrade your existing subscription, then any existing Exclaimer transport rules will not be removed in the process.
You can do one of the following:
- Re-run the Connector Setup wizard: The Microsoft 365 Connector Setup will automatically run the Transport Rule 'Create Bypass Out of Office Transport Rule'. This transport rule will stop all automatic reply emails from being sent to Exclaimer Cloud.
Note: For more information, see How to re-run the Office 365 Connector Setup Wizard. - Upgrade your existing subscription: The Upgrade wizard will add a new transport rule in addition to the existing Exclaimer Cloud transport rules already set up. The new rule will ensure that Exclaimer Cloud does not process 'Out of Office' emails.
Warning: The Upgrade Rule option will not be visible if the new Transport Rule has already been set up via the Setup wizard (if you are a new customer) or if the Upgrade wizard has already been run before.
For more information, see Setup Overview for Office 365.
Upgrading your existing subscriptionTo upgrade your existing subscription for the new Transport rule:
To complete the steps described below, you will need:
Microsoft 365 Global Administrator credentials
- Log into the Exclaimer Cloud portal, launch your subscription, then click the options list from the top-right of your screen and select Settings:
- The Settings window is displayed, select the Mail Flow tab and click Upgrade Rule:
- You are prompted to sign in (if you haven't already) as a Global Administrator.
Once you have successfully signed in as a Global Administrator, the Bypass Exclaimer Cloud for Out of Office Messages wizard is displayed:
- Click Next to proceed.
- You will be prompted to authorize Exclaimer Cloud to configure Microsoft 365 on your behalf.
Copy the code (), then click Authorize.
- The Microsoft window is displayed; paste the copied code in the space provided, then click Next:
The wizard now creates the Out of Office Transport Rule:
- Once the rule has been successfully created, click Close to complete the setup process:
- Log into the Exclaimer Cloud portal, launch your subscription, then click the options list from the top-right of your screen and select Settings: