The analysis of messages received from Dr.Web MailD (or any other external application) for signs of spam is performed using the anti-spam library and the Dr.Web Anti-Spam component. The analysis of the messages is performed in standalone mode without requests to external sources of information on spam. This solution provides a high rate of message processing and constant improvement of message analysis owing to the dynamic update of the database of rules for spam classification of messages (the update is performed automatically via Dr.Web Updater).
|
You can create your own component (an external application) using Dr.Web Anti-Spam for scanning email messages for spam. For this, Dr.Web Anti-Spam provides a special API based on Google Protobuf. To obtain the Dr.Web Anti-Spam API guide and examples of client application code using Dr.Web Anti-Spam, contact the partner relations department of the Doctor Web company (https://partners.drweb.com/).
Dr.Web Mail Security Suite 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 that you forward them to special addresses for analysis and improvement of spam filter quality. To do that, save each message as 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 classified as spam; •spam@drweb.com—if it contains spam email files failed to be classified as spam. |
