Add support to StartTLS on Quota's mailing

[GutoVeronezi]

Description

On Quota's mailing settings, ACS has a configuration (quota.usage.smtp.useAuth) to inform if it will use secure SMTP authentication when sending emails.
However, this configuration only refers to use SSL or not. Operators haves no option to choose if they want to use StartTLS.

This PR intends to add support to StartTLS on Quota's mailing settings.

It is interesting to highlight that this enhancement would be able to solve issue #2625 (if it was applied in that setting as well); however, to reduce the scope of change, this one focuses only on Quota's mailing configuration.

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

How Has This Been Tested?

It has been tested locally on a test lab.

1. I had Enabled Quota's plugin on the management server and configured it to use Gmail's SMTP server.

server address: smtp.gmail.com
username: gmail address
password: gmail password
port (TLS): 587

2. On Quota - All Accounts, I added 10 credits to my user and set 20 as min balance.

3. I had added an gmail address to Accounts > <account> > Users - Email.

4. I allowed Less secure app access on my Google account.

5. I had restarted management server.

6. And I called quota update API via Cloudmonkey. Without the new option being introduced here, I would see an error in the management server. After setting it, everything is fine, and the alert email is sent.

[DaanHoogland]

code looks ok, and old behaviour is default, so looks good in that aspect. As a thunderbird user i have the experience that the client can discover what kind of security is used however, can we implement such a thing as well?

[RodrigoDLopez]

Code LGTM

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✖centos7 ✖centos8 ✖debian. JID-2681

[DaanHoogland]

@blueorangutan package

[blueorangutan]

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔centos7 ✔centos8 ✖debian. JID-2701

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔centos7 ✖centos8 ✖debian. JID-2756

[blueorangutan]

Packaging result: ✔centos7 ✖centos8 ✖debian. JID-2757

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✖centos7 ✖centos8 ✖debian. JID-2878

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 325

[GutoVeronezi]

@rhtyd @DaanHoogland is there anything else to do?

[blueorangutan]

Trillian test result (tid-390)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42094 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4573-t390-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_life_cycle.py
Smoke tests completed. 85 look OK, 2 have error(s)
Only failed tests results shown below:

Test	Result	Time (s)	Test File
test_01_deploy_kubernetes_cluster	Failure	3609.16	test_kubernetes_clusters.py
test_02_invalid_upgrade_kubernetes_cluster	Failure	3602.74	test_kubernetes_clusters.py
test_03_deploy_and_upgrade_kubernetes_cluster	Failure	0.05	test_kubernetes_clusters.py
test_04_deploy_and_scale_kubernetes_cluster	Failure	0.04	test_kubernetes_clusters.py
test_05_delete_kubernetes_cluster	Failure	0.05	test_kubernetes_clusters.py
test_07_deploy_kubernetes_ha_cluster	Failure	0.05	test_kubernetes_clusters.py
test_08_deploy_and_upgrade_kubernetes_ha_cluster	Failure	0.04	test_kubernetes_clusters.py
test_09_delete_kubernetes_ha_cluster	Failure	0.04	test_kubernetes_clusters.py
ContextSuite context=TestKubernetesCluster>:teardown	Error	44.66	test_kubernetes_clusters.py
test_01_migrate_VM_and_root_volume	Error	71.50	test_vm_life_cycle.py
test_02_migrate_VM_with_two_data_disks	Error	53.28	test_vm_life_cycle.py