>...
>Greetings:
>
>While it has never been pleasant, we regularly review spam including the
>HTML source code behind the spam to help us adjust our system-wide spam
>tagging rules.
>
>We've noticed a lot of sick porn spam being left untagged.
>
>The tests that raised the score, though not high e
On Friday 11 March 2005 14:17, DNI Support Department typed:
> Greetings Jeff:
>
> These are live examples; but it appears the porn spam all follow the same
> hex (?) directory structure after the domain name.
>
> Hence, wanting a pattern for that purpose.
> > > http://yamanekohm.com/9d70188c4e797
On Friday, March 11, 2005, 6:17:21 AM, DNI Department wrote:
> Greetings Jeff:
> These are live examples; but it appears the porn spam all follow the same
> hex (?) directory structure after the domain name.
> Hence, wanting a pattern for that purpose.
I'll let others comment on expressions.
H
Greetings Jeff:
These are live examples; but it appears the porn spam all follow the same
hex (?) directory structure after the domain name.
Hence, wanting a pattern for that purpose.
Thank you.
At 09:15 AM 3/11/2005, you wrote:
On Friday, March 11, 2005, 6:01:58 AM, DNI Department wrote:
> Howev
On Friday, March 11, 2005, 6:01:58 AM, DNI Department wrote:
> However, I did notice in the HTML source code a common theme:
> src="http://yamanekohm.com/9d70188c4e7971b6d3b1e2fa8/Nf3KZuBf0T/file_name";
> alt="rundowns" border="0">
> http://yamanekohm.com/9d70188c4e7971b6d3b1e2fa8/file_name";
Greetings:
While it has never been pleasant, we regularly review spam including the
HTML source code behind the spam to help us adjust our system-wide spam
tagging rules.
We've noticed a lot of sick porn spam being left untagged.
The tests that raised the score, though not high enough were as fo
