- Newest
- Most votes
- Most comments
Upgrading my GroupMail software indeed solved the issue. So this problem had nothing to do with AWS. Anyway thanks a lot for your assistance in finding a solution.
I would continue to check your workstation or network. Connection to the host and port work from my workstation.
❯ nc -zv email-smtp.eu-west-1.amazonaws.com 465
Connection to email-smtp.eu-west-1.amazonaws.com port 465 [tcp/urd] succeeded!
Hope this helps!
Thanks iBehr, I just tested, and the result seems OK:
tnc -ComputerName email-smtp.eu-west-1.amazonaws.com -Port 465
ComputerName : email-smtp.eu-west-1.amazonaws.com
RemoteAddress : 52.18.165.220
RemotePort : 465
InterfaceAlias : Ethernet
SourceAddress : nnn.nnn.nnn.nn
TcpTestSucceeded : True
There may be an issue with your mail program. Please explain more about it.
Is the program written in PHP or another language? Is it running directly on your computer or in a Docker container or something similar?
Hi Shibata, The program that I use is called GroupMail. It runs on my own PC (Windows 10), that is connected to the Internet via a Fritzbox router. In the Groupmail I can enter all parameters that I mentioned above, the program then connects to the SMTP server and starts distributing our newsletter email. I have been using this program for many years, no changes have bee applied. So I think that something must have changed in the PC, the router or in AWS.
Update: a reply just came in from GroupMail support: it seems that my (old) version does not support TLS 1.2. Strange; I had checked that and since TLS 1.2 was published in 2008 I had not expected this - as the program that I use is much younger.
I will try to upgrade and post about the result.
Relevant content
- asked 4 years ago
- asked 9 months ago
- asked 7 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago