Rob wrote:
Philip Taylor <[email protected]> wrote:
Rob <[email protected]> wrote:
SeaMonkey has no way to see that an e-mail is "the same as one that
you have seen before". That probably is not true, anyway.
So your ooptions are to disable the detector or to live with it.
Rob, it is a fundamental feature of good software design that
software should adapt to the needs of the user; the user should
never have to adapt to the needs of the software.
Philip Taylor
Yes, but in this case that is not a simple task.
The user says "this is an e-mail I have seen before, it should not
be detected as a scam".
But what properties of the mail do you want to store in a whitelist?
Certainly not the sender address, as it can very easily be spoofed.
Anyone sending a genuine-looking phishing mail will try to use the
usual sender address of the company they want to phish data for.
So, whitelisting on sender address would be an extremely bad idea!
You can store a hash of the message to whitelist it, but I bet that
the messages the user is talking about are not "the same". They
are messages from the same company that have the same general layout,
but their content is not the same.
So what would the software have to store and match to identify "the same"
messages that it should not classify as scam the next time?
It will not be easy...
how about instead of using a white list use a Black list whatever the
user marks as spam. If its not corrected within a week, Make it a
Permanent forever or at least 100 years block.
--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net mailto:[email protected]
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
