ISP has man in the middle STARTTLS SMTP monitoring and blocks 2465 2587 ports to amazon. Any other options?

0

We're looking to use Amazon SES for our outbound mail since our current datacenter has implemented SMTP traffic inspection (man-in-the-middle) breaking confidentiality on all SMTP connectivity originating from our servers. This shows as a nasty "red padlock" on Gmail.com for example.

Our servers are Linux EXIM (cPanel) and I am following these instructions:

Telnet tests from datacenter to email-smtp.us-east-2.amazonaws.com fail on port 465, 2465, 2587.

While port 25 and 587 do succeed, I am aware of how STARTLS works and so its highly likely the datacenter will continue to break TLS encryption to monitor outbound mails.

Does Amazon SES offer any alternatives to avoid this issue; such as an unpublished port that is not found in the documentation that can alternative be used? or perhaps a way to connect to an VPN tunnel only for SMTP traffic connections that are always encrypted? (TLS wrapper was supposed to do this but datacenter seems to block it)

已提問 1 年前檢視次數 267 次
1 個回答
0

Hi Vint.

Is there any way to use the Amazon SES SDK/API instead of SMTP? That way you can use TCP/TLS. Also, it would help with achieving higher trhroughput.

I hope this helps.

profile pictureAWS
專家
已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南