MVP - Most Valuable Professional

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft Technologies like Exchange, Office 365, Azure and Cloud Security.
Thomas Stensitzki | MVP
Thomas Stensitzki | MVP

MVP LogoThomas Stensitzki is a principal technology consultant focusing on the Microsoft messaging and collaboration technologies and the owner of Granikos GmbH & Co. KG.

He was awarded as MVP for Office Apps & Services in 2018.

He holds Master certifications as Microsoft Certified Solutions Master Messaging and as Microsoft Certified Master for Exchange Server 2010. This makes him a subject matter expert for any messaging topic related to Microsoft Exchange, Exchange Online, Microsoft 365, and Hybrid configurations.

Follow Thomas on: Google+, LinkedIn, Twitter

My sessions:

Personal blog:
Personal blog (legacy):
Personal website:
Contact Thomas at


On September 15, 2014
0 Comment

Exchange and other MTAs use DSNs (Delivery Status Notifications) and NDRs (Non Delivery Reports) to notify the sender or sending MTAs (Message Transfer Agents aka Mail Servers) about the varioius statuses of a given email message. In Exchange those messages are generated primarily by the categorizer component of the transport service.

You can use the New-SystemMessage cmdlet to create new messages. These messages can even be localized and can contain Html tags for properly styled notifications.

From a system perspective the various notifications used are named and fulfill a specific purpose.

Report and receipt types (Exchange Version independent) used for notification

  • Delivery Receipt (DR)

    Report confirming that a message was delivered to its intended recipient

  • Delivery Status Notification (DSN)
    Report describing the result of an attempt to deliver a message

  • Message disposition Notification (MDN)
    Report describing the status of a message after it has been successfully delivered to a recipient. Examples: read notification (RN) or non-read notification (NRN)
    Defined by RFC 2298 and controlled by Disposition-Notification-To header

  • Non-Delivery Report (NDR)
    Report indicating to the message sender that the message could not be delivered to the intended recipients

  • Non-Read Notification (NRN)
    Report indicating that a message was deleted before is was read, when a read receipt was requested

  • Out Of Office/Facility (OOF)
    Report indicating that the recipient will not respond to a new message
    OF referes to the Microsoft original term „out of facility

  • Read Notification (RN)
    Report indicating that a message was read

  • Recall Report (RR)
    Report indicating the status of a recall request for a specific recispient
    A recall request is used when a sender tries to recall a sent message by using Outlook



This post has first been published in my personal legacy blog here.

Read More »


Add remote IP address ranges to an Exchange Server 2013/2016 receive connctor.

Create a new text file containing the new remote IP address ranges


The script creates a new sub folder named ReceiveConnectorIpAddresses and saves the currently configured remote IP address ranges first.

While adding the new remote IP address ranges, the script checks, if the new ranges already exist.


# Add IP addresses from ip.txt to MYCONNECTOR

.\Add-ReceiveConnectorIpAddress.ps1 -ConnectorName MYCONNECTOR -FileName D:\Scripts\ip.txt

.\Add-ReceiveConnectorIpAddress.ps1 -ConnectorName REMOTECONNECTOR -FileName .\ip-new.txt -ViewEntireForest $true

Version History

  • 1.0, Initial community release
  • 1.4, Support Mailbox role added (Issue #4)



Read More »

When testing the Outlook Anyhwere configuration using the Exchange Remote Connectivity Analyzers (ExRCA) you might encounter the following error message:

Autodiscover settings for Outlook Anywhere are being validated.
ExRCA wasn't able to validate Outlook Anywhere Autodiscover settings.
The AuthPackage wasn't specified in the EXPR section of the Autodiscover response.

ExRCA OutlookAnywhere error

If you encounter this error, you need to verify the following two attriobutes of the Outlook Provider configuration:

  • Server attribute
  • CertPrincipalName attribute

Server Attribute

Remove any dedicated server configuration.

Get-OutlookProvider EXPR | Set-OutlookProvider -Server $null

Now the appropriate CAS FQDN will be used.

CertPrincipalName Attribute

The CertPrincipalName attribute must match the common name (CN) of the SSL certificate. If a wildcard certificate is being used, it is required to configure the CertPrincipalName for the certificate

Set-OutlookProvider EXPR | Set-OutlookProvider -CertPrincipalName msstd:*




This post had originally been posted at SF-Tools in German language.

Read More »