3.3.5.6 Receiving a RopSpoolerLockMessage ROP Request
On receipt of a RopSpoolerLockMessage ROP request ([MS-OXCROPS] section 2.2.7.5), a server MUST take the actions listed in the following table based on the value of the LockState field.
|
Value name |
Action |
|---|---|
|
lstLock |
Locks the message for the client that is sending the request. The request fails if the message is locked by some other client. |
|
lstUnlock |
Unlocks the message. |
|
lstFinished |
Unlocks the message and completes post-processing of sent mail according to the PidTagSentMailSvrEID property (section 2.2.3.10) and the PidTagDeleteAfterSubmit property (section 2.2.3.8) on the message. |
The following error codes can be returned in the response.
|
Error code name |
Value |
Meaning |
|---|---|---|
|
ecNotSupported |
0x80040102 |
The server does not support sent message processing, or the client is not the spooler. |
|
ecNotInQueue |
0x80040601 |
An attempt was made to lock an already locked message, or the message is not in the spooler queue.<14> |