Doug Miller wrote:
> In article <[email protected]>, Enoch Root <[email protected]> wrote:
>
>>Enoch Root wrote:
>>
>>
>>>Or, as you /appear/ to be interested in blocking posts to xposted to
>>>_more_than_two_ groups:
>>>
>>>\w+:\w+:\w+
>>
>>Come to think of it, wouldn't just a colon be sufficient?
>
>
> I don't think so. It's fairly common, and entirely legitimate, for posts to
> rec.woodworking to be crossposted to alt.binaries.pictures.woodworking or to
> rec.crafts.woodturning, and, somewhat less commonly, to
> alt.binaries.pictures.furniture, rec.crafts.metalworking, or alt.home.repair.
> So it's probably undesirable to just drop everyything that's crossposted.
>
> Articles that are posted to three or more groups at once are likely to be
> spams or trolls, though -- hence the desire to trap crossposts to multiple
> groups.
Ah, that explains the need for 3. Thanks.
er
--
email not valid
On Mon, 15 May 2006 13:54:38 GMT, Doug Miller wrote:
> That's a good point -- it's *dis*abled in the default setup, and it must be
> *en*abled for my filters to work.
Doug,
I have just gotten nfilter to work with slrn. I had to disable slrn's use of
the XOVER command to do this. (I have no idea what the means, exactly. I just
follwed a discussion that took place some time ago on news.software.readers.)
I have regular expressions enabled in nfilter. But NONE of the garbage present
here is being dropped. Looking at the nfilter messages window, it is clear
that it has read the filter file. But the "Dropped Articles" window shows
nothing has been dropped.
I can identify the rules that should be operative here ... but they don't
appear to be working.
Can you offer any pointers? Is slrn somehow bypassing the proxy?
--
Art
This is a multi-part message in MIME format.
--------------040101020402060500070205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Doug Miller wrote:
> In article <[email protected]>, "Bill Stock" <[email protected]> wrote:
>> I've got my test filter set up as:
>>
>> rec.woodworking flag:XPOST xref:*:*:*
>>
>> Header looks like:
>>
>> Xref: uni-berlin.de rec.woodworking:1274982
>>
>> So this should not be flagged, but it is.
>
> Yes, it should. You told it to. :-)
>
>> What am I doing wrong?
>
> Trying to write regexps without understanding them fully, or not paying as
> much attention as you should. :-)
>
> Asterisk means "match zero or more of the preceding character".
>
> Thus, *:*:* means match zero or more of any character, followed by zero or
> more colons, followed by zero or more colons.
>
> In other words, your filter will flag *anything* in the Xref: header, whether
> there are any colons present or not.
>
> *:.*:.* is probably closer to what you want: zero or more of any character,
> followed by one colon, followed by zero or more of any character, followed by
> one colon, followed by zero or more of any character.
>
> Or you could just download my filter file, instead of trying to write your
> own. (see my sig for details)
>
>
Doug,
How long does it take for the autoresponder? Sent the email hours ago -
nothing.... Guess we all should be thankful for all these posts... It's
forcing me to do what I should have done a long, long time ago. And
thanks for the service Doug...
--------------040101020402060500070205
Content-Type: text/x-vcard; charset=utf-8;
name="jeepnDOGcoloradoCAT.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="jeepnDOGcoloradoCAT.vcf"
begin:vcard
fn:John Dykes
n:Dykes;John
note:Remove the animals to email me....
version:2.1
end:vcard
--------------040101020402060500070205--
In article <[email protected]>, Enoch Root <[email protected]> wrote:
>Enoch Root wrote:
>
>> Or, as you /appear/ to be interested in blocking posts to xposted to
>> _more_than_two_ groups:
>>
>> \w+:\w+:\w+
>
>Come to think of it, wouldn't just a colon be sufficient?
I don't think so. It's fairly common, and entirely legitimate, for posts to
rec.woodworking to be crossposted to alt.binaries.pictures.woodworking or to
rec.crafts.woodturning, and, somewhat less commonly, to
alt.binaries.pictures.furniture, rec.crafts.metalworking, or alt.home.repair.
So it's probably undesirable to just drop everyything that's crossposted.
Articles that are posted to three or more groups at once are likely to be
spams or trolls, though -- hence the desire to trap crossposts to multiple
groups.
--
Regards,
Doug Miller (alphageek at milmac dot com)
It's time to throw all their damned tea in the harbor again.
"Doug Miller" <[email protected]> wrote in message
news:[email protected]...
> In article <[email protected]>, "Bill Stock"
> <[email protected]> wrote:
>>I've got my test filter set up as:
>>
>>rec.woodworking flag:XPOST xref:*:*:*
>>
>>Header looks like:
>>
>>Xref: uni-berlin.de rec.woodworking:1274982
>>
>>So this should not be flagged, but it is.
>
> Yes, it should. You told it to. :-)
>
>>What am I doing wrong?
>
> Trying to write regexps without understanding them fully, or not paying as
> much attention as you should. :-)
>
> Asterisk means "match zero or more of the preceding character".
>
> Thus, *:*:* means match zero or more of any character, followed by zero or
> more colons, followed by zero or more colons.
>
> In other words, your filter will flag *anything* in the Xref: header,
> whether
> there are any colons present or not.
>
> *:.*:.* is probably closer to what you want: zero or more of any
> character,
> followed by one colon, followed by zero or more of any character, followed
> by
> one colon, followed by zero or more of any character.
Thanks, but the above was the example given in the FAQ.
BTW, any idea how precedence works? If my message is caught by a rule, will
subsequent rules still be applied? The reason I ask, is that I had an AFLAG
that did not seem to get applied, as the message was trapped by an earlier
rule.
> Or you could just download my filter file, instead of trying to write your
> own. (see my sig for details)
>
>
> --
> Regards,
> Doug Miller (alphageek-at-milmac-dot-com)
>
> Get a copy of my NEW AND IMPROVED TrollFilter for NewsProxy/Nfilter
> by sending email to autoresponder at filterinfo-at-milmac-dot-com
> You must use your REAL email address to get a response.
>
> Download Nfilter at http://www.milmac.com/np-120.exe
>
In article <[email protected]>, "Bill Stock" <[email protected]> wrote:
>I've got my test filter set up as:
>
>rec.woodworking flag:XPOST xref:*:*:*
>
>Header looks like:
>
>Xref: uni-berlin.de rec.woodworking:1274982
>
>So this should not be flagged, but it is.
Yes, it should. You told it to. :-)
>What am I doing wrong?
Trying to write regexps without understanding them fully, or not paying as
much attention as you should. :-)
Asterisk means "match zero or more of the preceding character".
Thus, *:*:* means match zero or more of any character, followed by zero or
more colons, followed by zero or more colons.
In other words, your filter will flag *anything* in the Xref: header, whether
there are any colons present or not.
*:.*:.* is probably closer to what you want: zero or more of any character,
followed by one colon, followed by zero or more of any character, followed by
one colon, followed by zero or more of any character.
Or you could just download my filter file, instead of trying to write your
own. (see my sig for details)
--
Regards,
Doug Miller (alphageek-at-milmac-dot-com)
Get a copy of my NEW AND IMPROVED TrollFilter for NewsProxy/Nfilter
by sending email to autoresponder at filterinfo-at-milmac-dot-com
You must use your REAL email address to get a response.
Download Nfilter at http://www.milmac.com/np-120.exe
In article <[email protected]>, "Mortimer Schnerd, RN" <[email protected]> wrote:
>Enoch Root wrote:
>> Enoch Root wrote:
>>
>>> Or, as you /appear/ to be interested in blocking posts to xposted to
>>> _more_than_two_ groups:
>>>
>>> \w+:\w+:\w+
>>
>> Come to think of it, wouldn't just a colon be sufficient?
>
>
>I have no idea. Now, taking your posting, I came up with this but it doesn't
>seem to be what I want... I'm still seeing stuff in other newsgroups
> crossposted
>to 3 groups....
>
>* drop xref:\w+:\w+:\w+
>
>I obviously don't know what I'm doing but I'm hoping you do. Lead me by the
>hand, will ya?
I think that oughta catch it -- but you have to stop and restart Nfilter
before changes to the filter file take effect.
--
Regards,
Doug Miller (alphageek-at-milmac-dot-com)
Get a copy of my NEW AND IMPROVED TrollFilter for NewsProxy/Nfilter
by sending email to autoresponder at filterinfo-at-milmac-dot-com
You must use your REAL email address to get a response.
Download Nfilter at http://www.milmac.com/np-120.exe
In article <[email protected]>, Enoch Root
<[email protected]> wrote:
>Doug Miller wrote:
>> In article <[email protected]>, "Bill Stock" <[email protected]>
> wrote:
>
>>>rec.woodworking flag:XPOST xref:*:*:*
>
>>>Xref: uni-berlin.de rec.woodworking:1274982
>>>
>>>So this should not be flagged, but it is.
>
>> Yes, it should. You told it to. :-)
>
>> Thus, *:*:* means match zero or more of any character, followed by zero or
>> more colons, followed by zero or more colons.
>
>> *:.*:.* is probably closer to what you want: zero or more of any character,
>> followed by one colon, followed by zero or more of any character, followed by
>
>> one colon, followed by zero or more of any character.
>
>An illustration of the difference between mere globs, and more powerful
>regular expressions.
>
>Globbing text, a "*" will grab anything, but using regular expressions a
>"*" is a "zero or more" quantifier for the preceding symbol, which in
>this case is a character (irrelevant, since you are matching zero or
>more of them it'll succeed in any case).
>
>In regex: "." is any character and like Doug says, is prolly what you
>want. You could also be stricter (always better) and use \w in
>combination with "+":
>
>\w+:\w+
>
>Or, as you /appear/ to be interested in blocking posts to xposted to
>_more_than_two_ groups:
>
>\w+:\w+:\w+
Correct me if I'm wrong... but I believe that \w matches A..Z, a..z, 0..9, and
underscore -- but *not* hyphen, leaving the possibility that something
cross-posted to, say, alt.activism.death-penalty would slip through. This is
IMO far from implausible.
There are also a number of newsgroups with '+' in their names, and even a few
containing "&"; although less likely to appear, these would slip through also.
Possible refinements to avoid this are:
[\w-\+&]+:[\w-\+&]+:[\w-\+&]+:
or
[^:]+:[^:]+:[^:]+:
or, even more simply,
([^:]+:){2,}
[^:]+ means "one or more things that are not a colon"
[^:]+: means "one or more things that are not a colon, followed by a colon"
{2,} means "two or more occurrences of the stuff immediately preceding"
so ([^:]+:){2,} means "two or more occurrences of (one or more things that are
not a colon, followed by a colon)"
--
Regards,
Doug Miller (alphageek-at-milmac-dot-com)
Get a copy of my NEW AND IMPROVED TrollFilter for NewsProxy/Nfilter
by sending email to autoresponder at filterinfo-at-milmac-dot-com
You must use your REAL email address to get a response.
Download Nfilter at http://www.milmac.com/np-120.exe
In my opinion, this is the single most useful line you can put into nfilter:
* drop xref:*:*:*
Now, I know some people do want to see crossposted articles, and it's true,
they are often of interest in a certain newsgroup. In my experience though,
that one line gets rid of massive quantities of crap. Kooks rarely post to a
single group, though it does happen on occasion. If I'm reading rec.ww, I'm
willing to bet that I have no interest whatsoever in something that's also
crossposted to alt.guns.kkk.soc.whatever.
--
Bob
Travel and Astronomy Photos
http://www3.sympatico.ca/bomo
"Bill Stock" <[email protected]> wrote in message
news:[email protected]...
> I've got my test filter set up as:
>
> rec.woodworking flag:XPOST xref:*:*:*
>
> Header looks like:
>
> Xref: uni-berlin.de rec.woodworking:1274982
>
> So this should not be flagged, but it is. What am I doing wrong?
>
>
>
>
>
Mortimer Schnerd, RN wrote:
> Enoch Root wrote:
>
>>Enoch Root wrote:
>>
>>
>>>Or, as you /appear/ to be interested in blocking posts to xposted to
>>>_more_than_two_ groups:
>>>
>>>\w+:\w+:\w+
>>
>>Come to think of it, wouldn't just a colon be sufficient?
>
>
>
> I have no idea. Now, taking your posting, I came up with this but it doesn't
> seem to be what I want... I'm still seeing stuff in other newsgroups crossposted
> to 3 groups....
>
> * drop xref:\w+:\w+:\w+
>
> I obviously don't know what I'm doing but I'm hoping you do. Lead me by the
> hand, will ya?
maybe a space after the first colon? dunno
3+ ngs should be covered by :\w+:
But you are using a MS product, and they probably have their own
(broken) idea what a regex is.
Assuming that, for 3+ groups go with something like what Doug originally
gave you:
drop xref:.+:.+:.+
Note I'm also assuming you are right and no space after the first colon
is required. You could try it both ways.
er
--
email not valid
Doug Miller wrote:
> In article <[email protected]>, "Bill Stock" <[email protected]> wrote:
>>rec.woodworking flag:XPOST xref:*:*:*
>>Xref: uni-berlin.de rec.woodworking:1274982
>>
>>So this should not be flagged, but it is.
> Yes, it should. You told it to. :-)
> Thus, *:*:* means match zero or more of any character, followed by zero or
> more colons, followed by zero or more colons.
> *:.*:.* is probably closer to what you want: zero or more of any character,
> followed by one colon, followed by zero or more of any character, followed by
> one colon, followed by zero or more of any character.
An illustration of the difference between mere globs, and more powerful
regular expressions.
Globbing text, a "*" will grab anything, but using regular expressions a
"*" is a "zero or more" quantifier for the preceding symbol, which in
this case is a character (irrelevant, since you are matching zero or
more of them it'll succeed in any case).
In regex: "." is any character and like Doug says, is prolly what you
want. You could also be stricter (always better) and use \w in
combination with "+":
\w+:\w+
Or, as you /appear/ to be interested in blocking posts to xposted to
_more_than_two_ groups:
\w+:\w+:\w+
er
--
email not valid
On 14/05/2006 3:05 PM, Doug Miller wrote:
> Trying to write regexps without understanding them fully, or not paying as
> much attention as you should. :-)
> [...]
However, it's worth noting that regular expressions are only used if
enabled in the configuration settings. How many of these people have
that box checked off?
On 2006-05-15, Art Greenberg <[email protected]> ranted thusly:
> Can you offer any pointers? Is slrn somehow bypassing the proxy?
Hi Art, sorry I wasn't more specific in that other response--in
your .slrnrc file you need a line like:
set scorefile "News/Score"
and in your score file:
[*]
Score: -9999
NNTP-Posting-Host: .*\.telecom\.net\.ar
To get those posts.
er
--
email not valid
In article <[email protected]>, [email protected] wrote:
>On Mon, 15 May 2006 13:54:38 GMT, Doug Miller wrote:
>> That's a good point -- it's *dis*abled in the default setup, and it must be
>> *en*abled for my filters to work.
>
>Doug,
>
>I have just gotten nfilter to work with slrn. I had to disable slrn's use of
>the XOVER command to do this. (I have no idea what the means, exactly. I just
>follwed a discussion that took place some time ago on news.software.readers.)
>
>I have regular expressions enabled in nfilter. But NONE of the garbage present
>here is being dropped. Looking at the nfilter messages window, it is clear
>that it has read the filter file. But the "Dropped Articles" window shows
>nothing has been dropped.
>
>I can identify the rules that should be operative here ... but they don't
>appear to be working.
>
>Can you offer any pointers? Is slrn somehow bypassing the proxy?
Looks that way, but I'm not sure. I'm not familiar with slrn.
>
--
Regards,
Doug Miller (alphageek-at-milmac-dot-com)
Get a copy of my NEW AND IMPROVED TrollFilter for NewsProxy/Nfilter
by sending email to autoresponder at filterinfo-at-milmac-dot-com
You must use your REAL email address to get a response.
Download Nfilter at http://www.milmac.com/np-120.exe
Enoch Root wrote:
> Enoch Root wrote:
>
>> Or, as you /appear/ to be interested in blocking posts to xposted to
>> _more_than_two_ groups:
>>
>> \w+:\w+:\w+
>
> Come to think of it, wouldn't just a colon be sufficient?
I have no idea. Now, taking your posting, I came up with this but it doesn't
seem to be what I want... I'm still seeing stuff in other newsgroups crossposted
to 3 groups....
* drop xref:\w+:\w+:\w+
I obviously don't know what I'm doing but I'm hoping you do. Lead me by the
hand, will ya?
--
Mortimer Schnerd, RN
[email protected]
In article <[email protected]>, Doug Payne <[email protected]> wrote:
>On 14/05/2006 3:05 PM, Doug Miller wrote:
>
>> Trying to write regexps without understanding them fully, or not paying as
>> much attention as you should. :-)
>> [...]
>
>However, it's worth noting that regular expressions are only used if
>enabled in the configuration settings. How many of these people have
>that box checked off?
That's a good point -- it's *dis*abled in the default setup, and it must be
*en*abled for my filters to work.
However...
a) this fact is noted in the comments at the beginning of my filter file, and
b) it's not related to the OP's problem. He clearly *did* have regexps
enabled, as demonstrated by the fact that his regexp was trapping posts. The
problem was that an error in the regexp caused it to trap posts that he wanted
it to pass.
--
Regards,
Doug Miller (alphageek-at-milmac-dot-com)
Get a copy of my NEW AND IMPROVED TrollFilter for NewsProxy/Nfilter
by sending email to autoresponder at filterinfo-at-milmac-dot-com
You must use your REAL email address to get a response.
Download Nfilter at http://www.milmac.com/np-120.exe