[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 72010] Context menu plugin system like KonqPopupMenuPlugin,
From:       Ingo "Klöcker" <kloecker () kde ! org>
Date:       2004-01-10 16:20:17
Message-ID: 20040110162017.5160.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=72010      




------- Additional Comments From kloecker@kde.org  2004-01-10 17:20 -------
* Giving access to more advanced features of bogofilter, like *un*-registering as \
spam or non-spam

That's exactly what ad hoc filters in KDE 3.2 can be used for. Furthermore that's \
exactly what Andreas' Spam Filter Setup Wizard sets up for the user, i.e. menu \
options (and later also toolbar buttons) for teaching spamassassin or bogofilter \
about spam/non-spam.  
 * Viewing the details of why a mail was marked as it was

View->View Source?
 
 * Configuring Bogofilter (this would better be put in the Tools menu than a context \
menu)

As you pointed out yourself this doesn't belong into a context menu. It doesn't even \
belong into KMail. Anyway, the solution for this problem is trivial: Write a KControl \
module for configuring Bogofilter and then show this kcm in KMail's configuration \
dialog. Till is currently converting the complete KMail configuration dialog to kcms \
so adding more kcms will be a no-brainer.

 * Adding any kind of mail processing other than spam filtering, or even using two \
different spam filters

That's exactly what ad hoc filters with a pipe through action can be used for. And of \
course the scripts the messages are piped through can be written in Python or Ruby.


I don't see why we would need plugins for anything of the above. But I won't close \
this bug report. I will just mark it as IWONTFIXIT.


[prev in list] [next in list] [prev in thread] [next in thread]