On 29/03/2017 3:58 AM, NFN Smith wrote:
Daniel wrote:
One of my UseNet groups has been getting a lot of pester posts from
someone calling themselves "mogulah" so yesterday I made a filter
using that for the Sender Contains field.

Today more posts from "mogulah" but no filtering out.

As shown below, I'm using the production version of SM. Is filtering
not working on this??


Filtering should work fine -- if something isn't working, it's generally
a matter of making sure that you have built your filter correctly.

I have a number of bozo filters created for various usenet NGs, and they
do what I need them to do.

For this particular one, what may be getting you is that you're looking
on the Sender: header, rather than the From: header (and use "contains"
rather than "is"), and that the text that you're looking for isn't in
that header.

Sorry, my typo ... I actually selected "From" as there is no listing for "Sender"!!

To be sure that you're looking for the correct content and the correct
header, it's good to use Ctrl-U to look at the raw content of an
offending message (including the headers).  Look carefully for the
identification of the sender, whether display name, email address, etc.,
and note which headers show that info.

FWIW, I just checked a few Usenet posts, and on my feed (coming from
aioe.org), I'm not seeing any messages that show a Sender: header. I
don't remember NNTP specs in that area without looking it up, but I
suspect that Sender: is not a header that's normally used.  The only
header that's reliable for identifying a sender is the From: line.

Smith

Today, I've made a similar filter for this mozilla server because, today, the mozilla.test group received garbage posts from "FABIO"!!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 SeaMonkey/2.46 Build identifier: 20161213183751
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to