Hello,

  I don't think the idea will work because IMAP doesn't have a "move"
command.  To move a message, it is first copied from one folder to
another (via APPEND, I believe), then a second command is issued to
delete the original message.  The IMAP server could try to second-guess
that the client was "moving" a message, but it won't be right 100% of
the time (eg. I've copied a message to another folder, planning on
replying to the original one in my INBOX or something, then changed my
mind and deleted the original .. you probably wouldn't have that
scenario with your spam folder setup, but reguardless, it's same
sequence of events, but I didn't intent to conceptually "move" the
message out of my INBOX).

  Aside from that, can't you just use a database trigger to do what you
want today?  Eg. something along the lines of an insert trigger on the
dbmail_messages table .. if the message resolves to the same
message_blks (or physmessageblks?) as a message in the same user's Spam
folder, you fire off a PL/Perl or PL/Python procedure to train dspam (as
ham in this case).  Or can you not call system() (and whatever the
python equivalent is) from there?

Jn


On Thu, 2006-02-02 at 13:51 +0200, Aleksander wrote:
> Magnus Sundberg wrote:
> 
> > How do you know that the content of the deleted mail was spam? 
> 
> Sorry if I didn't express myself good enough, I'll try again:
> 
> Spam is delivered to the user's SPAM folder. Good mail is delivered to 
> the users INBOX. That's how it works.
> 
> Now dspam can make a mistake, especially in the beginning of the 
> training. There two cases where dspam can be wrong:
> 1) either it thinks a mail is good, whereas it was actually spam or
> 2) it thinks a mail is spam, but it's actually good.
> 
> The first case is basic training, telling dspam what is spam. The second 
> one is correcting it's mistakes.
> 
> 1) If dspam missed a spam mail and delivered it to the default INBOX 
> folder, the user moves the spam mail to the SPAM folder. Trigger goes 
> off and dspam relearns that this mail was actually spam.
> 
> 2) If dspam got a false positive and delivered a good mail to the SPAM 
> folder, the user moves the false positive from the SPAM folder to 
> wherever he wants it (INBOX, My_documents, Family, whatever custom 
> folder). Trigger goes off and dspam relearns that this mail is actually 
> a good one.
> 
> The user moves something _to_ and _from_ the SPAM folder only in these 
> two cases. Deleting is still deleting, we don't care about that. Only 
> moving from and to the SPAM folder matters.
> 
> I hope I cleared that up now,
>                 Alex
> _______________________________________________
> Dbmail mailing list
> [email protected]
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
-- 
Jesse Norell - [EMAIL PROTECTED]
Kentec Communications, Inc.

Reply via email to