urlsand.com is allowed, some third level domains are classified as phishing and
there is no way out other than attempting with a different third level domain.
I wander what the review process looks like.
Rodolfo
Da: mailop per conto di Rodolfo Saccani via mailop
Data: lunedì, 16 ottobre 2023 alle ore
Did anyone have similar issues?
We’re hitting a rubber wall trying to correct Microsoft false positives in URL
classification.
Any suggestion would be greatly appreciated.
Cheers
Rodolfo
Da: mailop per conto di Rodolfo Saccani via mailop
Data: venerdì, 13 ottobre 2023 alle ore 11:15
A
We are having issues with emails flagged as phishing by Defender (and not
delivered) when the email contains URLs of a URL sandboxing service that
performs security checks at click-time.
One example of a URL that is currently triggering false positives is
hxxps://blackflow[.]urlsand[.]com/?u=http
As far as I can see, envelope-from domains without a SOA record see their email
rejected with 554 over some volume threshold.
This seems to be a fairly recent update. This requirement only recently
appeared here: https://senders.yahooinc.com/smtp-error-codes/ (you can check
the internet archive
ce you sent this
and I at least have information that is more helpful than silence. So I
hope it helps some.
On 2022-11-14 03:13, Rodolfo Saccani via mailop wrote:
> If anybody from Microsoft con help on this, my gratitude will be huge.
>
>
> Some companies (like Southeastern railways, fo
Hi everyone,
below is a notification recently sent by Microsoft to O365 tenant admins.
As far as I understand this new subnet (40.95.0.0/16) is expected to deliver
mostly traffic from compromised O365 tenants.
I’d like to check whether my understanding is correct or not, any feedback is
welcome.