Traditionally, ESPs have been unable to use AWS for sending mail because
AWS IPs have very bad histories of being used for spam (among other
reasons). I believe most ESPs are running their own servers for email or
using a managed hosting service of some kind that allows them to use
private IPs/rent
ender Message Security: Click below to verify authenticity
https://verify.exchangedefender.com/verify.php?id=w6J0493R007074&from=howa...@macrollc.com
-- next part --
An HTML attachment was scrubbed...
URL:
<https://chilli.nosignal.org/cgi-bin/mailman/private/mailo
Not sure of the detail of the implementation, but it's named "Bring Your Own
IP", not "Bring your ranges", so it could not fit with ESPs' needs.
If it's about BGP announcement, it would probably still be announced by
Amazon's ASN (being 16509, 14618 or another one), so the footprint is still
the
In article
you write:
>-=-=-=-=-=-
>-=-=-=-=-=-
>Not sure of the detail of the implementation, but it's named "Bring Your Own
>IP", not "Bring your ranges", so it could not fit with ESPs' needs.
A few seconds looking at the AWS page reveals that you need to bring at least a
/24 that
is assign
I had the same initial concern that "bring your own Ip" != "bring thousands
of your own IPs"
However, that page explicitly lists email senders like ESPs as a use case:
"Bring Your Own IP is also useful for applications such as commercial email
services that rely on IP address reputation to allow
As John said, the signup form mentions the minimum /24 requirement, so that
seems better. Also, that would work with the theory of BGP announcement, as
anything smaller than /24 would be filtered out by many networks.
I guess the requirement of having IPs provided by ARIN is related to the beta
Hello Email Folks,
I work at Agari, where I guide large organizations through the process of
getting their email to pass DMARC. I have lately had some customers with
greater-than-usual issues relating to aligned authenticated messages that
get forwarded, where the forwarding system is changing hea
Maybe it's not a coincidence, but Steve Atkins just made a post about that:
https://wordtothewise.com/2018/07/minimal-dmarc/
I would tend to say that the more headers are included in the signature, the
"safer" it gets (any change would be suspicious), but this is challengeable and
it makes sens
Ugh, list-unsubscribe headers are required to be removed by mailing lists.
Well, I guess technically only if their sublists, but that's a distiction I
bet most don't make.
Though, the chances of a message passing dkim through a mailing list is
practically non-existent anyways. And marketing mail