Clarifying - I have both SES and EC2. EC2 is my main postfix box but the SMTP side is a backup for SES which is my main outbound email…
> On Jan 19, 2019, at 7:16 PM, Antonio Leding <t...@leding.net> wrote: > > FWIW - I’ve been using AWS for outbound SMTP well over 5 years with no > issues…maybe one-time have I bad an email rejected due to blacklisting…and > this was resolved within 30 minutes… > > > >> On Jan 19, 2019, at 7:13 PM, Durga Prasad Malyala <dp.maly...@gmail.com >> <mailto:dp.maly...@gmail.com>> wrote: >> >> >> On Sat, Jan 19, 2019, 23:26 Yasuhiro KIMURA <y...@utahime.org >> <mailto:y...@utahime.org> wrote: >> From: Christos Chatzaras <ch...@cretaforce.gr <mailto:ch...@cretaforce.gr>> >> Subject: Re: Forwarding received mail through AWS SES >> Date: Sat, 19 Jan 2019 12:35:58 +0200 >> >> > AWS EC2 IPs may have low reputation to e-mail providers, so is not >> > recommended to send e-mails using these IPs. >> > >> > Also AWS SES frequently have issues with RBLs. I wouldn't use it if you >> > use reliable delivery. It's good for newsletters because it has low cost >> > compared to other services and when you don't care if some e-mails are not >> > delivered. >> > >> > My recommendation is to setup a VPS (from a company that has clean >> > network) with multiple IPs if you need to send a lot of messages and use >> > postfix relay with randmap to balance the outgoing messages between the >> > IPs. >> >> Thank you for reply. Then I consider VPS instead of AWS EC2 and SES. >> >> --- >> Yasuhiro KIMURA >> >> Correct. I would recommend linode or digitalocean any time over AWS SES. AWS >> is a good option for heavy transactional mail alerts etc. >> >> Cheers/DP >
