Opened 12 years ago
Last modified 9 years ago
#307 testing defect (fixed)
Labeled spam should not be redelivered when marked as ham
Reported by: | dmorton | Owned by: | mortonda@… |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.3 |
Component: | PHP scripts | Version: | 1.0.1 |
Severity: | normal | Keywords: | labeled rescue |
Cc: |
Description (last modified by anonymous)
When your settings are set to label spam, it delivers it; when you mark it
as ham, it gets delivered again.
Change History (8)
comment:1 Changed 12 years ago by anonymous
- Keywords labeled rescue added
- Milestone set to 1.0.2
comment:2 Changed 12 years ago by rjl
comment:3 Changed 11 years ago by dmorton
- Description modified (diff)
- Milestone changed from 1.0.2 to 1.0.3
I think 'L' is being used for blacklisting. I also wonder if this ticket
would be obsoleted when we open up the scoring to have the better kill levels, aka 4th level patch.
comment:4 Changed 11 years ago by anonymous
Another way to fix this which is impossible right now but possible with
per-address stats... Look at the matching policy and take action according to spam_lovers and/or spam_kill_level. But there's no way currently to track a maia_user id back to a linked user and policy.
comment:5 Changed 11 years ago by anonymous
- Description modified (diff)
This was supposed ot be in the last comment, not the description:
In any case, this would have to touch a lot of code.... Let's bump this to 1.0.3 or 1.1
comment:6 Changed 9 years ago by mortonda@…
I've tried coding a new type, (P), and it makes for some ugly code; It would probably be better to add a flag field to mmr to designated what happened to the message.
comment:7 Changed 9 years ago by mortonda@…
- Owner changed from rjl to mortonda@…
- Status changed from new to accepted
[1391] works for 1.0.x. I still need to implement for 1.1.x, but I'm not sure if this is how I'd like to do it.
comment:8 Changed 9 years ago by mortonda@…
- Resolution set to fixed
- Status changed from accepted to testing
Just recording David's suggestion for dealing with this issue:
"Perhaps we should add another "type", called "L" for labeled spam.... which the spam quarantine page would look for both S and L, but behave differently on rescue..."
This seems to me to be the best way to handle this issue properly, yes.