DCC has been rolled into our SpamAssassin portfolio to combat the ever-growing problem of spam. DCC is designed to catch similar messages sent through everyone that participates in DCC by comparing the hashed message signature with the master database. Duplicate e-mails trigger the scoring mechanism and duplicates are what you always see with spam… unless you really know someone named “Millard Hurst” that solicites debt manage solutions via gobbledegook URLs on Live.com. After preliminary testing, DCC enhanced spam accuracy by approximately 55% compared to without. Enhanced accuracy means better scoring and hopefully fewer spams in your inbox.
Thanks to customer feedback through a ticket, Razor logging has been disabled and removed. We were accidentally logging Razor2 message status reports, which are useless unless you’re a developer debugging Razor2 problems. Depending upon e-mail volume this translates into a 10 KB – 20 MB decrease in disk usage per user.
Is there anything we have to do to regain whatever space the logs took?
No, the logs were pruned yesterday.
Cool, thanks.