Advanced configuration parameters for processing RTF mails
If necessary, you can affect the processing of RTF emails with the following advanced parameters in the connector.properties file.
Changing some values might be necessary, if you have very big RTF emails which could slow down the processing by the eperi sEcure Platform.
Note: Changes of the below configuration parameters take effect automatically after
approx. 20 seconds. A eperi sEcure Platform restart is not necessary.
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| o365.rtf.processing.timeout | Time after which the processing of RTF emails is aborted. | Time in milliseconds | 42000 (42 seconds) |
| o365.rtf.compressalways | By default, the eperi sEcure Platform only compresses RTF emails, if they were already compressed when the eperi sEcure Platform received them. With this parameter, you can change this behaviour. | true = RTF emails are always
compressed. false = RTF emails are only compressed, if they were already compressed when the eperi sEcure Platform received them. |
false |
| o365.rtf.limit | With this parameter, you can set a limit up to which size RTF emails are processed by the eperi sEcure Platform. If the limit is exceeded, the mail is no longer processed, but only forwarded. | Number of bytes | No limit |
| o365.rtf.compressed.limit | With this parameter, you can set a limit up to which size compressed RTF emails are processed by the eperi sEcure Platform. If the limit is exceeded, the email is no longer processed, but only forwarded. | Number of bytes (compressed size) | No limit |
| o365.rtf.cores | With this parameter, you can limit the number of CPU cores used for the parallel processing of RTF emails. | Number of CPU cores | No limit |
| o365.rtf.suspensiontime | With this parameter, you can set how long threads which are currently compressing RTF emails should be suspended at discrete points in time. | 1 - 20 seconds | None (compression threads are not waiting) |