
Vexira Antivirus for Mail servers
User Manual
Last modified: June 30, 2003

Contents
========

    End User License Agreement
    Introduction
        Intended Audience
        Vexira Antivirus overview

    vagated
        vagated usage

    vagatefwd
        vagatefwd usage

    Configuration File

        General parameters
            User
            Group
            Postmaster
            MyHostName
            SpoolDir
            VexiraDir
            TemporaryDir
            PidFile_vagated
            PidFile_vagatefwd
            MaxIncomingConnections
            SmtpTimeout
            MaxMessageSize
            MaxRecipientsPerMessage
            MinFreeBlocks
            MaxForwarders
            BlockSuspiciousMime
            ExposeAlerts
            ListenAddress
            ForwardTo
            RefuseEmptyMailFrom
            PollPeriod
            BounceMessageUser
	    AddPrecedenceHeader

        Scanning of files in an archive
            MaxRecursionDeepInArchive
            BlockSuspiciousArchive

            
        Handling Envelop Recipient Addresses
            AllowSourceRouting
            InEnvelopAddressesBangIs
            InEnvelopAddressesPercentIs
            AcceptLooseDomainName
            Examples
            Recommended settings

        Adding a notification in the body of transmitted emails
            AddStatusInBody
            ForwardAllEmailAsMIME

    Access Control Lists File

    Notification Templates


End User License Agreement
==========================

CENTRAL COMMAND, INC.
END USER SOFTWARE LICENSE AGREEMENT
For Vexira Antivirus and Vexira MailArmor

IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS DO NOT INSTALL
OR USE THE VEXIRA ANTIVIRUS OR VEXIRA MAILARMOR SOFTWARE
(referred to hereafter as the "Software"). BY CLICKING "YES", "I
ACCEPT", "I AGREE", "OK", "CONTINUE", "NEXT" OR BY INSTALLING OR
USING THE SOFTWARE IN ANY WAY, YOU ARE INDICATING YOUR COMPLETE
UNDERSTANDING AND ACCEPTANCE OF THE TERMS AND CONDITIONS OF THIS
END USER SOFTWARE LICENSE AGREEMENT (referred to hereafter as
the "License"). IF YOU DO NOT ACCEPT ALL OF THE TERMS AND
CONDITIONS OF THIS LICENSE, THEN CENTRAL COMMAND, INC. IS
UNWILLING TO LICENSE THE SOFTWARE TO YOU. YOU MAY, WITHIN THIRTY
(30) DAYS OF YOUR INITIAL PURCHASE OF A COPY OF THE SOFTWARE,
RETURN THE ENTIRE COPY OF THE SOFTWARE (INCLUDING ALL COMPUTER
MEDIA, PACKAGING AND DOCUMENTATION) WITH PROOF OF PURCHASE
EITHER TO CENTRAL COMMAND, INC. DIRECTLY AT ITS CUSTOMER SERVICE
DEPARTMENT OR TO THE RETAILER FROM WHICH YOU PURCHASED THE
SOFTWARE, FOR A FULL REFUND OF THE AMOUNT INDICATED BY YOUR
SALES RECEIPT OR PROOF OF PURCHASE FOR THE SOFTWARE.

IF YOU ARE INSTALLING THE SOFTWARE ON A COMPUTER THAT IS NOT
OWNED BY YOU, YOU ARE BOUND TO THE TERMS AND CONDITIONS OF THIS
LICENSE BOTH IN YOUR INDIVIDUAL CAPACITY AND AS AN AGENT OF THE
OWNER OF THE COMPUTER, AND YOUR ACTIONS WILL BIND THE OWNER OF
THE COMPUTER.  YOU REPRESENT AND WARRANT TO CENTRAL COMMAND,
INC. THAT YOU HAVE BOTH THE CAPACITY AND AUTHORITY TO ENTER INTO
THIS LICENSE ON YOUR OWN BEHALF AS WELL AS ON BEHALF OF THE
OWNER OF THE COMPUTER ON WHICH YOU ARE INSTALLING THE SOFTWARE.
FOR PURPOSES OF THIS LICENSE, THE "OWNER" OF A COMPUTER IS THE
INDIVIDUAL OR ENTITY THAT HAS LEGAL TITLE TO THE COMPUTER OR
THAT HAS THE POSSESSORY INTEREST IN THE COMPUTER IF IT IS LEASED
OR LOANED BY THE ACTUAL TITLE OWNER.

This End User License Agreement ("License") is a legal agreement
between you (either an individual, agent of the owner, or a
single entity end user) and Central Command, Inc. for use of the
Central Command, Inc. software product identified above (i.e.
Vexira Antivirus and Vexira MailArmor), which includes computer
software and may include associated media, printed materials,
and "online" or electronic documentation (collectively referred
to as the "Software"), all of which are protected by U. S.
copyright laws and international treaty protection. By
installing, copying, or otherwise using the Software, you agree
to be bound by the terms of this License. If you do not agree to
the terms of this License, do not install or use the Software.

The Software and the name "Vexira Antivirus" and "Vexira
MailArmor" is protected by copyright laws and international
copyright treaties, as well as other intellectual property laws
and treaties. The Software is licensed, not sold. If you agree
to be bound by all of the terms of this License, you will only
own the media on which the Software has been provided and not
the Software itself.

THIRTY DAY MONEY BACK GUARANTEE: If you are the original
licensee of this copy of the Software and are dissatisfied for
any reason with it within the first thirty (30) days after your
purchase or delivery date, you may return the complete product,
together with your original proof of purchase to Central
Command, Inc. or the retailer from which you purchased the
Software, for a refund of the amount indicated by your original
proof of purchase. If this purchase was completed using
electronic delivery you may be required to complete a Letter of
Destruction (referred to hereafter as an "LOD") and return it
within thirty (30) days after your purchase date to receive a
refund. Central Command, Inc. uses the postmark or fax date of
the completed and returned LOD to determine compliance. You can
receive a LOD by contacting your electronic retailer from which
you purchased the software or directly from Central Command,
Inc. via e-mail at service@centralcommand.com, postal mail at
P.O. Box 468, Medina, Ohio, 44256, or fax at 330-722-6517.  For
assistance you may also contact Central Command, Inc. by calling
330-723-2062 and requesting Customer Service.

GRANT OF LICENSE: Central Command, Inc. hereby grants you and
only you a non-exclusive license to use the Software subject to
and upon all of the terms and conditions set forth in this
License.

APPLICATION SOFTWARE: You may install and use only one copy of
the Software, and only on a single computer terminal. 

NETWORK USE: You may also store or install a copy of the
Software on a storage device, such as a network server, which is
used only to install or run the Software on your other computers
over an internal network; however, you must purchase and
dedicate a separate license for each separate computer terminal
on which the Software is installed or run from the storage
device. A license for the Software may not be shared or used
concurrently on different computers or computer terminals. You
are required to purchase a license pack or multi-use license if
you require multiple licenses for use on multiple computers or
computer terminals.

If you purchase a License Pack and you have acquired this
License for multiple licenses of the Software, you may make the
number of additional copies of the computer software portion of
the Software specified above as "Licensed copies." You are also
entitled to make a corresponding number of secondary copies for
use on a single home computer as specified above in the section
entitled "Application Software".

TERM OF LICENSE: The License granted hereunder shall commence on
the date that you install, copy or otherwise first use the
Software. You may terminate this License at any time.  This
License shall terminate automatically (and you shall have no
right to use the Software) upon your breach of any term of this
License. Upon termination, you must destroy the Software and all
copies, if any, you made pursuant to this License.

UPGRADES: If the Software is labeled as an upgrade, you must be
properly licensed to use a product identified by Central
Command, Inc. as being eligible for the upgrade in order to use
the Software. A copy of the Software labeled as an upgrade
replaces and/or supplements the product that formed the basis
for your eligibility for the upgrade. You may use the resulting
upgraded product only in accordance with the terms of this
License. If the Software is an upgrade of a component of a
package of software programs that you licensed as a single
product, the Software may be used and transferred only as part
of that single product package and may not be separated for use
on more than one computer.

COPYRIGHT: All right, title and interest in and to the Software
and the name "Vexira Antivirus" and "Vexira MailArmor" and all
copyright rights in and to the Software (including but not
limited to any images, photographs, animations, video, audio,
music, text, and "applets" incorporated into the Software), the
accompanying printed materials, and any copies of the Software
are owned by Central Command, Inc. or its suppliers. The
Software is protected by copyright laws and international treaty
provisions. Therefore, you must treat the Software and the term
"Vexira Antivirus" and "Vexira MailArmor" like any other
copyrighted material except that you may install the Software on
a single computer provided you keep the original solely for
backup or archival purposes. You may not copy the printed
materials accompanying the Software. You may not use the name
"Vexira Antivirus" and "Vexira MailArmor" or any similar name
except when referring to the Software. You must produce and
include all copyright notices in their original form for all
copies created irrespective of the media or form in which the
Software exists. You may not sub-license, rent, sell, or lease
the Software. You may not reverse engineer, recompile,
disassemble, create derivative works, modify, translate, or make
any attempt to discover the source code for the Software or any
part thereof. Except as expressly permitted by applicable law,
you may not remove from the Software, or alter, any of the
trademarks, trade names, logos, patent or copyright notices or
other proprietary rights notices or markings, or add any other
notices or markings to the Software.

LIMITED WARRANTY: Central Command, Inc. warrants that the media
on which the Software is distributed is free from defects for a
period of thirty (30) days from your date of receipt or purchase
date of the Software. Your sole remedy for a breach of this
warranty will be that Central Command, Inc. at its option, may
replace the defective media upon receipt of the damaged media,
or refund the money you paid for the Software. Central Command,
Inc. does not warrant that the Software will be uninterrupted or
error free or that the errors will be corrected. Central
Command, Inc. does not warrant that the Software will meet your
requirements. CENTRAL COMMAND, INC. HEREBY DISCLAIMS ALL OTHER
WARRANTIES FOR THE SOFTWARE, WHETHER EXPRESSED OR IMPLIED. THE
ABOVE WARRANTY IS EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES,
WHETHER EXPRESSED OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS.
YOU MAY HAVE OTHER RIGHTS, WHICH VARY FROM STATE TO STATE.

DISCLAIMER OF DAMAGES: Anyone using, testing, or evaluating the
Software bears all risk to the quality and performance of the
Software. In no event shall Central Command, Inc. be liable for
any damages of any kind, including, without limitation, direct,
indirect, exemplary, special, consequential or incidental
damages of any kind (including without limitation lost profits
or damage to other systems) arising out of the use, performance,
or delivery of the Software, even if Central Command, Inc. has
been advised of the existence or possibility of such damages.
SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF
LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. IN NO CASE SHALL
CENTRAL COMMAND, INC.'S LIABILITY EXCEED THE PURCHASE PRICE PAID
BY YOU FOR THE SOFTWARE. The disclaimers and limitations set
forth above will apply regardless of whether you accept or use,
evaluate, or test the Software.

IMPORTANT NOTICE TO USERS: THE SOFTWARE IS NOT FAULT-TOLERANT
AND IS NOT DESIGNED OR INTENDED FOR USE IN ANY HAZARDOUS
ENVIRONMENT REQUIRING FAIL-SAFE PERFORMANCE OR OPERATION. THIS
SOFTWARE IS NOT FOR USE IN THE OPERATION OF AIRCRAFT NAVIGATION,
NUCLEAR FACILITIES, OR COMMUNICATION SYSTEMS, WEAPONS SYSTEMS,
DIRECT OR INDIRECT LIFE-SUPPORT SYSTEMS, AIR TRAFFIC CONTROL, OR
ANY APPLICATION OR INSTALLATION WHERE FAILURE COULD RESULT IN
DEATH, SEVERE PHYSICAL INJURY OR PROPERTY DAMAGE.

GOVERNMENT RESTRICTED RIGHTS/RESTRICTED RIGHTS LEGEND: Use,
duplication, or disclosure by the Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the
Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 or subparagraphs (c)(1) and (2) of Commercial
Computer Software-Restricted Rights clause at 48 CFR 52.227-19,
as applicable. Contact Central Command, Inc., at P.O. Box 468,
Medina Ohio 44258-0468.

GENERAL: This License is deemed delivered in, and will be
governed by, the laws of the State of Ohio, in the United States
of America. This License may only be modified by a license
addendum, which must accompany this License or by a written
document which has been signed by both you and Central Command,
Inc. This License has been written in the English language only
and is not to be translated or interpreted in any other
language. Prices, costs and fees for use of the Software are
subject to change without notice to you. In the event of
invalidity of any provision of this License, the invalidity
shall not affect the validity of the remaining portions of this
License. Vexira, Vexira logo, Central Command, Central Command's
logo, EVRT, Emergency Virus Response Team, Without us, there's
no defense, are trademarks of Central Command, Inc. Microsoft,
Windows, Excel, Word, the Windows logo, Windows NT, Windows 2000
are registered trademarks of Microsoft Corporation. All other
trademarks are the property of their respective owners.


Introduction
============

    Intended Audience
    -----------------

        This document is intended  for the UNIX adminstrators who will
        install and configure Vexira Antivirus for Mail servers the
        antivirus email scanner.

        General  UNIX  administration skills and email server configuration
        knowledge are pre-requisites.

        Questions, comments and suggestions regarding this document or
        Vexira Antivirus solutions should be directed to:

        support@centralcommand.com  (Technical)
        sales@centralcommand.com  (Sales)

        For more  information on Vexira Antivirus please visit our web
        site http://www.centralcommand.com



    Vexira Antivirus for Mail servers overview
    ------------------------------------------

                           +-----------------------+
                           |       vagated         |
                           +-----------------------+
                                       |
                                       |
                                       |
                                       V
                             +-------------------+
                             |    Input Queue    |+
                             |                   ||
                             +-------------------+|
                              +-------------------+
                                       |
                                       V
                            +-----------------------+
                            |       vagatefwd       |
                            +-----------------------+
                                  |          |
                   +--------------+          +--------------+
                   |                                        |
                   V                                        V
         +-------------------+  force Delivery     +-------------------+
         | Error/Virus Queue |+ ------------------>|  Output Queue     |+
         |                   ||                    |                   ||
         +-------------------+|                    +-------------------+|
          +-------------------+                     +-------------------+
                                                            |
                                                            V
                                                  +-----------------------+
                                                  |      vagatefwd        |
                                                  +-----------------------+
                                                        |    |
                        +-------------------------------+    |
                        |                                    |
                        V                                    V
             +-----------------------+            +-----------------------+
             | other MTA sendmail    |            |         SMTP          |
             +-----------------------+            +-----------------------+


        Vexira Antivirus for Mail servers is composed of two processes:

            - vagated:       the smtpd receiver that stores incoming emails
                             into the input queue. (daemon)

            - vagatewfd:     virus scanning function and smtp forwarder and
                             sendmail invoker. (daemon)



vagated
=======

    vagated usage
    -------------

        vagated [-V|--version] [-i] [-p port] [-C config-file] [-D debug-level]


        -V or --version     Print the version number and exit.

        -C config-file      Specify an alternative configuration file,
                            instead        of        the       default
                            '/etc/vamailarmor.conf'.

        -A acl-file         Specify an alternative Access Control List
                            file,     instead    of     the    default
                            '/etc/vamailarmor.acl'.

        -i                  Runs  vagated  in  inetd mode  doing  SMTP
                            conversation  via  stdin  and stdout.  See
                            inetd(8)  for   information  on  how  this
                            works.

        -p port             Specify  the port  at  which vagated  will
                            listen for incoming SMTP sessions, instead
                            of the normal smpt (25) port.

        The following options are used while debugging:

        -D debug-level      Set the debug level (a small integer).

        -R remote.host      Specify the remote host domain name.
                            Imply -i.

        -r remote-ip-addr   Specify the remote host IP address (aaa.bbb.ccc.ddd).
                            Imply -i.

        -q port             Specify the remote host TCP port.

        When run interactively, the SMTP daemon directly converse with
        the terminal instead of working with a TCP port.



vagatefwd
=========

    vagatefwd usage
    ---------------

        vagatefwd [-V|--version] [-C config file] [-D debug level]"

        -V or --version     print the version number and exit.

        -C config-file      specify an alternative configuration file,
                            instead        of        the       default
                            '/etc/vamailarmor.conf'.

        -D debug-level      set the debug level (a small integer).



Configuration File
==================

    The configuration for Vexira Antivirus is  "/etc/vamailarmor.conf".
    It's  used  by  all  the  programs  of Vexira Antivirus (vagated,
    vagatefwd).

    Comments can be written anywhere in the configuration file (but in
    a quoted string), starting with a  '#' character, up to the end of
    the line.

    Spaces or tabulations can be placed anywhere.

    Parameter names  and parameter values may be quoted (') or
    double-quoted ("), and must be  quoted when they contain spaces or
    tabulations or a double-quote or a quote. The quotes don't affect
    the values, or the type (numeric or alphanumeric) of the value.

        ParamExampleNumber      1234
        ParamExampleNumber      "1234"
        ParamExampleSimple      a-name
        ParamExampleSpace       "One Space"
        ParamExampleQuote       "6'"
        ParamExampleDblQuote    '3"1/2'
        'QuotedParamExample'    quoted
        "DblQuotedParamExample" dbl-quoted

    Usually parameters are merely given with the parameter name and the
    parameter value on the same line. However some parameters have a
    more complex syntax, but all stand on a single line starting with
    the parameter name.

    The parameter names and and the parameter values that are keywords,
    are not case sensitive:

       BoolParamExample         Yes
       BoolParamExample         YEs
       BoolParamExample         yEs
       BOOLPARAMEXAMPLE         yes
       boolparamexample         YES

    are all the same.

    Boolean parameters values can be written as YES or NO, or as TRUE or
    FALSE.

    First are presented general parameters that apply to all the
    programs composing Vexira Antivius, then those specific to vagated,
    and lastly those specific to vagated.


    General parameters
    ------------------

        The parameters presented in this section are used by both
        vagated and vagatefwd.



        User
        ....

            This parameter allow the administrator to set the UNIX user
            under which Vexira Antivirus will run (the owner of Vexira
            Antivirus).

            This should NOT be root.

            The  parameter  must be  a  login  name  as found  in  the
            /etc/passwd file.


            Syntax:
              User    "string"

            Default value:
              User    uucp

        Group
        .....

            This parameter allow the administrator to set the UNIX group
            under which Vexira Antivirus will run.

            This should NOT be root.

            The parameter must be a group name as found in the
            /etc/group file.


            Syntax:
              Group    "string"

            Default value:
              Group    uucp




        Postmaster
        ..........

            This parameter specifies the email address of Postmaster.
            It's the address where notifications that an email contained
            a virus are sent (beside the sender and recipient of the
            potentially malicious email).


            Syntax:
              Postmaster    "string"

            Default value:
              Postmaster    postmaster.

            An example of value may be:
              Postmaster virusmaster@admins.department.example.com



        MyHostName
        ..........

            This parameter specifies the FQDN of the localhost.


            Syntax:
              MyHostName    "string"

            Default value:
              If not set in configuration  file, is  that obtained  by
              gethostname(2), or if this fails, "localhost".



        SpoolDir
        ........

            This parameter specifies the spool directory where Vexira
            Antivirus stores the messages it processes.


            Syntax:
              SpoolDir    "string"

            Default value:
              SpoolDir    /var/spool/vamailarmor



        VexiraDir
        ..........

            This parameter specifies the library directory of Vexira
            Antivirus, where the key file, the virus definition file and
            other critical data for Vexira Antivirus are stored.


            Syntax:
              VexiraDir    "string"

            Default value:
              VexiraDir    /usr/lib/Vexira



        TemporaryDir
        ............

            This parameter specifies the temporary directory name where
            emails will be extracted and scanned.


            Syntax:
              TemporaryDir    "string"

            Default value:
              TemporaryDir    /var/tmp



        PidFile_vagated
        ................

            This parameter specifies the location of the pid file of the
            SMTP daemon vagated.


            Syntax:
              PidFile_vagated    "string"

            Default value:
              PidFile_vagated    /var/run/vamailarmor_d.pid



        PidFile_vagatefwd
        .................

            This parameter specifies the location of the pid file of the
            forwarder daemon vagated.


            Syntax:
              PidFile_vagatefwd    "string"

            Default value:
              PidFile_vagatefwd    /var/run/vamailarmor_fwd.pid



        MaxIncomingConnections
        ......................

            This parameter specifies the number of simultanous
            connections.

            The number of simultanous connections from remote sites
            should be limited. A limit of 0 disables this feature.


            Syntax:
              MaxIncomingConnections    "integer"

            Default value:
              MaxIncomingConnections    0



        SmtpTimeout
        ...........

            This parameter specifies the number of seconds until a
            timeout occures in SMTP conversation.


            Syntax:
              SmtpTimeout    "integer"

            Default value:
              SmtpTimeout    300



        MaxMessageSize
        ..............

            This parameter specifies the maximum of message size in
            bytes.

            This value should be set to the same number used by your
            MTA.
            A limit of 0 disables this feature.


            Syntax:
              MaxMessageSize    "integer"

            Default value:
              MaxMessageSize    0



        MaxRecipientsPerMessage
        .......................

            This parameter specifies the maximum number of recipients.

            This limit should be limited to 100 as recommended in REC
            821.
            A limit of 0 disables this feature.


            Syntax:
              MaxRecipientsPerMessage    "integer"

            Default value:
              MaxRecipientsPerMessage    100



        MinFreeBlocks
        .............

            This parameter specifies the number of free blocks on file
            system.
            The incoming connection will not be accepted, if the number
            of free blocks reaches this limit. A limit of 0 disables
            this feature.


            Syntax:
              MinFreeBlocks    "integer"

            Default value:
              MinFreeBlocks    0



        MaxForwarders
        .............

            This parameter specifies the maximum number of forward
            processes of vagated.
            The number is dependend on the performance of mail system
            and quality of network connection. The default value should
            be increased, if the performance of the used mail system and
            the connection to the network is low.


            Syntax:
              MaxForwarders    "integer"

            Default value:
              MaxForwarders    10



        BlockSuspiciousMime
        ...................

            This parameter specifies if suspicious MIME emails will be
            blocked.
            The delivery of suspicious MIME emails will be stopped, when
            a MIME nesting level >20 or more than 100 attachments is
            reached.


            Syntax:
              BlockSuspiciousMime    YES | NO

            Default value:
              BlockSuspiciousMime    YES



        ExposeAlerts
        ............

            This parameter specifies if virus alerts will be sent
            outside your domain, if the sender of an email is a user
            local to your domain.


            Syntax:
              ExposeAlerts    YES | NO

            Default value:
              ExposeAlerts    YES



        ListenAddress
        .............

            This parameter specifies the interface and port the smtp
            daemon will listen on. The default interface 0.0.0.0 means
            all interfaces.


            Syntax:
              ListenAddress "string" port "integer"

            Default value:
              ListenAddress 0.0.0.0 port 25

            An example of value may be:
              ListenAdress 192.168.5.20 port 25



        ForwardTo
        .........

            This parameter specifies the type of email forwarding. There
            are two possibilities how to sent emails further. First is,
            emails could be send by piping it thru sendmail (this is
            default).
            Second is, to send emails further by SMTP.


            Syntax (by piping):
              ForwardTo string

            Syntax (by SMTP):
              ForwardTo   SMTP: "string" port "string"
               or
              ForwardTo   SMTP: "string" port "integer"

            Default value:
              ForwardTo    /usr/sbin/sendmail -oem -oi

            An example of Syntax when sending by SMTP may be:
              ForwardTo    SMTP: localhost port smtp-backdoor



        RefuseEmptyMailFrom
        ...................

            This parameter specifies if emails containing a blank sender
            address will be blocked.

            RFC 1123 explicitly says in section 5.2.9 that a blank
            sender address must be accepted.  If you don't accept a
            blank sender address, then you don't have an SMTP server. 
            Additionally, you will greatly annoy other postmasters,
            possibly to the point of being blocked yourself.


            Syntax:
              RefuseEmptyMailFrom    YES | NO

            Default value:
              RefuseEmptyMailFrom    NO



        PollPeriod
        ..........


            PollPeriod specifies the periodicity, in seconds, of the
            queue scanning done by vagatefwd.


            Syntax:
              PollPeriod    "integer"

            Default value:
              PollPeriod    30  



        BounceMessageUser
        .................


              User name of sender of error (bounce) messages if a mail
              couldn't be delivered via MTA (bounce messages).

              Syntax:
                BounceMessageUser    "string"

              Default value:
                BounceMessageUser    MAILER-DAEMON    
    



    Scanning of file in archives
    ----------------------------


         MaxRecursionDeepInArchive
         .........................

            This parameter specifies the maximum of recursion deep of
            scanning in archives. If MaxRecursionDeepInArchive is 0,
            recursive archives are going to be unpacked with an
            unlimited recursion deep.

            If MaxRecursionDeepInArchive is >0, recursive archives are
            going to be unpacked up to the adjusted recursion deep.


            Syntax:
              MaxRecursionDeepInArchive    "integer"

            Default value:
              MaxRecursionDeepInArchive    5



         BlockSuspiciousArchive
         ......................

             This parameter specifies if emails containing suspicious
             archives will be blocked when MaxRecursionDeepInArchive has
             reached.
             If BlockSuspiciousArchive is NO, don't stop delivery of
             emails containing archives with a suspicious recursion
             deep.
             If BlockSuspiciousArchive is YES, stop delivery of emails
             containing archives if MaxRecursionDeepInArchive has been
             reached.


             Syntax:
               BlockSuspiciousArchive    YES | NO

             Default value:
               BlockSuspiciousArchive    NO


    Handling Envelop Recipient Addresses
    ------------------------------------


        The parameters presented in this section are used by vagated
        only.

        Two orthogonal processings are at hand here:  source routing
        (which normaly is prohibed now ), and interpreting bangs and
        percents (which normaly should be refused, but can be allowed
        for interoperability with UUCP or strange gateways) [RFC0821,
        RFC0976, RFC1123].

        These processings are directed by the following configuration
        parameters:


        AllowSourceRouting             YES | NO
        InEnvelopAddressesBangIs       IGNORED | REFUSED | INTERPRETED
        InEnvelopAddressesPercentIs    IGNORED | REFUSED | INTERPRETED
        AcceptLooseDomainName          YES | NO



        AllowSourceRouting
        ..................


            When AllowSourceRouting is NO, if source routing is present
            in the given path, it's removed.
            When AllowSourceRouting is YES, then source routing is
            honored, and the messages is forwared to the first host
            specified in the route.


            Syntax:
              AllowSourceRouting    YES | NO

            Default value:
              AllowSourceRouting    NO.



        InEnvelopAddressesBangIs
        ........................

            This configuration parameter directs the interpretation of
            the bang character, "!", in the envelop recipient addresses.

            When InEnvelopAddressesBangIs is REFUSED, the presence of an
            unquoted "!" in the recipient envelop address implies that
            the message will be refused.

            When InEnvelopAddressesBangIs is IGNORED, any unquoted "!"
            will be processed as any other non-special character of the
            address.

            When InEnvelopAddressesBangIs is INTERPRETED, then the
            address is rewritten in RFC821 standard form. An address
            such as:

                hostA!hostB!hostC!user

            is rewritten as:

                @hostA,@hostB:user@hostC

            Then, if source routing is allowed, the message is
            transmited to hostA, otherwise it's directly sent to hostC.

            Thus, this rewritting allow us to discover the recipient
            host, in the case where all the UUCP gateways on the route
            would have interpreted the address the same way as us. (If
            that were not the case, then this parameters should be set
            to IGNORED).


            Syntax:
              InEnvelopAddressesBangIs    IGNORED | REFUSED | INTERPRETED

            Default:
              InEnvelopAddressesBangIs    REFUSED



        InEnvelopAddressesPercentIs
        ...........................

            This configuration parameter directs the interpretation of
            the percent character, "%", in the envelop recipient
            addresses.

            When InEnvelopAddressesPercentIs is REFUSED, the presence of
            an unquoted "%" in the recipient envelop address implies
            that the message will be refused.

            When InEnvelopAddressesPercentIs is IGNORED, any unquoted
            "%" will be processed as any other non-special character of
            the address.

            When InEnvelopAddressesPercentIs is INTERPRETED, then the
            address is rewritten in RFC821 standard form. An address
            such as:

                user%hostC%hostB@hostA

            is rewritten as:

                @hostA,@hostB:user@hostC

            Then, if source routing is allowed, the message is
            transmited to hostA, otherwise it's directly sent to hostC.

            Thus, this rewritting allow us to discover the recipient
            host, in the case where all the gateways on the route would
            have interpreted the address the same way as us. (If that
            were not the case, then this parameters should be set to
            IGNORED).


            Syntax:
            InEnvelopAddressesPercentIs    IGNORED | REFUSED | INTERPRETED

            Default:
            InEnvelopAddressesPercentIs    REFUSED


        AcceptLooseDomainName
        .....................


            The AcceptLooseDomainName parameter allow to process domain
            names even if they don't respect strictly domain name
            syntax, that is:  a domain name can contain only
            [-.0-9A-Za-z], each name being at most 63 characters not
            beginning nor ending with a '-', the last name not being
            digit-only and in total less than 256 characters.

            When AcceptLooseDomainName is NO, if the name of the domain
            selected for delivery (depending on source routing) does not
            strictly conform it the domain name syntax,then it's
            refused.

            When AcceptLooseDomainName is YES, then no check is done on
            the domain name, apart of interpreting the domain name
            syntax for numerical IP addresses.

            In any cases, then domain name can be either a true domain
            name (a sequence of names separated by dots), or else a
            numerical IP address with either one of these syntax:

                # <decimal-number>
                [ <small-numer> . <small-numer> . <small-numer> . <small-numer> ]

            Note that we won't accept mixing IP addresses with domain
            names as would be allowed by the syntax defined in RFC0821,
            since no semantics are defined for these forms.


            Syntax:
              AcceptLooseDomainName    YES | NO

            Default value:
              AcceptLooseDomainName    NO


        Examples
        ........

            The "!", "%" and "@" can be combined in an address.

            With the configuration paremeters set as:

                InEnvelopAddressesBangIs       INTERPRETED
                InEnvelopAddressesPercentIs    INTERPRETED

            PATH:       <host-b!host-c!user@host-a>
            FIRST-HOST: host-a
            LAST-HOST:  host-c
            LOCAL-PART: user
            RECIPIENT:  <user@host-c>
            ROUTE:      <@host-a,@host-b:user@host-c>


            PATH:       <user%host-c%host-b@host-a>
            FIRST-HOST: host-a
            LAST-HOST:  host-c
            LOCAL-PART: user
            RECIPIENT:  <user@host-c>
            ROUTE:      <@host-a,@host-b:user@host-c>


            PATH:       <@host-a:host-b!user%host-c>
            FIRST-HOST: host-a
            LAST-HOST:  host-c
            LOCAL-PART: user
            RECIPIENT:  <user@host-c>
            ROUTE:      <@host-a,@host-b:user@host-c>



        Recommended settings
        ....................

            The recommended settings of the parameters are:


            For a pure Internet (RFC0822) MTA:

                AllowSourceRouting             NO
                InEnvelopAddressesBangIs       IGNORED


            For an Internet -> UUCP gateway MTA:

                AllowSourceRouting             YES
                InEnvelopAddressesBangIs       INTERPRETED


            For a UUCP MTA (hypothetical case, given that vagated is a
            SMTP daemon ; this could occur if the UUCP rmail would
            inject the emails thru SMTP into vagated for virus
            checking):

                AllowSourceRouting             YES
                InEnvelopAddressesBangIs       INTERPRETED


            However, all depends on the processing done by the forward
            MTA.


    Adding a notification in the body of transmitted emails
    ------------------------------------------------------

        The parameters presented in this section are used by vagated
        only.

        The following configuration parameters allow the insertion of a
        paragraph stating the Vexira Antivirus status of the forwarded
        email:

            AddStatusInBody         YES | NO
            ForwardAllEmailAsMIME   YES | NO


        AddStatusInBody
        ...............


            When AddStatusInBody is NO, no not status notification is
            inserted in the body of the emails.

            When AddStatusInBody is YES:

            For plain rfc822 email (non MIME), just insert the
            notification paragraph in the beginning of the body.

            For MIME email, transmit the checked email as a new MIME
            multipart/mixed email, with a first text/plain section
            containing the status notification paragraph, and with a
            second message/rfc822 section containing the whole original
            message.  Most headers from the original are copied to the
            transmitted message.


            Syntax:
              AddStatusInBody    YES | NO

            Default value:
              AddStatusInBody    NO.



        ForwardAllEmailAsMIME
        .....................


            When ForwardAllEmailAsMIME is NO, incoming emails that are
            not MIME emails get out as they came, non-MIME.

            When ForwardAllEmailAsMIME is YES:

            The  behaviour does  not  change for  MIME emails.

            However, plain rfc822 emails are encapsulated into a MIME
            message/rfc822 section of a multipart/mixed email that will
            inherit all the headers of the user email.  If
            AddStatusInBody is YES too, then our text is added into a
            text/plain entity inserted before the message/rfc822 entity.


            Syntax:
              ForwardAllEmailAsMIME    YES | NO

            Default value:
              ForwardAllEmailAsMIME    NO


	AddPrecedenceHeader
	...................


	    When AddPrecedenceHeader is YES, every notice mail
	    contains a headerline "Precedence: junk".
	    This causes some programs (e.g. vacation) that respond automatically to
	    incoming mails, to NOT respond to this mail.
	    

	    Syntax:
	      AddPrecedenceHeader               YES | NO

	    Default value:
	      AddPrecedenceHeader               NO


Access Control Lists File
=========================


    The file '/etc/vamailarmor.acl' defines which hosts are considered
    local and for which we are allowed to relay emails.

    Comments can be written anywhere in the ACL file (but in a quoted
    string), starting with a '#' character, up to the end of the line.

    Spaces or tabulations can be placed anywhere.

    Parameter names and parameter values may be quoted (') or
    double-quoted ("), and must be quoted when they contain spaces or
    tabulations or a double-quote or a quote. The quotes don't affect
    the values, or the type (numeric or alphanumeric) of the value.

    The parameter names and the parameter values that are domain names,
    are not case sensitive.


    ACL lines may add either to the list of local host ('local:'
    parameter name) or to the list of hosts for which relaying is
    allowed ('relay:' parameter name).

    In either case, the parameter name can be followed of any number of
    space separated domain names or IP addresses/masks.

    The IP addresses can be written either as a network address prefix,
    or with a '/' and a number of bits to match.

         192.168.0.0/16
         192.168.0.0
         192.168.0.
         192.168.0
         192.168.
         192.168

    are all equivalent. When the '/' and number of bits is not present,
    the mask is either 8, 16, 24 bits if the 24, 16, or 8 low order bits
    are null, or else 32 bits for an exact IP address match.


    Example:
        +----------------------+
        | /etc/vamailarmor.conf|
        +----------------------+------------------------------+
        |# Access lists for Vexira Antivirus                  |
        |                                                     |
        |# These hosts and/or domains are local.              |
        |local: localhost 127.0.0.1                           |
        |local: centralcommand.com                            |
        |                                                     |
        |# These hosts and networks are allowed to relay.     |
        |relay: 127.0.0.1/8                                   |
        |relay: 192.168.0.0/16                                |
        +-----------------------------------------------------+

    The following configuration file options refine the meaning of the
    domain name and IP addresses given in the ACL file:

         MatchMailExchangeForLocal
         MatchMailExchangeForRelay
         AllowDnsLookups



Notification Templates
======================

    If you are running a commercial you have the possibility to define
    your own message in virus and pathological notification mails.

    Create the following directory:
    /usr/lib/Vexira/templates
    
    Copy the sample template files from archive directory templates to 
    /usr/lib/Vexira/templates

    Change the ownership to uucp for user and group:
    chown -R uucp:uucp /usr/lib/Vexira/templates/

    Change to the directory /usr/lib/Vexira/templates. Now there exist
    the following files:

     patho-administrator
     patho-recipient
     patho-sender
     virus-administrator
     virus-recipient
     virus-sender

    Edit all files and insert your own messages. Pay attention on the 
    format of these files. The first line is the subject of an mail. 
    After this line there must be follow an empty line (new line), 
    then the body.
    The virus-* and patho-* files may contain the following keywords,
    that will be replaced by the corresponding text:
 
       LICENSE      Centered license text (one or two lines).
 
       SENDER       The email address of the sender of the email.
 
       VIRUSES      A list of viruses found in the bad email, one per line,
                    the prefix and postfix substring being repeated on each
                    line.
 
       REASON       The cause explaining why the email could not be scanned.
                    (one short sentence).
 
       ADVICE       A suggestion as to what the sender can do to remediate
                    the problem (see REASON). (About one line long).
 
       QUEUEID      The ID of the message in the vamailarmor queue.

       SUBJECT      The Subject of the message.

    For example see the file virus-recipient:


Subject: Vexira Antivirus found a virus in mail from you!

*********************************************************************
                       Vexira Antivirus Alert
*********************************************************************
                              LICENSE
*********************************************************************

Vexira Antivirus found these viruses in a messsage from you!

     VIRUSES

The email was not delivered.

Your computer may be infected with a virus! Please visit
Central Command at http://www.centralcommand.com and obtain a copy
of Vexira Antivirus now.

---
Vexira Antivirus for Linux, OpenBSD, FreeBSD
Virus Protection for the Real World. TM
Central Command http://www.centralcommand.com

