Prerequisites

• Tried the most recent nightly build
• Checked if your issue is already reported.

Is your feature request related to a problem?

My server is in a DMZ and listening on two hostnames (internal/ external). The SSL certificate is for the external hostname only. External connections to 4190 work well. Internal connections to 4190 fail due to wrong certificate (hostname). For IMAPS in TB I am able to accept the certificate and ignore the hostname error for internal connections. For the sieve plugin this does not work.

Describe the solution you'd like

I would like to be able to disable certificate/hostname checks for the sieve TB plugin

Describe alternatives you've considered

Additional context