There is a jerk in one of the music groups I use. He posts about 100
headers with the following type subject.

Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}

I get rid of him with this filter.

subject: {\{} and {\}} and {\-} and {\-}

I'm sure there's another fancy way of doing this, but this is my
simple way of doing it.

On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:

>There is a jerk in one of the music groups I use. He posts about 100
>headers with the following type subject.
>
>Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>
>I get rid of him with this filter.
>
>subject: {\{} and {\}} and {\-} and {\-}
>
>I'm sure there's another fancy way of doing this, but this is my
>simple way of doing it.

I found another filter that will work for the music poster jerk.

"To prevent Agent from retrieving message headers that start
with odd characters such as !, $, <, -, etc. (usually spam)"
subject: ={^[^a-z"].*}

With this one from the Agent Filter page it will take only 1 filter to
take out messages starting with odd characters. You won't have to
make a different filter for each different character, as in my OP.

(I ain't a filter guru. Just trying to help out those as ignorant as
I am on the subject.)

On Mon, 27 Feb 2023 16:45:29 -0600, geo@wxyz.com wrote:

>On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:
>
>>There is a jerk in one of the music groups I use. He posts about 100
>>headers with the following type subject.
>>
>>Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>>
>>I get rid of him with this filter.
>>
>>subject: {\{} and {\}} and {\-} and {\-}
>>
>>I'm sure there's another fancy way of doing this, but this is my
>>simple way of doing it.
>
>I found another filter that will work for the music poster jerk.
>
>"To prevent Agent from retrieving message headers that start
>with odd characters such as !, $, <, -, etc. (usually spam)"
>subject: ={^[^a-z"].*}
>
>With this one from the Agent Filter page it will take only 1 filter to
>take out messages starting with odd characters. You won't have to
>make a different filter for each different character, as in my OP.
>
>(I ain't a filter guru. Just trying to help out those as ignorant as
>I am on the subject.)

Doesn't this also eliminate posts where the subject starts with a
number?

--
Remove del for email

On Mon, 27 Feb 2023 17:29:33 -0800, Barry Schwarz <schwarzb@delq.com>
wrote:

>On Mon, 27 Feb 2023 16:45:29 -0600, geo@wxyz.com wrote:
>
>>On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:
>>
>>>There is a jerk in one of the music groups I use. He posts about 100
>>>headers with the following type subject.
>>>
>>>Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>>>
>>>I get rid of him with this filter.
>>>
>>>subject: {\{} and {\}} and {\-} and {\-}
>>>
>>>I'm sure there's another fancy way of doing this, but this is my
>>>simple way of doing it.
>>
>>I found another filter that will work for the music poster jerk.
>>
>>"To prevent Agent from retrieving message headers that start
>>with odd characters such as !, $, <, -, etc. (usually spam)"
>>subject: ={^[^a-z"].*}
>>
>>With this one from the Agent Filter page it will take only 1 filter to
>>take out messages starting with odd characters. You won't have to
>>make a different filter for each different character, as in my OP.
>>
>>(I ain't a filter guru. Just trying to help out those as ignorant as
>>I am on the subject.)
>
>Doesn't this also eliminate posts where the subject starts with a
>number?

You're right! I guess the right one to use would be my first one -
subject: {\{} and {\}} and {\-} and {\-}

Although, it was a music group I made it for, and didn't even consider
numbers posted in such a group. I think I will keep it for just that
group and not Global.

I'm glad I made it clear in one post that I ain't no filter guru. :o)

On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:

>There is a jerk in one of the music groups I use. He posts about 100
>headers with the following type subject.
>
>Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>
>I get rid of him with this filter.
>
>subject: {\{} and {\}} and {\-} and {\-}
>
>I'm sure there's another fancy way of doing this, but this is my
>simple way of doing it.

That is just an encrypted post, trying not to get sued by RIAA for
posting pirate music ... as if they really care these days.
Those groups are largely dead compared to the days when You would see
thousands of new headers every day ... in the clear and I never heard
of anyone being sued. That was Napster.

On Mon, 27 Feb 2023 21:46:06 -0500, gfretwell@aol.com wrote:

>On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:
>
>>There is a jerk in one of the music groups I use. He posts about 100
>>headers with the following type subject.
>>
>>Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>>
>>I get rid of him with this filter.
>>
>>subject: {\{} and {\}} and {\-} and {\-}
>>
>>I'm sure there's another fancy way of doing this, but this is my
>>simple way of doing it.
>
>That is just an encrypted post, trying not to get sued by RIAA for
>posting pirate music ... as if they really care these days.
>Those groups are largely dead compared to the days when You would see
>thousands of new headers every day ... in the clear and I never heard
>of anyone being sued. That was Napster.

I kinda figured that, but usually they use the torrent stuff today.

I've been around when the Warez groups had tons and tons of software
available, and rarely would you find a virus or any malware problem
with the uploads.

Yeah, Usenet is almost totally dead. My provider has over well over
100,000 groups. I go through a big bunch every once in a while and
can find almost none that are still active.

I don't use Web forums because of their censoring any truth they
consider "harmful". So, I'm kinda stuff with what's left of Usenet.

On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:

> There is a jerk in one of the music groups I use. He posts about 100
> headers with the following type subject.
>
> Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>
> I get rid of him with this filter.
>
> subject: {\{} and {\}} and {\-} and {\-}

Best add parentheses like below. Otherwise Agent will match a '-' or '}' in
the Author header even when there isn't one in the Subject header.

subject: ( {\{} and {\}} and {\-} and {\-} )

FYI the second
and {\-}
does not add any value, it will still need only one '-' to match.

> I'm sure there's another fancy way of doing this, but this is my
> simple way of doing it.

A much fancier way looks like this in Agent but is quite long:

subject:{\{[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]\}}

--
Kind regards
Ralph

On Tue, 28 Feb 2023 18:34:01 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Mon, 27 Feb 2023 14:55:40 -0600, steve@yakook.com wrote:
>
>> There is a jerk in one of the music groups I use. He posts about 100
>> headers with the following type subject.
>>
>> Subject: {1a5156ab-a34a-4ec2-a564-00e48564142b}
>>
>> I get rid of him with this filter.
>>
>> subject: {\{} and {\}} and {\-} and {\-}
>
>
>Best add parentheses like below. Otherwise Agent will match a '-' or '}' in
>the Author header even when there isn't one in the Subject header.
>
> subject: ( {\{} and {\}} and {\-} and {\-} )

Got it!

>FYI the second
> and {\-}
>does not add any value, it will still need only one '-' to match.

I thought it would force it to filter only if there were two instances
of the - thingy. Wrong - as usual. :o)
>
>> I'm sure there's another fancy way of doing this, but this is my
>> simple way of doing it.
>
>
>A much fancier way looks like this in Agent but is quite long:
>
>subject:{\{[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f]-[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]\}}

With that one you just gave me a bad headache. :o(