| Summary | dspam integration for simple spam filtering |
| Queue | Ingo |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | liamr (at) deathstar (dot) org |
| Created | 8/9/07 (6820 days ago) |
| Due | |
| Updated | 11/13/13 (4532 days ago) |
| Assigned | |
| Resolved | 11/13/13 (4532 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Version ⇒ Git master
State ⇒ Accepted
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ dpsam integration for simple spam filtering
Queue ⇒ Ingo
State ⇒ New
solution scores spam by looking for anything greater or equal to a
numerical score, or by looking for a number of repeating characters.
I believe the best header to base refiling messages identified by
DSPAM as spam, is X-DSPAM-Result, which returns values like..
"Innocent", "Whitelisted", and "Spam".
Our default spam rule is..
X-DSPAM-Result is "Spam", Deliver to folder "Spam" [stop]
I'd like to see the ability to specify an exact string match for a
specified header.