On Tue, Mar 02, 2010 at 03:21:33PM +0200, Henrik K wrote: > On Tue, Mar 02, 2010 at 02:46:26PM +0200, Henrik K wrote: > > > > Sorry if there's a well known explanation, but I didn't have time to dig > > in.. > > > > body: > > > > example.com/fubar > > http://example.com/fubar > > > > SA 3.3: > > > > uri: parsed uri found of type parsed, http://example.com > > uri: parsed uri found of type parsed, http://example.com/fubar > > > > SA 3.2: > > > > uri: parsed uri found of type parsed, example.com/fubar > > uri: parsed uri found of type parsed, http://example.com/fubar > > > > Why do the results differ? Seems it's impossible to get full paths for uris > > without http:// using 3.3. > > Sorry a bit hard to read example.. here's better: > > 3.3: > > parsed uri found of type parsed, http://example1.com > parsed uri found of type parsed, http://example2.com/fubar2 > > 3.2: > > uri: parsed uri found of type parsed, example1.com/fubar1 > uri: parsed uri found of type parsed, http://example1.com/fubar1 > uri: parsed uri found of type parsed, http://example2.com/fubar2 > > Fubar1 completely missing in 3.3? This also affects uri rules! Seems kinda > buggyish to me.
Ok I think this relates to https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5780 So at the expense of less FPs, if I want to hash full URIs from message for BL use, I guess I need to pretty much duplicate the old code in my plugin. :( Probably would make sense to keep the FPish URIs somewhere, but not use them by default.. Cheers, Henrik
