https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8101
--- Comment #12 from Sidney Markowitz <sid...@sidney.com> --- (In reply to Christer Mjellem Strand from comment #11) > Here's another weird one; according to logs, this redirect chain was not > followed further: > > https://cutt.ly/6KH04Tn => https://cutt.ly/guard/6KH04Tn That second link produces a 403 "client is forbidden from accessing a valid URL" status, which is how cutt.ly indicates a linked blocked for abuse. The plugin doesn't have anything to directly check for a blocked link. The perldoc for the plugin has examples of rules URI_TINYURL_BLOCKED and URI_BITLY_BLOCKED. It would work to add a URI_CUTTLY_BLOCKED m,^https://cutt\.ly/guard/, once the bug that causes these local links not be followed gets fixed. -- You are receiving this mail because: You are the assignee for the bug.
