Summary: | Enhancement - Mark Message As Not Spam | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Rob <r.tirrell> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Rob
2005-04-12 04:37:51 UTC
Spam is still mail: UCE = Unsolicited Commercial Email. So "Mark as Mail" would be wrong, technically. Do you agree with what I'm driving at? I honestly have never heard of Ham (or if I've heard it, it didn't stick) and I'm pretty 'net-savvy. I think ham is a valid term, even if it's not as widely known as spam. Perhaps a compromise would be to change it to 'Mark as Ham (not Spam)'? Thoughts? These menu items have been removed for KDE 3.5 to avoid confusion of the users. You can still mark messages as ham/spam, but you can do it only in filters. (It makes sense only when filtering by spam headers or when passing messages to bayesian tools like sa-learn). So this report is not valid for the development version (and it can't be fixed for the 3.4 branch because of necessary string changes which aren't allowed). > These menu items have been removed for KDE 3.5 to avoid confusion of the users Excuse me - but are you mad? -> Bug 119790 You r e m o v e d them? To a v o i d confusion? We need them! And not via some filters but to set them manually. Alas going back to kmail 1.8 isn't the solution for kmail 1.8. does not work with KDE 3.5.1 :( Look, the status change to "spam" leads to the conclusion, KMail would somehow work like Thunderbird/Mozilla, where classifying messages as spam would train the spam tool. KMail can do this only via filters, that's the reason the stati are accessbile there. What's wrong with defining a filter, plug it with a nice icon into the toolbar an using that one? You can even define a hot-key for it. This isn't as flexible as other people demand (scriptability) but it's a beginning. OTOH, what do you do with spam message? I let them be filtered by a tool (sa) to a folder where I can quickly scan them and delete them. What's your workflow? Declaring developers as mad doesn't help at all. You'll have to convince them why your way is better than theirs. Then there is a good chance to get things changed or corrected. (As has been done with the "remove folder" action which is in the popup menu again.) SRY But not all people use the markers for filtering spam. There are people like me who use the ham marker to mark mails which were set to "to do" as "done". And the spam marker I also use(d to use) for marking mails manually, e.g. newsletters I want to cancel or where I want to see if a second mail of that spammer arrives or just a "forget about it baby I won't reply"... They are markers, just markers. Usually no action follows the setting of a marker. But those markers makes my mail life much easier. |