On 3/1/2011 1:36 PM, Karsten Bräckelmann wrote: > On Tue, 2011-03-01 at 13:11 -0500, Bowie Bailey wrote: >> On 3/1/2011 12:39 PM, tr_ust wrote: >>> Thanks...I could really use the help! > [...] >>> uri LOCAL_URI_EXAMPLE /03ysl.9hz.com\// >>> score LOCAL_URI_EXAMPLE 20 >>> uri LOCAL_URI_EXAMPLE /040jk.9hz.com\// >>> score LOCAL_URI_EXAMPLE 20 >>> uri LOCAL_URI_EXAMPLE /0oczg.9hz.com\// >>> score LOCAL_URI_EXAMPLE 20 >>> >>> I'm using the per user option right now for spamassassin, so I test it by >>> sending the user an email with one of these links...and it's still going >>> through. >> You are aware that these rules are specifying that there MUST be a slash >> after .com in order to match, right? >> >> Other than that, I don't see any obvious problem. Send an example email >> through your system and put the resulting email (with headers) into a >> pastebin so I can look at it. > Uhm... There is only ONE rule. Repeatedly overwriting the previous rule > definition. Last one is defined, everything prior to that is effectively > non-existent. > > Does that count as obvious problem? ;)
Yea, that counts. :) -- Bowie
