On 9/23/2020 1:51 PM, Marc Roos wrote:
I'm hosting on AWS. So the recommendation was to proxy my outbound
mail through AWS's SES server so it :?
appeared that the mail came from 'trusted' Amazon.
Ehhh, amazon cloud messages are flagged by us as spam, and some ranges
are even blocked. I would try get a dedicated ip address if you value
your mail.
Thanks for the info Marc. But I feel like when I push in one place it
pops out somewhere else. I do have a fixed IP. When I was using it
directly (not going through SES), the MTAs that had the courtesy of
bouncing with a reason said the IP address was blacklisted but didn't
say where, even though SpamAssassin and mail-tester.com found no
blacklisting. I changed to several other fixed IP addresses and got the
same thing. SA and mail-tester continued to say it's totally clean....
but MTAs kept bouncing the messages, some with the blacklist message and
some with no explanation. So I went to SES out of desperation. I'm
getting fewer bounces going through SES than not using it. But your
comment worries me a lot. With all of the gyrations I had to go through
to be able to use SES along the monitoring Amazon does with SES, I'm
kinda surprised that it would be flagged as a spam source.
Is there some trick I'm missing? What do others do when mail keeps
bouncing with no explanation and SA says everything's clean? There's
got to be a way to make my mail more acceptable. Just give me a fighting
chance to fix whatever is wrong. But I have to know what is wrong
before I can address it.
Is there a 'right' solution?
Thx
