X-SPAM-LEVEL: Spam detection results: 9
AWL -3.026 Adjusted score from AWL reputation of From: address
BAYES_50 0.8 Bayes spam probability is 40 to 60%
CLOUD_SHARE 1 Suspicious cloud storage links
DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain
HTML_MESSAGE 0.001 HTML included in message
KAM_VERY_BLACK_DBL 5 Email that hits both URIBL Black and Spamhaus DBL
MIME_HTML_ONLY 0.1 Message only has text/html MIME parts
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
T_SCC_BODY_TEXT_LINE -0.01 -
URIBL_ABUSE_SURBL 1.25 Contains an URL listed in the ABUSE SURBL blocklist [corelearners360.com]
URIBL_BLACK 1.7 Contains an URL listed in the URIBL blacklist [appleacademy.com.my]
URIBL_DBL_SPAM 2.5 Contains a spam URL listed in the Spamhaus DBL blocklist [appleacademy.com.my]
I would suggest to disable bayes - this should give you 1.9 points more on that mailBAYES_00 -1.9 Bayes spam probability is 0 to 1%
Not 100% sure if that's the case - but check the SPF of the sending domain - and maybe your DNS setupT_SPF_PERMERROR 0.01 SPF: test of record failed (permerror)
Is the IP being blacklisted?After the changes - unfortunately, next spam from now:
X-MS-Exchange-CrossTenant-Network-Message-Id: beaed4ca-5327-4843-448c-08da4e08dfe0
X-MS-Exchange-CrossTenant-AuthSource: BN6PR19MB3393.namprd19.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Jun 2022 13:22:05.2192
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 8d36836e-6b75-4de6-bab9-5f4b1775427f
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: HLxnY/D6JPgHjGf+OZlcYHo2Ba8oS9whoYmZ63OrjT1ZGcDsHxCag7N+zipnk38YICEOOwo4i5qDTC+HdtkvfTDHTklyI7cAHLTimjE2jmXU2Tn3FMtHSYn/FIWkypfV
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR19MB4447
X-SPAM-LEVEL: Spam detection results: 1
DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain
HTML_MESSAGE 0.001 HTML included in message
KAM_GOOGLE_REDIR 0.5 Message contains a google URL redirector link
LIST_UNSUB 1 Mailinglist/Newsletter emails
RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust
RCVD_IN_MSPIKE_H2 -0.001 Average reputation (+2)
SPF_HELO_PASS -0.001 SPF: HELO matches SPF record
SPF_PASS -0.001 SPF: sender matches SPF record
T_SCC_BODY_TEXT_LINE -0.01 -
Return-Path: pedro.sogamosoc@campusucc.edu.co
I mean if the IP is not blacklisted in DNSBL then spam mail will through.Blacklisting of O365 IPs is not good :-/
PMG utilize few options to block spam.
1. DNSBL - block blacklisted IP based on your DNSBL list.
2. Mail filter - block/quarantine based on your custom what/who object rule.
3. Spamassassin rules - increase/decrease SA score based on spamassassin default and your custom rules.
You have to study your own environment and customize your spam mail fighting strategy.