On 17/12/2022 08:35, Marc wrote:
The sender's SPF record includes the sending IP (40.107.96.128) in the
secureserver.net <http://secureserver.net> entry, and SPF_PASS is
hit.
Without even checking anything I can already remember that this
secureserver.net is shit. I have blocked whole ranges of them, they
send spam, try passwords etc. I have the impression that there is
nothing secure about secureserver and everything seems to be hacked
there.
s/secureserver/google/
s/secureserver/amazon/
s /secureserver/microsoft/
s /secureserver/ ... /
I often have gmail accounts hit our honeypots, to the point that I now
deliberately take a week or more to clear the google smtp of the day off
the list, each time, I take longer and longer to remove - just like
other providers
and I currently have a large chunk of google/amazon/MS/linode/D.O/...
cloud ranges blocked.
My point is, they are all the same and if someone wishes to whitelist
them, that's the risk they take, they are answerable to their users, not
to you, me or anyone else.
--
Regards,
Noel Butler
This Email, including attachments, may contain legally privileged
information, therefore at all times remains confidential and subject to
copyright protected under international law. You may not disseminate
this message without the authors express written authority to do so.
If you are not the intended recipient, please notify the sender then
delete all copies of this message including attachments immediately.
Confidentiality, copyright, and legal privilege are not waived or lost
by reason of the mistaken delivery of this message.
