Alex Tomlins wrote:
By database I was thinking whatever database backend dspam was using (hash, mysql, postgres etc.), not specifically a RDBMS. While implementing this it would make sense to put the user logs in there as well. The advantage to doing this is that all the data for dspam would be in one place as opposed to the current setup where some of it is in a database, and some of it is on the filesystem.
OK, I see your point. However, I'm not sure suited how well a hash database would be for storing quarantine emails - or, for that matter, even a RDBMS. Logging to a RDBMS would be helpful given how much processing we do of dspam log files, but in most cases that can be improved simply through better ways of handling the text files.
I'm strongly of the opinion that mbox is horrible, but which alternative is best I'm open to suggestion on.
-- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0845 45 89 555 Registered in England (0456 0902) at 13 Clarke Rd, Milton Keynes, MK1 1LG
