Project Summary
The main idea behind was in situation where you have SpamAssassin installed on the mail server itself and there's no use to have another spam procesing engine.
For instance I have SA installed on my home mailserver and I have the office email account (no SA at office) and I would like to use my home SA to identify junk.
On my office account I have Report as Spam (Rspam) Plugin installed so I didn't touch learn/report stuff. Of course spamc is still required (it usualy comes already installed in most modern distros). If this makes sense I'll add port option, ssl, and username option.
In a Nutshell, sa-junk-plugin...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in March, 2007
ending with its most recent commit over 16 years ago
Quick Reference
GNU General Public License v2.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
This Project has No vulnerabilities Reported Against it
Did You Know...
-
...
55% of companies leverage OSS for production infrastructure
-
...
you can embed statistics from Open Hub on your site
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
compare projects before you chose one to use
30 Day SummaryMay 25 2016 — Jun 24 2016
|
12 Month SummaryJun 24 2015 — Jun 24 2016
|
