On 30/03/2023 16:48, Michael Peddemors via mailop wrote:
> Now, if you could get EVERYONE to block them for a day, or find some
> other way to hit their pocket books, maybe we could see some relief.
Co-ordinate deferring all email from them for a 30 hour period (UTC
00:00 to UTC 32:00, so that i
So, I guess we have to assume that IP address on AWS is a forgery.. huh?
host 18.235.53.110
110.53.235.18.in-addr.arpa domain name pointer s1.email.freshdesk.com
Return-path:
host -t TXT emailuss.freshdesk.com
emailuss.freshdesk.com descriptive text "v=spf1
include:fdspfus.freshemail.io ~al
Hi
> My recommendation is to recognize that 1-bit binary blocklistings
> aren't granular enough to account for shared environments without
> causing false positives.
Agreed, the blacklist scores adds to the SpamAssassin score.
That is why not every email sent from that IP is rejected as spam but
> On 3/30/23 07:37, Benoit Panizzon via mailop wrote:
>
> > What would be the best way to address such issues for Office365
> > customers?
My recommendation is to recognize that 1-bit binary blocklistings
aren't granular enough to account for shared environments without
causing false positives.
S
On 3/30/23 18:36, Hans-Martin Mosner via mailop wrote:
I try to tackle this by analyzing domains present in mail headers and rejecting
mails accordingly. As you've experienced, talking the Office365 customers into
leaving their crappy host isn't working, so I will have to accept that a
signific
