SMTP task should have an option to allow invalid certificates

SMTP servers seem to not-so-seldomly use self-signed certificates with names that do not match the server's public hostname. With the current SMTP task, establishing an SSL/TLS connection to these kinds of SMTP servers does not work. The task should have the option to accept invalid certificates and handle the validation based on a user-provided certificate thumbprint.