Hi All,
Is anyone else seeing this resurfacing?
We've seen a large number of 421 Deferred - see
https://ipcheck.proofpoint.com/?ip=
What's odd is, it's affecting some of our best senders with very good list
hygiene and great engagement, open, click and reply rates, very few
bounces, little spam
https://datatracker.ietf.org/doc/html/rfc7208#section-5.2
See the table at the bottom of the section regarding recursive check_host()
evaluation.
In this case, the recursive check_host() function returned "none" as a
result from the include mechanism, and therefore according to the table,
the
Update on this - it appears that Google will now be restricting BIMI
display to specifically DKIM authenticated mail.
Link below, see the update on the article.
https://www.scmagazine.com/news/email-security/gmail-spoofing-google-priority-1-probe
"This issue stems from a third-party security
John Levine via mailop skrev den 2023-06-06 11:45:
It appears that Al Iverson via mailop said:
How long until Google, Yahoo, others stop accepting that forwarded
mail from Microsoft, is another way to frame that.
The problem is that you can't tell it's forwarded, since it comes
from the same
It appears that Al Iverson via mailop said:
>How long until Google, Yahoo, others stop accepting that forwarded
>mail from Microsoft, is another way to frame that.
The problem is that you can't tell it's forwarded, since it comes
from the same servers that sent real mail for the forged domains.
Hi List
One more technical question after some discussion with one of our
customers.
Sender has SPF entry:
"v=spf1 ip4:10.1.2.0/25 include:_spf.example.com -all"
_spf.example.com either has no txt entry or just does not exist.
So from my point of view, the SPF entry is still valid as it has
