> In my opinion, dspam should store everything in the database, rather > than some things in the database, and some things (quarantine,logs) in > files. It would make everything dspam (again, my opinion) easier to > replicate, manage, backup, and scale. > Storing human created white list entries would then rather need to be created in clear text (currently the automatic white list is implemented with tokenized entries). Not because DSPAM needs it in that way but because managing such lists would be done by humans and they can not handle the tokanized entries. Such lists could grow big. Would that be a problem?
One other issue needs to be looked at as well: DSPAM does not only have databases as backend. Some classifier/tokenizers use other formats then a DBMS. For example Markovian uses CSS files. There you can not implement white listing inside the CSS file without changing the format of the container. > -Troy > // Steve -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer !DSPAM:1011,486dd4d0150921675458559!
