On 2015-10-19 14:41, Ryan Coleman wrote:
Actually it makes absolute sense since I dump my spam into a folder to be
scanned as spam and anything that is still in my inbox, and read, is indeed ham.
I just have to re-investigate the ./new and ./cur folders to make sure they
will operate how I want. But if the email was delivered to my phone and it
moves (but not read) then it’s not an option.
I agree completely, this has proved to be quite useful here. In my case,
I scavenge the "Archive" folder of various accounts for my users who use
the Archive functionality of modern mail clients, in particular, mobile
clients and Thunderbird.
The concept of "Copy" doesn't exist on most mobile clients, and even
when it does, most users simply won't be bothered to copy non-spam with
any regularity, so at least for me, I've had far better success dealing
with messages on an automated basis than trying to influence user behaviour.
At this point I only implement this for specially selected users (and of
course, only with a user's consent, but since I approach users when
they've had a message get misclassified, they're usually happy to help).
For users who don't use an "Archived" folder, capturing
left-in-the-inbox, marked-as-read would be useful, but it hasn't been
worth the time to implement (yet). Unfortunately I don't use maildir, so
any tools I've created here aren't useful in the general case and are
really platform and environment specific.
Also, if a user later takes a message from their archive and places it
into the spam folder, I do have a tool that detects the duplicate and
purges it from the corpus. Currently I think I just delete the whole
message, although I did actually write code to detect which was newer
and trust the most recent decision made by the user, but ultimately I
decided it was safer to just delete it completely.
--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren
