local rule exclude all domains except "my list of approved"
As an increasing amount of SPAM from "boutique" domains began slipping through, I resorted assuring they are marked as SPAM by adding custom rules when sufficiently annoyed. The local rules take this form (thanks to whoever provided the "template" for this): header __LOCAL_FROM_BE From =~ /.\.beauty/i meta LOCAL_BE (__LOCAL_FROM_BE) score LOCAL_BE 2 describe LOCAL_BE from beauty domain Initially I thought it might be fun to create a "match everything except what I list in this rule", so will search the Camel book, to learn or refresh. But, likely someone has already done this, or, there is a simpler way already devised, hence the post. I do not want to block these outright, say at the firewall or Postfix level, just simply flagged as SPAM, as some of these might deserve review at least for entertainment value.
perldoc Mail::SpamAssassin::GeoDB and MaxMind wooes
how to setup ASN plugin with it ? currently i find that _ASNCIDR_ gives not cidr info with GeoIPLite2-ASN.mmdb is this a limit of Lite ?
Re: awl postgresql
Sidney Markowitz wrote on 4/01/23 8:47 pm: There's a typo, which must just be in your email since postgres won't accept it, that should be =+ not += I am not expert it SQL :) Further testing reveals that there is no auto-increment operator in postgres or SQLite SQL, neither += nor =+ The reason why =+ does not get a syntax error is because it is parsed as two separate operators and whitespace is not required and is ignored. In other words, totspace =+ 10 is the same as totspace = +10 which sets totspace to the value 10, which is not what was intended. The change to =+ doesn't fail the syntax, but does cause test t/sql_based_welcomelist.t to fail because the results are wrong. The only syntax that actually works is to include the table name as in totspace = awl.totspace + 10 I have submitted a patch to that effect in bug 8098 for people who do know SQL to review. Benny, if you want to try out that patch, please do so. Sidney
