@Fastnlight A normalized version, {{'18025518160'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number +1-802-551-81*60 to determine which entries on the number lists match that pattern, which would tell you: Matched by 18025518160 on line 2468 of blacklisted_numbers.txt: 18025518160 found normalized; 8025518160 found normalized
@Fastnlight A normalized version, {{'18089008011'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number 1 > -(808)~ 900 ~8^0.11 to determine which entries on the number lists match that pattern, which would tell you: Matched by 18089008011 on line 723 of blacklisted_numbers.txt: 18089008011 found normalized; 8089008011 found normalized
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (271): Does kuku FM refund money? by Plesk Plesk on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (271): How to get a refund in zepto by Plesk Plesk on serverfault.com
@VLAZ That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 977-778-6797 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 977-778-6797. Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow 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 word(s) if you really want to add the pattern you provided.
@Cow The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
