SEO

------------------------------------------------------------------------
MULTILEVEL MARKETING SPAMBLOCK OF 'INTERNET WISE GUY, MACON GEORGIA USA'
------------------------------------------------------------------------
bulk emailing is completely legal!! method for to advertising multilevel
marketing opportunities, and all such ' spam fighters ' who interfere in
violation of usa FREE SPEECH laws. one who is such 'spam fighter' using
name of the 'internet wise guy, macon georgia usa' has ILLEGALLY engage
in restraint of trade interfered with legitimate business ventures. we
demand that ''internet wise guy, macon georgia usa'' reveal the identity
so we can serve important papers regarding restraint of a trade lawsuit!
------------------------------------------------------------------------
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
------------------------------------------------------------------------
our customers are happy to see arival our emails, plus many of them have
reached financial independence through the multilevel marketing. IS NOT
as this 'internet wise guy, macon georgia usa' claims a PYRAMID SCHEME!!
------------------------------------------------------------------------
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
'internet wise guy, macon georgia usa' stop interfer with advertising!!!
------------------------------------------------------------------------
singed legitimate legal multilevel marketer no pyramid scheme advertised
------------------------------------------------------------------------

Horton heard a Who named multilevel@marketing.com saying:
> ------------------------------------------------------------------------
> MULTILEVEL MARKETING SPAMBLOCK OF 'INTERNET WISE GUY, MACON GEORGIA USA'
> ------------------------------------------------------------------------
> bulk emailing is completely legal!! method for to advertising multilevel
> marketing opportunities, and all such ' spam fighters ' who interfere in
> violation of usa FREE SPEECH laws. one who is such 'spam fighter' using
> name of the 'internet wise guy, macon georgia usa' has ILLEGALLY engage
> in restraint of trade interfered with legitimate business ventures. we
> demand that ''internet wise guy, macon georgia usa'' reveal the identity
> so we can serve important papers regarding restraint of a trade lawsuit!
> ------------------------------------------------------------------------
<snip>
------------------------------------------------------------------------
> our customers are happy to see arival our emails, plus many of them have
> reached financial independence through the multilevel marketing. IS NOT
> as this 'internet wise guy, macon georgia usa' claims a PYRAMID SCHEME!!
> ------------------------------------------------------------------------
<snip>

Needs to improve his English.

BTW, it's my privilege to ignore free speech as I chose.

Anyone know how to limit, score against, x-posting with slrn's score file? The
FAQ explains howto cross-post, but I see nothing where to control/limit seeing
the number of cross-posted articles. I'd like to set the number at two. If it's
not possible, how about catch phrases, such as "marketing"? Here's my current
score file:

% Below is my general filtering.
%BOS[*]
Score: -9999
Xref: advocacy
Xref: windows
Xref: conspiracy
Xref: flame
Xref: kook
Xref: microsoft
Xref: politics
Xref: \<alt\.religion\.jehovahs-witn
Xref: \<rec\.ponds[^.]
Xref: \<soc\.culture\.jewish
Xref: \<soc\.singles
Xref: wrestling

%EOS

%BOS
% specifically rejected newsgroups
% since the general filter doesn't
% always catch them
Score: -9999
Newsgroups: advocacy
Newsgroups: windows
%EOS

%BOS
% kills all "test" posts not in a *test NG
[~*.test]
Score: -9999
Subject: ^test$
%EOS

%BOS
% Interested in slrn articles only
[news.software.readers]
Score: 9999
Subject: slrn
%EOS


%BOS
% scoring for ONLY 'slrn' posts in listed NG
% and discard all others
[news.software.readers]
Score: -9999
~Subject:^slrn$
%EOS

Thank you,
--
sk8r-365
The only way to make Windows "secure":
1) go to http://goodbye-microsoft.com
2) replace existing operating system.

On Tue, 02 Oct 2007 08:05:56 -0500, sk8r-365 wrote:

> Anyone know how to limit, score against, x-posting with slrn's score file? The
> FAQ explains howto cross-post, but I see nothing where to control/limit seeing
> the number of cross-posted articles. I'd like to set the number at two.

I don't know the answer with slrn, but it's really easy to do with
leafnode.

Horton heard a Who named Mark South saying:
> On Tue, 02 Oct 2007 08:05:56 -0500, sk8r-365 wrote:
>
>> Anyone know how to limit, score against, x-posting with slrn's score file? The
>> FAQ explains howto cross-post, but I see nothing where to control/limit seeing
>> the number of cross-posted articles. I'd like to set the number at two.
>
> I don't know the answer with slrn, but it's really easy to do with
> leafnode.

I have it figured out - filtering by keyword ... of course, when I apply it I
won't see further messages for this post due to word matching; which would have
included this reply, except that I changed the Subject so as to *not* have a
match:
[*] % filter for all NG
Score: -9999 % absolute death of article
Subject: market % any match of this word and _poof_ !

Thanks for reminding me of leafnode's method, Mark!
--
sk8r-365
The only way to make Windows "secure":
1) go to http://goodbye-microsoft.com
2) replace existing operating system.

On Tue, 02 Oct 2007, in the Usenet newsgroup alt.os.linux.debian, in article
<mqydnSiXEbufAZ_anZ2dnUVZ_rSinZ2d@bresnan.com>, sk8r-365 wrote:

>Horton heard a Who named Mark South saying:

>> sk8r-365 wrote:

>>> Anyone know how to limit, score against, x-posting with slrn's score
>>> file? The FAQ explains howto cross-post, but I see nothing where to
>>> control/limit seeing the number of cross-posted articles. I'd like
>>> to set the number at two.

That's a bit on the low side. For _most_ of the 84 groups I try to scan
daily, I allow up to 4 groups. OK, inexpensive killing of cross-posts:

% When a newsreader contacts the newsserver, it requests a so-called Xover,
%which gives a subset of the headers for the requested article. Headers
%present in this list include From:, Subject:, References:, Date:, Bytes:,
%Lines:, Message-ID: and Xref:. Newsreaders use this to compose their
%header list, and to perform threading. OTHER headers can be queried
%from the server, but this is expensive and should be avoided over the
%Internet.
%
%Killfile rules based on these headers can be implemented quite efficiently,
%since this information has to be requested for normal operation anyway.

so given the choice of 'From:', 'Subject:', 'References:', 'Date:',
'Bytes:', 'Lines:', 'Message-ID': and 'Xref:':

-----
From: sk8r-365 <sk8r-365@sk8r.debian.etch.invalid.org>
Subject: Re: (snip) slrn scoring help needed
References: <0aadnfMN8ZJErZ_aRVn_vwA@giganews.com>
<QNadnUok1aOp35_anZ2dnUVZ_hKdnZ2d@bresnan.com>
<47025d2e$1_4@news.bluewin.ch>
Date: Tue, 02 Oct 2007 14:29:06 -0500
Bytes: 2115
Lines: 25
Message-ID: <mqydnSiXEbufAZ_anZ2dnUVZ_rSinZ2d@bresnan.com>
Xref: number1.nntp.dca.giganews.com alt.os.linux.debian:7519
-----

the latter is the only one with any indication of newsgroup. From
another posting today in another newsgroup:

-----
Xref: number1.nntp.dca.giganews.com news.announce.newgroups:6172
news.groups:430617 news.groups.proposals:3031
-----

you said two groups are OK? Try

Xref: :.*:.*:

which should kill posts where the Xref: header contains three colons.

>> I don't know the answer with slrn, but it's really easy to do with
>> leafnode.

but no hints?

>I have it figured out - filtering by keyword ... of course, when I
>apply it I won't see further messages for this post due to word
>matching; which would have included this reply, except that I changed
>the Subject so as to *not* have a match:

which is why filtering by keyword isn't the solution _here_ (for the
problem of cross-posters).

>[*] % filter for all NG
>Score: -9999 % absolute death of article

Score: =-9999 %kill it, and don't bother searching for more score terms

According to the 'changes' file, that mode was included way back in
slrn-0.8.0. You may also want to think about 'Score:' verses 'Score::'.
The single colon is a logical AND indicator so all conditions/rules for
that score have to be true. The double colon is a logical OR indicator,
and _any_ condition/rule that matches sets the score.

>Subject: market % any match of this word and _poof_ !

[compton ~]$ grep -vE '^([%\[ ]|Score|$)' /var/spool/slrnpull/score | cut
-d' ' -f1 | sort | uniq -c | column
899 From: 7 Message-ID: 78 Xref:
2 Lines: 282 Subject: 2 ~Subject:
[compton ~]$

Imagine what that would look like if I were grumpy instead of my nice
cheery disposition. (That also is an indication why I use the '=' in
score values.)

Old guy

multilevel@marketing.com wrote:

>
>
>
> - - - - - - < BLEEP BLEEP > - - - - - - -

Hey, RM: when did you sign up with Giganews?

--
humjohn AT aerosurf DOT net

Horton heard a Who named Moe Trin saying:
> On Tue, 02 Oct 2007, in the Usenet newsgroup alt.os.linux.debian, in article
> <mqydnSiXEbufAZ_anZ2dnUVZ_rSinZ2d@bresnan.com>, sk8r-365 wrote:
>
>>Horton heard a Who named Mark South saying:
>
>>> sk8r-365 wrote:
>
>>>> Anyone know how to limit, score against, x-posting with slrn's score
>>>> file? The FAQ explains howto cross-post, but I see nothing where to
>>>> control/limit seeing the number of cross-posted articles. I'd like
>>>> to set the number at two.
>
> That's a bit on the low side. For _most_ of the 84 groups I try to scan
> daily, I allow up to 4 groups. OK, inexpensive killing of cross-posts:

84!? Holy smokes. I have time for 3 groups. I'm so busy I have to
be draconian about x-posting limits. BTW, on the matter of killing
posts and expense; way I had it getting articles was very
slowwwwwww.

> % When a newsreader contacts the newsserver, it requests a so-called Xover,
<snip good explanations>

>
> you said two groups are OK? Try
>
> Xref: :.*:.*:
>
> which should kill posts where the Xref: header contains three colons.


Now that's working and is F-A-S-T!

<snip>

> Imagine what that would look like if I were grumpy instead of my nice
> cheery disposition. (That also is an indication why I use the '=' in
> score values.)

You're a nicer guy than I !

Here's my faster score file (thanks to you), but I have to set each item
separately; for an unknown reason grouping isn't getting it:


%BOS
[*]
Score: =-9999
Xref: advocacy[*]
Score: =-9999
Xref: windows[*]
Score: =-9999
Xref: conspiracy[*]
Score: =-9999
Xref: flame[*]
Score: =-9999
Xref: kook[*]
Score: =-9999
Xref: microsoft[*]
Score: =-9999
Xref: politics

% limits x-posting max 2 groups[*]
Score: =-9999
Xref: :.*:.*:


% kills all "test" posts not in a *test NG
[~*.test]
Score: =-9999
Subject: ^test$

% Interested in all slrn articles;
% need to test for redundancy with this
% and the next filter
[news.software.readers]
Score: 9999
Subject: slrn


% scoring for ONLY 'slrn' posts in listed NG
% and discard all others
[news.software.readers]
Score: -9999
~Subject:^slrn$

% limits message size in max bytes;
% if it can't be said in about 400 lines
% there's to much yapping, it's a binary
% or unneeded text is not being snipped
Score: =-9999
Bytes: 14700


% handles those get rich schemes with "$" in Subject[*]
Score: =-9999
Subject:^\$\

%EOS


Thanks for your time!!

--
sk8r-365
The only way to make Windows "secure":
1) go to http://goodbye-microsoft.com
2) replace existing operating system.

On Thu, 04 Oct 2007, in the Usenet newsgroup alt.os.linux.debian, in article
<FO6dnU2DxIfBupjanZ2dnUVZ_q-jnZ2d@bresnan.com>, sk8r-365 wrote:

>Horton heard a Who named Moe Trin saying:

>> That's a bit on the low side. For _most_ of the 84 groups I try to
>> scan daily, I allow up to 4 groups.

>84!? Holy smokes. I have time for 3 groups. I'm so busy I have to
>be draconian about x-posting limits. BTW, on the matter of killing
>posts and expense; way I had it getting articles was very
>slowwwwwww.

There's a difference between _reading_ a newsgroup and scanning it.
That's the reason all of the netiquette guidelines and FAQs suggest
using a descriptive subject line. For more than half of the posts to
Usenet, the Subject: line - in fact, only the first 40 characters -
is probably all I'm going to see. The 'n' and 'c' keys get a lot of
use when looking at Usenet.

Actually, 84 groups isn't that bad, as _usually_ only about 45 have
any posts at all, and many of the groups don't even get double-digit
numbers of posts daily (heck, some don't even do that in a month). A
more accurate measure is the total article counts, and that has been
running around 5-600 per day before the news _reader_ (as opposed to
slrnpull) starts killing things.

>> you said two groups are OK? Try
>>
>> Xref: :.*:.*:
>>
>> which should kill posts where the Xref: header contains three colons.
>
>Now that's working and is F-A-S-T!

Glad to help.

>Here's my faster score file (thanks to you), but I have to set each item
>separately; for an unknown reason grouping isn't getting it:

>[*]
>Score: =-9999
> Xref: advocacy
>[*]
>Score: =-9999
> Xref: windows

[snip]
[*]
Score:: =-9999
Xref: advocacy
Xref: windows
Xref: conspiracy
Xref: flame
Xref: kook
Xref: microsoft
Xref: politics
Xref: :.*:.*:

Two colons on the score line, not one.

>% kills all "test" posts not in a *test NG

I kill them all, along with

Score: =-9999
Subject: don
Subject: read

Here, the single colon says this score only applies to posts where the
subject line includes BOTH the string 'don' and 'read'.

>% limits message size in max bytes;
>% if it can't be said in about 400 lines
>% there's to much yapping, it's a binary
>% or unneeded text is not being snipped
>Score: =-9999
> Bytes: 14700

Score:: =-9999
Bytes: 14700
Lines: 400

Again, two colons on the score line to logically _OR_ the conditions.

Actually, I put an exception for several groups where I know there will
occasionally be some longer posts - such as the monthly posting to
news.announce.newgroups (and news.groups and news.lists.misc) of the
list of sanctioned Big Eight newsgroups (~2310 lines).

>Thanks for your time!!

Glad to be able to help!

Old guy

Horton heard a Who named Moe Trin saying:
> On Thu, 04 Oct 2007, in the Usenet newsgroup alt.os.linux.debian, in article
> <FO6dnU2DxIfBupjanZ2dnUVZ_q-jnZ2d@bresnan.com>, sk8r-365 wrote:
<snip>
>
>>Here's my faster score file (thanks to you), but I have to set each item
>>separately; for an unknown reason grouping isn't getting it:
>
>>[*]
>>Score: =-9999
>> Xref: advocacy
>>[*]
>>Score: =-9999
>> Xref: windows
>
> [snip]
>
>[*]
> Score:: =-9999
> Xref: advocacy
> Xref: windows
> Xref: conspiracy
> Xref: flame
> Xref: kook
> Xref: microsoft
> Xref: politics
> Xref: :.*:.*:
>
> Two colons on the score line, not one.
<snip>

>>% limits message size in max bytes;
>>% if it can't be said in about 400 lines
>>% there's to much yapping, it's a binary
>>% or unneeded text is not being snipped
>>Score: =-9999
>> Bytes: 14700
>
> Score:: =-9999
> Bytes: 14700
> Lines: 400
>
> Again, two colons on the score line to logically _OR_ the conditions.

I understand now! Getting to _love_ the "::" usage. slrn is wonderful. Hope it's
never abandoned.

Again, OG of the MT, your help has been invaluable - thank you.

--
sk8r-365
The only way to make Windows "secure":
1) go to http://goodbye-microsoft.com
2) replace existing operating system.