User manual KASPERSKY ANTI-VIRUS FOR WINDOWS WORKSTATION

[. . . ] Distribution kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help desk for registered users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adopted conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TYPICAL DEPLOYMENT SCENARIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] Example: </FOR> closing bracket of the end tag for a construct without a body. Example: <DEF __NAME __= "NAME_1"/> escape symbol. Instructs the parser to treat the following special character as a plain one. Example: \%VIRUSNAME\% equal sign: a coincidence in mask or value. Example: <FOR FILTERNAME == "KAVFilter1"> Example: <FOR FILTERNAME == "KAVFilter*"> unequal sign: a non-coincidence in mask or value. Example: <FOR FILTERNAME != "KAVFilter1"> </ /> \ == != 54 Kaspersky Anti-Virus® for Sendmail with Milter API Example: <FOR FILTERNAME != "KAVFilter*"> * Unlimited length of all possible values. It is used only inside tags in comparison with templates. Example: <FOR FILTERNAME == "KAV*"> All possible one-character values. It is used only inside tags in comparison with templates. Example: <FOR FILTERNAME == "KAVFilter?"> Comment; the parser ignores all characters after `#' till the end of line. ? # Reserved keywords FOR Iteration construct Example: <FOR FILTERNAME = "KAVFilter1"> definition. DEF Variable definition (statement without an end tag). Example: <DEF __NAME__= "NAME_1"/> Predefined macros %CRLF% %TAB% Line feed macro (CR+LF) Tab macro The processing is performed within a global section (no statement is needed) or within a condition construct: <FOR KAV_LANGUAGE == "5. 0"> . . . %ACTION% ­ Action applied to the object based on its status. 56 Kaspersky Anti-Virus® for Sendmail with Milter API %INFO% ­ Information related to the following actions performed: · · · List of detected viruses (malicious software) ­ for infected objects. Error code description ­ for objects that generated a scan error. MIME type or attachment name ­ for filtered objects. The macros must be specified in the text of notification templates. 6. 12. Reporting options Kaspersky Anti-Virus performance results are logged in the application report. You can store results either in the system log or a separate file (defined by the LogFacility parameter of the [kavmilter. log] section). The report records: Events related to application functionality ­ All events that occur during application performance, for example, results of message scans. Events not related to the application functionality ­ All events that are not directly caused by application performance but provide important information. This information can be the size of the backup storage, program errors, license policy events, etc. The administrator can decide what information will be included into the report and determine the detail level of the selected data for each. The types of data and their detail levels are discussed below. The following information can be logged in the report: config ­ Records about the application configuration. [. . . ] This licence authorizes you to make or download one copy of the Documentation for each additional copy authorized by the volume licence, provided that each such copy contains all of the Document's proprietary notices. This Agreement is effective for one (1) year unless and until earlier terminated as set forth herein. This Agreement will terminate automatically if you fail to comply with any of the conditions, limitations or other requirements described herein. Upon any termination or expiration of this Agreement, you must immediately destroy all copies of the Software and the Documentation. [. . . ]