Thanks Jani.  I thought I had seen it somewhere but just couldn't find it
back.  Turns out I had deleted it from my config file and I couldn't find
it on DSpam's web pages.

Anyway, on to my primary question:  Why does DSpam keep storing signatures
while I have it very much configured to train on error?


Auke

> TOE = Train On Error
> TUM = Train Until Mature
> TEFT = "Train Every Fucking Time"
>
> Copy paste from conf:
>
> # Training Mode: The default training mode to use for all operations, when
> # one has not been specified on the commandline or in the user's
> preferences.
> # Acceptable values are:
> #     toe     Train on Error (Only)
> #     teft    Train Everything (Trains on every message)
> #     tum     Train Until Mature (Train only tokens without enough data)
> #     notrain Do not train or store signatures (large ISP systems,
> post-train)
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On
>> Behalf Of Auke Jilderda
>> Sent: Monday, November 05, 2007 10:28 PM
>> To: [email protected]
>> Subject: [dspam-users] Setting training mode fails
>>
>> Hi,
>>
>> I have been using DSpam for a year or so and am very happy to
>> see it has restored sanity to my mail boxes.
>>
>> Recently though, I noticed its run-time data has grown to
>> huge amounts with some users' <user>.sig directory at over 1
>> GB at the moment.  It looks like DSpam continues to train on
>> every incoming message even though (I think) I configured it
>> to train on errors only.  (Can anybody tell me what the
>> various training modes stand for?  I reckon TOE means Train
>> On Error.  What does TUM and TEFT exactly mean?)
>>
>> I run DSpam 3.6.8 on Debian 4.0.  I have set "TrainingMode
>> teft" and "AllowOverride trainingMode" in
>> /etc/dspam/dspam.conf.  In addition, /etc/dspam/default.prefs
>> contains "trainingMode=TOE" (after having set this in the
>> admin section in the web interface).  Finally, the users
>> involved here have their personal preferences set to train
>> only when the filter makes a mistake.  Despite this
>> configuration, DSpam continues to store a .sig for each new
>> message.  Any ideas why?
>>
>> Thanks,
>>
>>
>> Auke
>>
>>
>
>


Reply via email to