The analysis of messages received from Dr.Web MailD (or any other external application) for the traits of spam is performed using the anti-spam library and the Dr.Web Anti-Spam component. The analysis of messages is performed in a standalone mode, without requests to external sources of information on spam. This solution also provides a high rate of message processing and constant improvement of the message analysis quality due to the dynamic update of the database of rules for spam classification of messages (update is performed automatically via Dr.Web Updater).
|
Users are provided with the opportunity to create their own component (an external application) using Dr.Web Anti-Spam for anti-spam scans of email messages. For this, Dr.Web Anti-Spam provides a special API based on Google Protobuf. To obtain Dr.Web Anti-Spam API guide and examples of a client application using Dr.Web Anti-Spam, contact Doctor Web partner care department (https://partners.drweb.com/).
Dr.Web for UNIX Mail Servers is not distributed with the Dr.Web Anti-Spam component on АRM64, E2K, and IBM POWER (ppc64el) architectures.
If any email messages are falsely detected by the Dr.Web Anti-Spam component, we recommend you to forward them to special addresses for analysis and improvement of spam filter quality. To do that, save each message to a separate .eml file. Attach the saved files to an email message and forward it to the corresponding service address: •nonspam@drweb.com—if it contains email files erroneously considered spam; •spam@drweb.com—if it contains spam email files failed to be recognized as spam. |
