Custom rulesets for SpamAssassin which are not part of the official distro.
Before running these rules please do the following:
1. Read any extra info available with the rules, including the comments
in the .cf files.
2. Check to make sure that the default scores in these rules fit your
installation. You might want to modify scores.
3. Make sure to --lint the rules after loading them.
4. Test the new rulesets. Keep an eye on hits from the new rules to
determine if the scoring is right for you.
===> The following configuration options are available for spamass-rules-20190101:
AIRMAX=off: Some custom rulesets
BACKHAIR=off: Catch those ugly, unsightly HTML tags
BOGUS_VIRUS=on: Catch 'collateral spam' caused by viruses
CHICKENPOX=off: Catch spam like 'l.ooks f|or th.is garb+age'
DBRACKETS=on: Double-brackets around To header address
EVILNUMBERS=off: Phone numbers, PO boxes, ... from spam
MANGLED=off: Looks for obfuscated/gappy words
MIMEVLD=on: Some mime validation rules
RANDOM=on: Detects spamware mistakes like: %RANDOM_WORD
TRIPWIRE=on: Matches 3 chars that shouldn't be together
====> Catch spam written in...
CHINESE=off: Chinese
GERMAN=off: German
GREEK=off: Greek
POLISH=off: Polish
====> Options available for the group BLACKLIST
AHBL=off: AHBL Blacklist
MALWARE=off: Malware Patrol
MSPIKE=on: mailspike.net blacklist
NIXSPAM=on: NiX Spam blacklist
====> Looks at alphanum, hex, lower-, uppercase chars: you have to select exactly one of them
WEEDS1=off: Less restrictive rules
WEEDS2=on: More restrictive rules
===> Use 'make config' to modify these settings
The custom rulesets are installed in /usr/local/etc/mail/spamassassin
Before running these rules please do the following:
1. Read any extra info available with the rules, including the comments
in the .cf files.
2. Check to make sure that the default scores in these rules fit your
installation. You might want to modify scores.
3. Make sure to --lint the rules after loading them.
4. Test the new rulesets. Keep an eye on hits from the new rules to
determine if the scoring is right for you.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Update to 20190101
This is supposed to silence the Pel 5.28 deprecation warnings
From the Maintainer:
I have updated some of the rules files an changed the default options
because for most files sa-update is the preferred solution
PR: 234025
Submitted by: maintainer
Reported by: cy
Move {mail,japanese}/p5-Mail-SpamAssassin to &/spamassassin, in the name of
improving accessibility.
I think people who want to just find the port/package and install it are
more likely to look for "spamassassin the program" than "spamassassin the
perl module collection."
- Update to 20120817
- Switch to new options framework
- Convert to new Makefile header
PR: ports/175201
Submitted by: Michael Ranner <michael@ranner.eu> (maintainer)
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
