On Wednesday 16 June 2004 17:53, Young, Darren might have typed:

> So... What I need is a web front end either works, or could be made to
> work, with preference files there so list administrators are able to
> maintain SA prefs for their own mailing lists.
>
> Perhaps I should consider storing prefs in a database instead and use
> whatever interface is out there for that type of installation?

I store stuff in MySQL, and have edited Conf.pm to allow me to stick stuff 
beyond required_hits etc in it.  Wrote a quick and dirty bit of php to allow 
the virtual users (imap, but processed as virtual via spamc) to edit the DB 
settings.  It is, however, very quick and dirty, as it only supports 
required_hits and whitelist_from :)

> Next, is it possible to have SA add something to the subject line after
> a certain threshold of spam detection has been hit? As in if the score
> is 100 out of 10 rewire the subject line to say [POSSIBLE SPAM] or
> something?

Like this? (man Mail::SpamAssassin::Conf)

rewrite_subject { 0 | 1 }        (default: 0)
           By default, the subject lines of suspected spam will not be tagged.
           This can be enabled here.
subject_tag STRING ...        (default: *****SPAM*****)
           Text added to the "Subject:" line of mails that are considered
           spam, if "rewrite_subject" is 1. Tags can be used here as with the
           add_header option. If report_safe is not used (see below), you may
           only use the _HITS_ and _REQD_ tags, or SpamAssassin will not be
           able to remove this markup from your message.

Reply via email to