Tim,
I understand that ST path to fighting unwanted mail is going to be centered around SPAMFOO going forward since that is the solution you invested in. Was hoping to get a report phishing button to allow those without a spamfoo license to get some user feedback classification to train our own systems with. Thanks for taking the time to give feedback.
Douglas,
My proposal would drop the messages marked as phishing into a separate training folder from the one you and I currently pull messages from when someone marks it as Junk. (Example: Spool/Phishing and Spool/Junk) A report phishing button would move the classification upstream to the user before it ever hits that training folder. To me it is purely another classifying data point I can use to influence my system and how it takes action on messages reported by users.
On false positives, I'd treat those the same way I already handle junk mis-flags today: review and correct as needed. In practice I don't expect many. From my perspective someone who doesn't recognize phishing is unlikely to blindly click "report phishing" over "report junk" in the first place. The button itself requires a baseline of intent to use correctly.
There's also a support-side win here. Right now when a customer flags something suspicious, it often turns into a support ticket where we manually confirm "yes, that's phishing". That is time that eats into other work. A dedicated button turns that into self-service: users get a clear, obvious path to report it themselves, we get an immediate alert, and it skips the hand-holding entirely.
Its not a monumental feature addition but it helps with filtering accuracy and can educate users at the same time.