From SpamAssassin to more generic Spam preferences

interfasys

Verified User
Joined
Oct 31, 2003
Messages
1,821
Location
Switzerland
DA comes with a nice SpamAssassin preferences management tool, but wouldn't it be great if we could manage our own antispam solution from DA?

What we have now:
-We can customize the exim filter files so that they detect different headers than the one from SA and store the spam in any folders we want
-We can rename the links in the skins

Steps to take to have a more universal solution:
-Rename the links in the skin to a more generic Spam prefs
-Allow us to define where the prefs should be stored.
-Allow us to define which tokens we need to populate from the interface
-Give us a spam_prefs_post.sh
-more?

That way we could create a DSpam page and have it nicely integrated within DA if we want to :D
 
Olivier,

If you comment out the SpamAssassin "stuff" from exim.conf (make it look like the distribution version, DA won't show the SpamAssassin links.

And you can write and install a plugin which will display any links you want.

Then you just write your own backend.

Jeff
 
OK, but I figured since we already have all the mecanisms in place, why rewrite everything. It's just a mater of writing the prefs in the right file and using the right spam folders.
Tweaking some config files is much more easier than writing a plugin ;)
 
Here is an example of what I meant in my original post:
Let's call all the files and links antispam instead of spamassassin. Things like /home/user/.spamassassin/user_prefs should be changed to /home/user/.antispam/user_prefs.
user_prefs could either have different sections in it, one for each engine or a way of identifying which engine is in use. so that the proper preferences could be shown in DA, if needed.
The concept could be taken further by converting the current spamassassin skin pages into a spamAssassin plugin. That way, people who want to use something different could just copy and change the plugin without having to remove pages and links from the skin first.
 
What we've got here is a feature request. Let's see how many others are interested.

Jeff
 
What we've got here is a feature request. Let's see how many others are interested.

Jeff
 
Back
Top