The delivery of a message sent by public folder x has failed. To: bogus Cc: The non-delivery report has been deleted.
Hi, Our monitoring system has begun sending us a lot of events like The delivery of a message sent by public folder x has failed. To: bogus Cc: The non-delivery report has been deleted. I believe what is happening is that a spammer is using the address of one of our mail-enabled public folders in the From: address, then when the NDR is generated by their target host it is sent back to our public folder. Since Exchange doesn't accept NDRs to mail enabled public folders this message is generated. How can I prevent these messages from being logged in Exchange 2007 or send the NDRs to a dummy mailbox, etc. Anything to keep them from being sent into our monitoring system =) thank you.
September 10th, 2011 6:47pm

On Sat, 10 Sep 2011 15:47:09 +0000, aweaver6142 wrote: > > >Hi, > >Our monitoring system has begun sending us a lot of events like The delivery of a message sent by public folder x has failed. To: bogus Cc: The non-delivery report has been deleted. I believe what is happening is that a spammer is using the address of one of our mail-enabled public folders in the From: address, then when the NDR is generated by their target host it is sent back to our public folder. Since Exchange doesn't accept NDRs to mail enabled public folders this message is generated. > >How can I prevent these messages from being logged in Exchange 2007 or send the NDRs to a dummy mailbox, etc. > >Anything to keep them from being sent into our monitoring system =) Rather than ask how to prevent Exchange from recording a legitimate event, why not ask your monitoring system to ignore the event? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2011 7:30pm

On Sat, 10 Sep 2011 15:47:09 +0000, aweaver6142 wrote: > > >Hi, > >Our monitoring system has begun sending us a lot of events like The delivery of a message sent by public folder x has failed. To: bogus Cc: The non-delivery report has been deleted. I believe what is happening is that a spammer is using the address of one of our mail-enabled public folders in the From: address, then when the NDR is generated by their target host it is sent back to our public folder. Since Exchange doesn't accept NDRs to mail enabled public folders this message is generated. > >How can I prevent these messages from being logged in Exchange 2007 or send the NDRs to a dummy mailbox, etc. > >Anything to keep them from being sent into our monitoring system =) Rather than ask how to prevent Exchange from recording a legitimate event, why not ask your monitoring system to ignore the event? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP I don't see the point in an event being created for something which has no operational value especially considering there is no way to change the behaviour.
September 10th, 2011 7:32pm

On Sat, 10 Sep 2011 16:32:37 +0000, aweaver6142 wrote: >On Sat, 10 Sep 2011 15:47:09 +0000, aweaver6142 wrote: > > >Hi, > >Our monitoring system has begun sending us a lot of events like The delivery of a message sent by public folder x has failed. To: bogus Cc: The non-delivery report has been deleted. I believe what is happening is that a spammer is using the address of one of our mail-enabled public folders in the From: address, then when the NDR is generated by their target host it is sent back to our public folder. Since Exchange doesn't accept NDRs to mail enabled public folders this message is generated. > >How can I prevent these messages from being logged in Exchange 2007 or send the NDRs to a dummy mailbox, etc. > >Anything to keep them from being sent into our monitoring system =) Rather than ask how to prevent Exchange from recording a legitimate event, why not ask your monitoring system to ignore the event? --- Rich Matheisen MCSE+I, Exchange MVP >--- Rich Matheisen MCSE+I, Exchange MVP > >I don't see the point in an event being created for something which has no operational value especially considering there is no way to change the behaviour. Nor do I see the point in alerting on unnecessary events. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2011 8:08pm

The only workaround I know is to use the “publicDelegates” attribute. For example: There’re a dummy mailbox and a public folder called PF1, we can put dummy mailbox’s distinguishedName into the “publicDelegates” attribute of PF1 so that dummy mailbox will receive the NDR James Luo Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
September 12th, 2011 10:01am

James, how do you do this and what are the drawbacks?
Free Windows Admin Tool Kit Click here and download it now
September 14th, 2011 2:58pm

Process: 1. Get dummy mailbox’s DistinguishedName with the cmdlet below Get-User “User A” | Fl DistinguishedName 2. Launch ADSI Editor, go to “CN=Microsoft Exchange System Objects”, right-click the mail-enabled PF1 object, and then go to “Properties” 3. In the “Attribute Editor” tab, locate “publicDelegates” attribute, and then copy dummy mailbox’s DistinguishedName into it
September 19th, 2011 5:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics