A question about spam?

Jude DaShiell jdashiel at panix.com
Mon Dec 19 06:18:18 UTC 2016

a good domain to block is vizyn.com if anyone is interested.  I doubt 
anything of any consequence other than spam will be coming from that 
domain in the future. On Mon, 19 Dec 2016, Jude DaShiell wrote:

> Date: Mon, 19 Dec 2016 01:05:07
> From: Jude DaShiell <jdashiel at panix.com>
> Reply-To: Linux for blind general discussion <blinux-list at redhat.com>
> To: Linux for blind general discussion <blinux-list at redhat.com>
> Subject: Re: A question about spam?
> In email, the Messag-Id: field is supposed to be a fingerprint for email. 
> Perhaps a couple procmail recipes might be useful in this case. The first 
> recipe would treat any email missing a Message-Id: field as junk.  The second 
> recipe would have to be maintained with a data base holding Message-Id: 
> entries from email known to be spam.  Anything found in that data base would 
> also properly be considered junk and treated accordingly.  I'm not that good 
> with procmail yet so haven't tried this yet.  One important thing is to guard 
> that data base by backing it up to local storeage and be prepared to also get 
> its sha512sum and compare it with local edition.  If the two don't match, 
> remote version got tampered.
> On Sun, 18 Dec 2016, Tim Chase wrote:
>> Date: Sun, 18 Dec 2016 23:33:24
>> From: Tim Chase <blinux.list at thechases.com>
>> Reply-To: Linux for blind general discussion <blinux-list at redhat.com>
>> To: blinux-list at redhat.com
>> Subject: Re: A question about spam?
>> On December 18, 2016, Karen Lewellen wrote:
>>> We have Spam assassin here, and I do run sa-learn.
>>> However, I do not run this on addresses that use real names, even
>>> if I know the material is spam.
>>> At what level do programs like spam assassin do the filtering?  Are
>>> there other steps I can take to curb the flow?
>> SpamAssassin (SA) takes the content into consideration, so even if
>> you're receiving spam from known-good addresses, feed it to SA.  It
>> will learn from the content, not just the sender.
>> Depending on how your mail-server is configured, you can also set up
>> catch-all accounts and then direct various sources to custom email
>> addresses.  Because I own our domain, I can have all mail to this
>> list come to blinux.list@<mydomain> which lets me set up filters to
>> the effect "if anything comes to blinux.list@ and isn't also either
>> to the mailing-list or in my personal address-book of people with
>> whom I've previously sent messages, treat it as junk"
>> You can do something similar with GMail which allows you to take your
>> username at gmail.com and append a plus-sign and a tag for filtering
>> such as "username+blinux at gmail.com".
>> Not knowing the peculiars of your particular mail configuration, it's
>> hard to offer better suggestions, but at least you now know enough to
>> train SA with the junk mails even if they come from known-good
>> addresses.
>> -tim
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list


More information about the Blinux-list mailing list