Tickets :: [#2911] User must Blacklist and "Report as Spam"

6.0.0-beta1

7/30/25

Summary	User must Blacklist and "Report as Spam"
Queue	IMP
Queue Version	HEAD
Type	Enhancement
State	Rejected
Priority	2. Medium
Owners
Requester	virg2 (at) xiode (dot) com
Created	11/03/2005 (7209 days ago)
Due
Updated	11/28/2005 (7184 days ago)
Assigned
Resolved	11/28/2005 (7184 days ago)
Milestone
Patch	No

11/28/2005 04:13:14 PM	Jan Schneider	Comment #4 State ⇒ Rejected	Reply to this comment
Using blacklist and spam reporting for the same messages doesn't make any sense. If this is necessary you didn't set up your spam processing tools correctly.

11/03/2005 07:24:16 PM	virg2 (at) xiode (dot) com	Comment #3	Reply to this comment
Yeah, I agree with the faked 'from' address problem. It would be great if you could come up with a workable solution to this problem. Another idea I had was to leave the checkboxes checked when the page refreshes after a "Report as Spam" click. That way, it's easier for the user to then perform the blacklist action.

11/03/2005 07:04:09 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
Lots of (most?) spam has a faked From: address. I get a lot of spam that claims to be from me, for example. So I don't think this is a good idea.

11/03/2005 06:41:23 PM	virg2 (at) xiode (dot) com	Comment #1 State ⇒ New Priority ⇒ 2. Medium Type ⇒ Enhancement Summary ⇒ User must Blacklist and "Report as Spam" Queue ⇒ IMP	Reply to this comment
To get rid of unwanted email, the user must perform two actions, Blacklist and "Report as Spam". It might be better if the user could do both by performing one action, for example the "Report as Spam" feature could also blacklist.