Dr.Web MailD interacts with CGP in the following way:
1.CGP receives an email message.
2.CGP checks the settings and after that, if required, sends the message for check to helper, functions of which are performed by drweb-cgp-receiver.
3.Upon receipt of the message, drweb-cgp-receiver searches for SecureHash header:
oif the header is found, drweb-cgp-receiver returns OK status and passes the message to CGP for further processing;
ootherwise, the message is passed for check to drweb-maild;
4.drweb-maild applies plug-ins to the message and the plug-ins can modify it (for example, add headers);
oif no virus is detected and the message was not changed, OK status is returned to CGP;
oif during processing the message was changed, DISCARD status is returned to CGP and further message processing is performed by drweb-maild, as the helper protocol does not allow to return a modified message.
5.The message is passed to Sender and, after adding of SecureHash header (if UseSecureHash = yes), the message is moved to the submit directory /var/CommuniGate/Submitted/ that is periodically checked by CGP.
|
Value of the SubmitDir parameter of the Dr.Web MailD configuration file must be equal to/var/CommuniGate/Submitted. Otherwise, messages checked by Dr.Web MailD cannot reach their recipients. |
6.After the /var/CommuniGate/Submitted/ directory is checked and the message is received, CGP goes to step 2:
oif the settings are correct, the message is not checked again;
oif the settings are inaccurate, the message is returned to CGP after check of the SecureHash header;
oif the settings are incorrect, an infinite checking loop can occur.