Configuring Thresholds and Timeouts
Thresholds and timeouts are important because they affect the positive selection processing of each email that passes through Votiro Cloud for Email to the Positive Selection® Engine. For each email, a number of requests pass between the Votiro Cloud for Email and the Positive Selection® Engine - from the initial handshake, through various status check requests, to completion of positive selection processing. If thresholds and timeouts are not specified appropriately, emails might be returned and delivered to recipients in an unprocessed state.
Although unsanitized emails are identified as such in the email subject, the objective of using the Votiro Cloud solution is to positively select the mail. The maximum size limit of email attachments is 50MB. The limit is to be set on the Exchange server. Emails with attachments that are greater than 50MB are not sent and the sender receives an exception stating that the mailbox cannot receive an email of this size.
You modify thresholds and timeouts in the WebApiHandlerConfig.xml file. The following fields can be configured.
Field Name | Description | Value | ||||||
---|---|---|---|---|---|---|---|---|
WebApiTimeoutInMS | The total length of time Votiro Cloud for Email waits for a positive selection process to be completed, in milliseconds. | Range: 5000 to 180000000 Default value is 90000 | ||||||
WebRequestTimeoutInMS | The length of time the Votiro Cloud for Email waits per API request from the Positive Selection® Engine, in milliseconds. | Range: 5000 to 180000000 Default value is 60000 | ||||||
WebApiStatusCheckIntervalInMS | The length of time the Email Connector waits before a periodic status is sent to the Positive Selection® Engine, in milliseconds. | Range: 1 to 5000 Default value is 100 | ||||||
WebApiNumberOfRetries | Number of retries to perform in case one of the following HTTP error codes is returned by the Positive Selection® Engine:
| Range: 0 (minimum) Default value is 5. |
Note
The WebApiStatusCheckIntervalInMS cannot be greater than the WebRequestTimeoutInMS or WebApiTimeoutInMS fields for correct operation.
Note
There is a default timeout for the sanitization process. If the email is complex, the time required for the sanitization process may exceed the default timeout.. When this scenario occurs, the end user will receive an unsanitized email. We are providing the unsanitized file in order not to impact the customer's business. The customer will be able to define a policy for adding sanitization indications to the emails.
Comments
0 comments
Please sign in to leave a comment.