Hi.

Some of our emails are sent using public folder address as sender. After migrating to Exchange 2013 this folders are flooded with NDR from non existent adressess. Is there some way to filter NDR, sent to public folders? I've tried transport rules and "folder assistant" without saccess.

Transport rule should be able to do it...what is your transport rule settings?

Hi,

I understand you don't want to receive the NDR on the public folder address.

Please try to use the below command :

New-TransportRule -Name 'test' -Comments '' -Priority '0' -Enabled $true -SentTo public@domain.com -SubjectOrBodyContainsWords 'generating server:domain.com' -DeleteMessage $true

Hope it's helpful to you.

Regards,

David 

• Edited by David Wang_Microsoft contingent staff Tuesday, August 18, 2015 3:15 AM

It seems transport rules do not work with Exchange system messages. 

I've tried subject and sender rulles but they just do not work.

Hi Vden,

You are correct, transport rules on mailbox servers don't apply to DSN (NDR) messages. Edge server rules can handle NDRs well though. Applies to 'All messages except system messages'

In 2013 there is a option in the rules where you can select Message Type. But that too doesn't contain NDR or DSN messages.

MessageType

Single message type name

MessageType accepts one of the following message types: OOF AutoForward Encrypted Calendaring PermissionControlled Voicemail Signed ApprovalRequest ReadReceipt Does not match for a read receipt to a meeting request.

Options available only when you are having the mailbox at remote domain, send connector or via Edge only.

Solution is to use differnet replyto address for sending email using the PublicFolder address.

Referneces:

Transport rule conditions (predicates) Condition property values for a Mailbox server:

https://technet.microsoft.com/en-us/library/dd638183(v=exchg.150).aspx#MBPropertyValues

Exchange Hub Transport Rule Ignored for local NDR reports:

http://serverfault.com/questions/70997/exchange-hub-transport-rule-ignored-for-local-ndr-repor

Hi Vden,

Slight more explaination on the solution.

The actual mail-from sender would be a non-existant ID, and reply-to would be the valid ID, hence when System generates error its sends it to the non-existant ID saving you the NDRs storm. And when users reply to emails, it automatically populates the PublicFolderAddress making it replyable.

mail from: NDRhere@contoso.com
250 2.1.0 Sender OK
rcpt to: bar@contoso.com
250 2.1.5 Recipient OK
data
354 Start mail input; end with <CRLF>.<CRLF>
From:  PublicFolder<NDRhere@contoso.com>
To: Bar<bar@contoso.com>
Date: Mon, 1 May 2006 10:23:00 +0000 (UTC)
Reply-To: <PublicFolder@contoso.com>

#Header should appear like this
To: <satyajit@contoso.com>
Sender: John SMith<mailer@mailer.contoso.com>
From: John SMith <mailer@mailer.contoso.com>
Return-Path: mailer@mailer.contoso.com
Reply-To: <JohnSmith@contoso.com>

To feel it using outlook how it works. Refer below:

Direct Reply To Different Email Address (Reply-To Address) In Outlook 2010/2013

https://kb.intermedia.net/article/2387

4.Type the following command to tell the receiving SMTP server who the message is from:
 MAIL FROM:Admin@test.com

Note:- This address can be any SMTP address that you want, but it is a good idea to consider the following issues:
If you do not use a valid email address when you send a message, you cannot determine whether the message had a delivery problem because the non-delivery report (NDR) cannot reach an IP address that is not valid. If you use a valid email address, you receive the following response from the SMTP server:

References:

Telnet to Port 25 to Test SMTP Communication:
https://support.microsoft.com/en-us/kb/153119#/en-us/kb/153119

Setting reply-to using SMTP over telnet:
http://www.experts-exchange.com/Software/Internet_Email/Email/Q_21833740.ht