jdow wrote:
I absolutely do not want to report automatically - in the sense that
I am adamant that I want human intervention before reporting.
Conversely - given the task of establishing a remote shell; finding
the correct email in maildir - and verifying it is indeed the mail I
determined was a spam in my email client - followed by manually
reporting it individually to each service... I'm inclined not to
bother. If, for example I had an IMAP folder into which I drop spam
that my mail server should report on my behalf -then reporting would
become far less of a chore.
Simple matter of coding. That is how I handle ham and spam training. I
simply
dunk it into ham and spam folders and let a cron job run sa-learn over
the
two folders. In this case you'd probably have to code up something
that takes
the folder apart properly, forwards the mail appropriately, then
tosses it.
I haven't done such a thing. But there are perl tools for reading
messages
via IMAP that could be used as the core of a new tool.
Hmmm - given that this seems such an obvious thing to want, and because
I'm quite laz^H^H^Hbusy these days, I'd hoped that there such thing
pre-existed. It strikes me that the best way to do this would be with a
daemon which monitors the IMAP folders for user-identified spam; salearn
and report it - then move it to the same folder as the automatically
identified spam. I realise that it wouldn't be a herculean effort to
implement this but I'm very reluctant to re-invent the wheel.
