- 최신
- 최다 투표
- 가장 많은 댓글
In this case; given that it's a third-party component that you don't have a lot of control over: You're going to need to run it on compute platform that supports it and also supports connecting to the Internet on TCP/25. That means you can use EC2 or Lightsail - both are virtual machine offerings from AWS. You might also find that you can run it in Docker; if so you might consider Fargate as an alternative which might be more cost effective - but it entirely depends on a bunch of factors including how long the component runs for; how often it runs; how much memory it requires; and so on.
Thanks so much for the explanation. I've read a little about Docker but have never used it. Truemail has a Docker image. I guess I can run it in EC2/Lightsail somehow. I have a AWS Discovery call this morning to discuss cost differences between the two. Truemail also offers an integration service https://truemail.io/integrations/zapier/aws-lambda that works with an AWS Lambda. If the EC2/Lightsail costs are higher I may use that service for SMTP validations.
관련 콘텐츠
AWS 공식업데이트됨 7달 전
Could you expand on what you mean by "SMTP checking of email addresses"? Do you mean that you're connecting to the email server of an email address that has been entered to verify it?
The Truemail gem is checking the validity of domains and emails so I will assume that's what happening. I want to know that an email doesn't exist before I receive the Delivery Status Notification (Failure) email. I'm getting more and more of them these days. I have the correct code to do that kind of validation but I was told that I was getting port closed errors because port 25 was closed. I just added the links to the GitHub repository of the gem.