When we delete large number of old emails for users, they receive large number of emails with 

Subject: Not read: This is a test email

"Your message

    To: user x

    Subject:  This is a test email

     Sent:   Monday, December 1, 2013 .....

was deleted without being read on Monday,. ......

I want to block all such emails in getting into user's mailbox.  So far, I've created only 1 rule that checks Subject for "No read:" from Inside to Outside.   This would cause issues if legitimate emails uses the phrase.

Looking at the header, it doesn't contain disposition as mentioned in other articles or any other items that can be filtered with...

Is there another condition I can add in order to prevent someone using these words to not get blocked?

Tell them to stop sending messages with read receipts requested.  And read and live my auto

Hi JT

Thank you for your question.

There are following conditions which we could add:

1.        The sender is;
2.        The recipient is  :
3.        Subject for: Not read: *

In action: Delete the message without notifying anyone

We could create transport rule which include above.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Sender / recipient could be anyone as there are few hundred users.

As emails are deleted via retention, user's unread emails with read receipt request gets an email back.

I am getting about 5,000 of them across the firm per week.

Using just "Not read:" seems risky, just need to see if there is another definite filter that can be used.   Adding a message contains "was deleted without being read" didn't seem to catch anything for unknown reason.

I am doing a forward at the moment for testing.

---------------------

Your message

   To: John Doe

   Subject: Meeting This Friday

   Sent: Monday, November 1, 2013 9:01:07 AM (UTC-08:00) Pacific Time (US & Canada)

 was deleted without being read on Monday, April 13, 2015 1:14:45 PM (UTC-08:00) Pacific Time (US & Canada).

----------------------

Header
----------------------

Received: from mailserer1.company.local
 ([fe80::5555:5555:1111:1111]) by mailserver2.canyonpartners.local
 ([fe80::5555:5555:2222:2222]) with mapi id 14.03.0224.002; Mon, 13 Apr 2015
 16:28:55 -0700
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: John Doe <jdoe@company.com>
To: "test@citi.com" <test@citi.com>
Subject: Not read: test email: December
 09 2014
Thread-Topic: test email: December 09
 2014
Thread-Index: AAHQFHweELDC0P7qOUuGOUa6kZWux51WWj6f
Date: Mon, 13 Apr 2015 16:28:54 -0700
Message-ID: <CF097956868555458A21E69D5D556B081255B39B@mailserver3.company.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: <CF097956868555458A21E6555D956B081558B355@mailserver3.company.local>
MIME-Version: 1.0
X-MS-Exchange-Organization-AuthSource: mailserver1.canyonpartners.local
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04

---------------------------

Send emails to ask a few hundred million outside users to not request read receipt when sending us email is a solution?

Sounds like that signature needs to be removed.

Well, it's their problem, not yours.  They asked for it.

The problem is the email is sent back to our user not the other party.......

Did your user request read receipts?

This is resolved by adding message type as read receipt and delete.

• Marked as answer by JT_CP 13 hours 3 minutes ago