Skip to content

Commit 3d86a1e

Browse files
committed
Update Release-QuarantineMessage.md
Updated de-dup delivery scenario.
1 parent 984abf7 commit 3d86a1e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

exchange/exchange-ps/exchange/Release-QuarantineMessage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Release-QuarantineMessage -Identity <QuarantineMessageIdentity>
6767
```
6868

6969
## DESCRIPTION
70-
Scenario: [email protected] sends a message to [email protected] and [email protected]. Gmail bifurcates this message into two copies that are both routed to quarantine as phishing in Microsoft. An admin releases both of these messages to [email protected]. The first message that reaches the mailbox is delivered. The second message is identified as duplicate delivery and is skipped. Message are identified as duplicates if they have the same message ID and received time.
70+
Consider the following scenario: [email protected] sends a message to [email protected] and [email protected]. Gmail bifurcates this message into two copies that are both routed to quarantine as phishing in Microsoft. An admin releases both of these messages to [email protected]. The first released message that reaches the admin mailbox is delivered. The second released message is identified as duplicate delivery and is skipped. Message are identified as duplicates if they have the same message ID and received time.
7171

7272
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
7373

0 commit comments

Comments
 (0)