@CodyGray That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@CodyGray That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +3 more (490): Bradley Walsh Green CBD Gummies by ttguhfbaj on drupal.SE
@CodyGray That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body (487): We are on the whole occupied by Zak Crawly on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword with email in body, bad phone number in body, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, +3 more (329): Create NFT Token in a hassle-free way? by Antier Solutions on bitcoin.SE
@CodyGray That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
