Re: Forwarding received mail through AWS SES

2019-01-21 Thread Stephen Satchell
On 2019-01-20 14:40, John Stoffel wrote: > The only problem with Digital Ocean right now is that Charter/Spectrum > in the US has blocked all (most? At least the one I'm using...) blocks > assigned to DO for some insane reason. The insane reason is phishing spam, and DO ignoring abuse notices. An

Re: Forwarding received mail through AWS SES

2019-01-21 Thread John Stoffel
> "Yuval" == Yuval Levy writes: Yuval> On 2019-01-20 14:40, John Stoffel wrote: >> The only problem with Digital Ocean right now is that Charter/Spectrum >> in the US has blocked all (most? At least the one I'm using...) blocks >> assigned to DO for some insane reason. Yuval> Why insane? Ha

Re: Forwarding received mail through AWS SES

2019-01-21 Thread Yuval Levy
On 2019-01-20 14:40, John Stoffel wrote: The only problem with Digital Ocean right now is that Charter/Spectrum in the US has blocked all (most? At least the one I'm using...) blocks assigned to DO for some insane reason. Why insane? Having been a DO customer for more than five years, I am no

Re: Forwarding received mail through AWS SES

2019-01-20 Thread John Stoffel
> "Durga" == Durga Prasad Malyala writes: Durga> Correct. I would recommend linode or digitalocean any time over Durga> AWS SES. AWS is a good option for heavy transactional mail Durga> alerts etc.  The only problem with Digital Ocean right now is that Charter/Spectrum in the US has blocked

Re: Forwarding received mail through AWS SES

2019-01-19 Thread Antonio Leding
KIMURA > <mailto:y...@utahime.org> wrote: >> From: Christos Chatzaras 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-mai

Re: Forwarding received mail through AWS SES

2019-01-19 Thread Antonio Leding
23:26 Yasuhiro KIMURA <mailto:y...@utahime.org> wrote: > From: Christos Chatzaras 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 provider

Re: Forwarding received mail through AWS SES

2019-01-19 Thread Durga Prasad Malyala
On Sat, Jan 19, 2019, 23:26 Yasuhiro KIMURA From: Christos Chatzaras > 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-mai

Re: Forwarding received mail through AWS SES

2019-01-19 Thread Bill Cole
On 19 Jan 2019, at 4:03, Yasuhiro KIMURA wrote: Hello, I use Debian 9 on AWS EC2. If mail is sent directly from EC2 host then some mail service provider such as Gmail rejects receiving it. So I set up so that mail is sent through AWS SES with following steps. 1. Obtain SES SMTP credential ac

Re: Forwarding received mail through AWS SES

2019-01-19 Thread Yasuhiro KIMURA
From: Christos Chatzaras 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

Re: Forwarding received mail through AWS SES

2019-01-19 Thread Christos Chatzaras
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 yo

Forwarding received mail through AWS SES

2019-01-19 Thread Yasuhiro KIMURA
Hello, I use Debian 9 on AWS EC2. If mail is sent directly from EC2 host then some mail service provider such as Gmail rejects receiving it. So I set up so that mail is sent through AWS SES with following steps. 1. Obtain SES SMTP credential accoring to following document https://docs.aws.amaz