Message rules

[Ray]

I have configured message rules every way possible but cannot delete any
messages.
I choose Apply Where the message is on - alt.binaries.images.fun
Where the From line contains - Idol Basics
Delete it
Apply to folder - alt.binaries.images.fun
Close

Nothing changes - the asshole is still there with all his damned yenc
entries

 

[Bob I]

You CAN'T delete messages, only hide them, by marking as read and
showing UNread.

 

[...winston]

"Ray" wrote in message

I have configured message rules every way possible but cannot delete any
messages.
I choose Apply Where the message is on - alt.binaries.images.fun
Where the From line contains - Idol Basics
Delete it
Apply to folder - alt.binaries.images.fun
Close

Nothing changes - the asshole is still there with all his damned yenc
entries[/QUOTE][/QUOTE]
WLM 11 (the version you posted your question)
- Folders tab > Message Rules
Create the rule (ensure you type in the exact From name and choose the
delete option, then check the rule to make it active for incoming messages)

To apply the rule for existing messages previously downloaded and present
when using WLM
- Folders tab > Message Rules
Select the Rule
Click Apply Now
Select the Rule (it will be highlighted in blue) and the rule action will
appear in the 'Rule Description' field
Click Browse
Scroll and select the newsgroup
Click OK
Verify that the newsgroup is shown in the 'Apply to folder' field and the
rule in the 'Rule Description' field
Click Apply Now

As a test of the above, I temporarily created a rule for this newsgroup and
deleted some previously downloaded posts with 'From' names using two words
with an included space (e.g. Ken Blake), thus a rule in WLM using the above
method should also work for Idol Basics. Apologies to my friend Ken for
being the validation test subject.

Note: Manually applying a rule only impacts messages that are previously
downloaded when shown in your WLM views. For the rule to work on future
messages it has to be active and will perform its intended function once
future messages are downloaded (i.e. after the message arrives). To avoid
conflict with other rules, ensure that your rule has the appropriate
priority and stops processing.

 

[XS11E]

I have configured message rules every way possible but cannot
delete any messages.
I choose Apply Where the message is on - alt.binaries.images.fun
Where the From line contains - Idol Basics
Delete it
Apply to folder - alt.binaries.images.fun
Close

Nothing changes - the asshole is still there with all his damned
yenc entries

A. you need a 'real' newsreader to do much filtering, WLM is far from a
functional newsreader.

B. FWIW, yEnc is the proper way to post to binary groups unless the
group has decided otherwise. I don't know if that group is one that
has?

 

[SC Tom]

A. you need a 'real' newsreader to do much filtering, WLM is far from a
functional newsreader.

B. FWIW, yEnc is the proper way to post to binary groups unless the
group has decided otherwise. I don't know if that group is one that
has?

A. If you (not "you" personally) know how to write rules and use the blocked senders list correctly, you can block just
about anything or anyone's post. Granted, it's a never-ending job because of nym-shifters and spammers, but it can be
done quite well with WLM or OE. I block items and posters just as well and easily in WLM v14.xx and OE6 as I do with
Xnews.

B. No matter what the binary group is, there are still posters that upload porn and unwanted binaries. Just the way it
is. Unfortunately, quite often, there's more spam than actual wanted content in the binary groups, but it would take
longer to block them all than it would to just skim over it to whatever IS wanted.

 

[Nil]

A. If you (not "you" personally) know how to write rules and use
the blocked senders list correctly, you can block just about
anything or anyone's post. Granted, it's a never-ending job
because of nym-shifters and spammers, but it can be done quite
well with WLM or OE. I block items and posters just as well and
easily in WLM v14.xx and OE6 as I do with Xnews.

That's not possible. Xnews's score system is far more capable and
flexible than any of Microsoft's email or netnews products. Xnews can
filter on anything in the header and criteria can be defined using
regular expressions. MS's products can't do that.

 

[SC Tom]

That's not possible. Xnews's score system is far more capable and
flexible than any of Microsoft's email or netnews products. Xnews can
filter on anything in the header and criteria can be defined using
regular expressions. MS's products can't do that.

So you're telling me I can't do what I'm already doing? Thank you, Nostradamus

 

[Nil]

So you're telling me I can't do what I'm already doing? Thank you,
Nostradamus

I'm skeptical. Say a troll posts through the same googlegroups account
but constantly changes names. How would WLM and OE filter them out? Or
what if there's someone who forges another poster's name, but the
forger posts through a different news service. Could you get OE to find
those? I could think of dozens of other situations that Xnews or
certain other readers can easily and quickly handle. OE's has just a
paltry choice of filter criteria available, and I just don't think it's
up to the task.

 

[SC Tom]

I'm skeptical. Say a troll posts through the same googlegroups account
but constantly changes names. How would WLM and OE filter them out? Or
what if there's someone who forges another poster's name, but the
forger posts through a different news service. Could you get OE to find
those? I could think of dozens of other situations that Xnews or
certain other readers can easily and quickly handle. OE's has just a
paltry choice of filter criteria available, and I just don't think it's
up to the task.

I'm not doing a bunch of different things in Xnews, so I've never delved deeply into it. And I'm sure it is much more
versatile than a number of other news readers (including WLM and OE), but my original statement was "I block items and
posters just as well and easily in WLM v14.xx and OE6 as I do with Xnews" and I stand by that statement. I started off
years ago writing my own rules in Outlook at work, so I found it rather simple to continue doing that on my home PCs
with WLM and OE.
Since I use those three programs more than I use Xnews, I consider myself a little more adept in them. Xnews has
tremendous power and abilities in the blocking and rules department, but mostly I use the blocked sender's list in it
(which I don't find as versatile as OE's) and the score file, which is very easy to work with for simple things, but can
get very involved, and since I don't use it as much as the others, I haven't bothered to learn all the ins and outs of
it. There are only a few binary groups I frequent, so it wasn't worth a lot of effort on my part to go farther than I
have with it. But I agree with you, it is a great news reader.

 

[VanguardLH]

I have configured message rules every way possible but cannot delete any
messages.
I choose Apply Where the message is on - alt.binaries.images.fun
Where the From line contains - Idol Basics
Delete it
Apply to folder - alt.binaries.images.fun
Close

Nothing changes - the asshole is still there with all his damned yenc
entries

I haven't used WLM is quite awhile (and that was before v15 where
Microsoft screwed it up even worse by removing proper quoting) but I
recall you could define rules that delete messages (from the local
store, not from the server).

Look at the order of your rules. Perhaps you have a rule before this
one which has the stop-clause and is firing. It a rule fires and has
the stop-clause in it then no following rules are exercised on that
article.

Look at the raw source for the article (in Outlook Express, you hit
Ctrl+F3 to see the raw source so it might be the same in WLM). What you
see rendered in the GUI may not be what's actually in the article.
That's because ISO encoding could be used in several headers (From,
Subject, etc). What you see looks like ASCII-7 text but it could be
encoded text. For example, you might see "Subject: Idol Basics" in the
GUI but the raw source shows "Subject: =?<charset>?=...". Microsoft
tests on the actual value, not the rendered value. Your rule is testing
on the ASCII-7 text string you see but the poster is using the old trick
of using encoding so your text rule won't see the same string in the raw
source of the article.

For example, there's a Roger poster in a newsgroup that I don't want to
see his posts (I test more than just on "Roger" in the headers to
identify him and not some other Roger). He fluctuates his nym by using
ASCII-8 and encoded text strings, like Roger, Rôger, Rogêr, Rôgêr, and
=?...?R=F4g=EAr?= (I forget what encoding he uses but then my filter
skips over the encoding spec portion, anyway). So my rule, along with
testing on the e-mail address in the From header (an overview header)
and the injection node in the Path header (a non-overview header).
Encoding can also be used in the Subject header. They use encoding that
looks like ASCII-7 text to you in the rendered version in the GUI but
testing on that string will fail because the actual string in the header
is an encoded string, like "=?<encoding>?<string>?=". Yep, if they use
encoding then you have to test on the actual encoding string, not its
rendered (displayed) string.

If the boob is flooding the newsgroup (like Panzke in the Windows Vista
group and like Bullwinkle in the 24hoursupport.helpdesk group), do you
really want to see ANY of his posts? Once someone behaves like a
hijacker of a group, just filtering out ALL their posts. And don't
bother telling them that you filtered them out (as it could prod them to
nymshift and it makes you look foolish in a vacuous threat). If they
have enough info that's stable in their headers to identify them, filter
them out. Alas, you're using a weak newsreader (WLM) for filtering as
you can only test on the overview headers (what your newsreader gets
when it gets a list of articles) and none of the other non-overview
headers (that are available when you retrieve the body which retrieves
the entire article).

 

[...winston]

"VanguardLH" wrote in message I haven't used WLM is quite awhile (and that was before v15 where
Microsoft screwed it up even worse by removing proper quoting) but I
recall you could define rules that delete messages (from the local
store, not from the server).

That is correct (all deletion occurs after the message is downloaded to the
local store)

 

[DanS]

For example, there's a Roger poster in a newsgroup that I
don't want to see his posts (I test more than just on
"Roger" in the headers to identify him and not some other
Roger). He fluctuates his nym by using ASCII-8 and encoded
text strings, like Roger, Rôger, Rogêr, Rôgêr, and
=?...?R=F4g=EAr?= (I forget what encoding he uses but then
my filter skips over the encoding spec portion, anyway).
So my rule, along with testing on the e-mail address in the
From header (an overview header) and the injection node in
the Path header (a non-overview header).

I don't think I'd want to filter on anyting other than an XOVER
header in binary groups. The larger binary groups anyway...as
that requires a HEAD command for each individual article.

 

[VanguardLH]

I don't think I'd want to filter on anyting other than an XOVER
header in binary groups. The larger binary groups anyway...as
that requires a HEAD command for each individual article.

I don't have access to an NNTP server that supports the XPAT command
(plus I don't think my newsreader supports it). Having to do searches
on non-overview headers using XPAT is resource intensive (or seen as a
waste of resources) to the server. However, if you have an NNTP server
and client that both support XPAT then that's one way to filter on the
non-overview headers without having to download the entire body of the
article (which would include the MIME/yEnc encoded part for the
attachment).

I don't visit the binary group the OP mentioned (I don't bother with any
binary groups) so I don't know if testing on the From header (which is
an overview header) would work to identify the person that the OP claims
is trying to hijack that group with a flood of supposedly worthless
posts. If the offending poster is using an identity they keep stable
then filtering will work on the From header. It was in my example of
looking for a poster named Roger that I had to use other headers to make
sure I wasn't filtering out the other Rogers. Other headers might be
needed to better identify an unwanted poster. If the From header is
sufficient then just use that.

I can't tell if Ray is bitching about one poster that is flooding a
group with repeat posts or if he's bitching about the poster using yEnc
to encode the attachments. Windows Live Mail which is hardly a sane
choice for yanking binary attachments from posts in binary groups. If
you want to be yanking binaries then use a newsreader designed for that.
Microsoft supports MIME for encoding, not yEnc which is used quite
heavily in binary groups (to squeeze down by a few more bytes despite it
is a poor encoding scheme). If he's bitching about yEnc encoding
instead of some flood of posts by the same poster then he choose the
wrong newsreader to retrieve binary content. None of Microsoft's NNTP
clients excel at handling binaries.

 

[Char Jackson]

I can't tell if Ray is bitching about one poster that is flooding a
group with repeat posts or if he's bitching about the poster using yEnc
to encode the attachments. Windows Live Mail which is hardly a sane
choice for yanking binary attachments from posts in binary groups. If
you want to be yanking binaries then use a newsreader designed for that.
Microsoft supports MIME for encoding, not yEnc which is used quite
heavily in binary groups (to squeeze down by a few more bytes despite it
is a poor encoding scheme).

yEnc is at least as good as uuencode as far as ability to reliably
transport 8-bit data over a 7-bit medium, and much better than
uuencode in terms of overhead, about 2% versus 30-40%. There are valid
reasons why yEnc so quickly became the norm in binary groups.

I agree with the rest of your points.

 

[Ray]

That's exactly what I've done.[/QUOTE][/QUOTE]
WLM 11 (the version you posted your question)
- Folders tab > Message Rules
Create the rule (ensure you type in the exact From name and choose the
delete option, then check the rule to make it active for incoming messages)

To apply the rule for existing messages previously downloaded and present
when using WLM
- Folders tab > Message Rules
Select the Rule
Click Apply Now
Select the Rule (it will be highlighted in blue) and the rule action will
appear in the 'Rule Description' field
Click Browse
Scroll and select the newsgroup
Click OK
Verify that the newsgroup is shown in the 'Apply to folder' field and the
rule in the 'Rule Description' field
Click Apply Now