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 wrote:
>
> FWIW - I’ve been using AWS for outbound SMTP well over 5 years with no
> issues…maybe one-time
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
> wrote:
>
>
> On Sat, Jan 19, 2019, 23:26 Yasuhiro
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-mails using these IPs.
> >
> >
> "Wietse" == Wietse Venema writes:
Wietse> John Stoffel:
>> > "Wietse" == Wietse Venema writes:
>>
Wietse> I'm implementing logfile support for Postfix on MacOS, because not
Wietse> providing results in a bad experience.
>>
Wietse> This is a retrofit workaround, therefore it will
Jan P. Kessler:
>
> > Try: make makefiles ...optional arguments... make WARN= Sorry, I
> > haven't built with /opt/SUNWspro/bin/cc for ~10 years. Wietse
>
> No problem. Seems like it's time for a change. After emptying WARN it
> looked promising, but then the build broke here:
>
>
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
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. I wouldn't
On Thu, Jan 17, 2019 at 11:22:46AM -0500, Bill Cole wrote:
You truly need to ask whoever runs that other server to explain why they
believe your server is misconfigured if you want a definitive answer.
On 18.01.19 07:06, Mayuresh wrote:
This is certainly strangest of the mailing lists I ever
> Try: make makefiles ...optional arguments... make WARN= Sorry, I
> haven't built with /opt/SUNWspro/bin/cc for ~10 years. Wietse
No problem. Seems like it's time for a change. After emptying WARN it
looked promising, but then the build broke here:
"milter.c", line 621: non-constant
Jan P. Kessler:
> -UUSE_DYNAMIC_MAPS -Wmissing-prototypes -Wformat -Wno-comment? -g -O
> -I. -DSUNOS5 -c alldig.c
> cc: illegal option -Wmissing-prototypes
Try:
make makefiles ...optional arguments...
make WARN=
Sorry, I haven't built with /opt/SUNWspro/bin/cc for ~10 years.
Hello,
I'm sorry for line breaks and showing the wrong output. It's not easy to
get that information here. Hope this will be readable.
### make makefiles finished; performing make ###
rm -f meta/main.cf.proto && ln -f conf/main.cf meta/main.cf.proto
rm -f meta/master.cf.proto
Hi postfix-users,
today I have the pleasure to update sparc some machines, that haven't
been touched for more than 2.5 years :/
The systems use sunstudio compiler. Openssl, bind, ... went fine but
now, as it comes to postfix, I'm failing. The build scripts are in use
since long time, and worked
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
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
14 matches
Mail list logo
