feat(smtp): support for unauthorized connections

[syncush]

Hi, predator devs!

Regarding issue #161

As followed by @enudler guideline I added the proper configuration for Nodemailer to support unauthorized connections/self-signed certificates and added the relevant doc for it.

One thing I may be missing, does your server automatically support the new key for a new configuration through Predator's REST-API?

P.S. it is my first time trying to contribute to an open-source project so I probably made some rookie mistakes, criticism is welcome.

unrelated: I loved your talk "Can you API handle this?" on the GO Open Source 2019 convention.

[NivLipetz]

hi @syncush ! we really appreciate your contribution

first thing first, welcome to the open source world!

can you please rebase to master (we see your forked project is 7 commits behind the master)

regarding the /config endpoint in the API, it does support this new key as long as you added the key to the configDataMap as you did correctly.

regarding the TLS configuration, in order for Nodemailer to use the TLS connection without any confusion I suggest adding secure: true

Additionally, IMO, default values for secure and rejectUnauthorized should be false and should be set to true if the user wants the connection to specifically use TLS

happy you liked our talk :)

[syncush]

Thank you for your quick response, I have never rebased (used to merge) before, I'll read about it.

[NivLipetz]

@syncush thanks again!