Mar 14 2024 03:58 AM
Hello,
Since 3 weeks the mails containing some urls are considered as phishing. It's linked to the URL detonation reputation. Currently we released some emails but it's not a solution and many customers complaints. The information is sent to Microsoft to remove false positive but it does not seem to work.
How we can improve reputation ? DMARK, SPF et DKIM are well configured
Mar 30 2024 01:35 PM
Apr 24 2024 11:09 AM - edited Apr 24 2024 11:20 AM
@Olivier34000 Unfortunately so far Microsoft is only allowing any people (properly identified with an MS account or even not so, then as much simpler guests) to 'Report unsafe site' for Phishing or 'Malware or other threats'. But from that same page I've already provided them (I mean MS side) some feedback about asking them to possibly consider in future also another option to even allow end users (and so obviously also their own customers) to propose their objections to something that might even be incorrectly identified as Phishing or 'Malware or other threats' related because those are currently the only 2 main possible identification categories allowed.
JFYI since there are already other known '3rd parties' that allow even end users to dispute already existing URLs being negatively tracked also because of detection made by their own 'free software' (and I've already had the chance to directly object/dispute some of such detections that I found to be wrong) I also already made them aware too accordingly. So for now let's just hope that also continuing to do so (I mean providing feedback from same 'Report unsafe site' page), in addition to also following previous suggestion you already received, might further help to better evolve things in future and maybe even help you to solve your issue. 0:-)
P.S. My above reporting of 1 3rd party I'm already aware of, and of their related free software, is only meant here for others simpler awareness and does not represent, by my side, any other specific endorsement or even suggestion to evaluate such products. 😮 0:-)
Apr 25 2024 12:04 AM
The issue was resolved with the Microsoft support.