[MlMt] Finer control of blacklist

[Henry Seiden]

A one-off rule for spam filtering seems doomed to fail getting all 
possible combinations, eventually.

I’m (un)lucky enough to have to filter many forms of junk mail 
including traditional spam, among several accounts. Four out of eight 
accounts have much more spam and much more activity, so I think that the 
more active with good (non spam mail) an account/source us the more junk 
you’ll get.

All-in-all, I filter all my incoming email with SpamSieve which does a 
great job overall. I happen to use a separate email drone set up outside 
of my MailMate app to do it and have been doing so for years.

But good luck to you.

Respectfully,

Henry Seiden
- -
Techworks Pro Co.
E: info<at>techworkspro<dot>com
W: http://techworkspro.com

On 20 Oct 2022, at 19:02, Randall Gellens wrote:

> On 18 Oct 2022, at 16:23, Malcolm Fitzgerald wrote:
>
>> I receive mail from a person that I always want to block. They always 
>> use the name "Steve Wroblewski" but they use a different email 
>> address each time. The options for blocking seem to be "User Name 
>> <email>" or "<email>".
>>
>> Is it possible for me to block this person using their name? Or 
>> should I set up a rule for this? I simply want email from them to be 
>> permanently deleted.
>
> I have a rule exactly like this in my "Spam (obvious) rule":
>
> [From -> Name] [is] [xxx]
>
> In my case, the spam has a consistent name and part of the subject, 
> with different from and to addresses, and modifications of the 
> subject, so my rule is a compound rule:
>
> [All} of the following are true
>    [From -> Name] [is] [Mel Gonzales]
>    [Subject] [Contains] [Electronic Waste Collection]
>
>
>
> --Randall
> _______________________________________________
> mailmate mailing list
> mailmate at lists.freron.com
> https://lists.freron.com/listinfo/mailmate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20221020/f6a6b28f/attachment-0001.htm>