On Friday, October 8, 2004, 8:01:44 AM, Matt Kettler wrote:
> At 08:43 AM 10/8/2004, Matt wrote:
>>I have a question on the new(ish) scanning that spamassassin does on
>>URI's.It seems to be working very well for us here, but I have a
>>question..
>>WIll it catch:
>>
>>http://www.blah.com/?jj38
Matt Kettler wrote:
> Theoretically, it should also match if the hostname changes, as long
> as the domain+TLD part is the same (ie: foo.blah.com)
>
> That said I've heard some mumblings the SA 3.0 implementation
> of domain stripping is a bit different than the
> Mail::SpamCopURI version, and the
At 08:43 AM 10/8/2004, Matt wrote:
I have a question on the new(ish) scanning that spamassassin does on
URI's.It seems to be working very well for us here, but I have a
question..
WIll it catch:
http://www.blah.com/?jj38942
as well as
http://www.blah.com/?34223
The URI blacklists only check the
It only looks at the domain.
For example, it will catch:
www.blah.com/
anything.blah.com
anything.anything.more.subdomains.blah.com/anything
Keith
> Hi,
> I have a question on the new(ish) scanning that spamassassin does on
> URI's.It seems to be working very well for us here, but I have a
Hi,
I have a question on the new(ish) scanning that spamassassin does on
URI's.It seems to be working very well for us here, but I have a
question..
WIll it catch:
http://www.blah.com/?jj38942
as well as
http://www.blah.com/?34223
We are beginning to notice alot of e-mails (being marked ri
