Without getting too much into RFCs, a read receipt is not a delivery report. While you are reading that you may notice the first sentence which mentions how editing the Remote Domain "Do not send delivery reports" will NOT block read receipts from entering/leaving your org (told you we'd come back to that). You can read about this in all its glory here. As you know all the relevant settings were kept in the IIS metabase (taken from AD during the DS2MB 1 way process or natively there) so when it was requested that the ability to block read receipts be put into the product we obliged with a hotfix that allowed the creation of a key in the metabase to block these (after it was discovered that checking off "Do not send delivery reports" on the remote domain object did not accomplish this. In Exchange 2003 we used the IIS SMTP engine. A question that comes up often enough to merit a post is: "How does one block read receipts from leaving or entering my org?"Īnd to answer that we need to go into the way back machine to Exchange 2003.
0 kommentar(er)
