In order for the MTA to allow scanning of messages, there are some startup switches that must be present in the MTA startup file. Refer to the diagram above for the most likely location of this file. These swtiches normally appear at the bottom of the startup file. The switches that can be used are below.
/vsnamevalue-<Scanner ID XML> <–In build 118+ the scanner’s object ID is placed here instead of the gwavamta.xml file.
/vsthread-50 <– This is the number of threads the GWAVA will use to scan the files (default is 50). This can be modified if necessary.
Optional:/vsnoadm <– GroupWise 7.01 or greater is required. This switch will make it so that admin messages are not scanned. It is highly recommended that you use this setting if your GroupWise version supports it.
/vsnostatus <– GroupWise 7.03 or greater is required. This switch will make it so status messages are not scanned. It is highly recommended that you use this setting if your GroupWise version supports it.
With these switches in place at the bottom of the MTA startup file, the MTA will start and then realize that it needs to load GWMTAVS. GWMTAVS will then load VS automatically. Because these files are loaded by each other it is necessary for them to be in known locations. On NetWare GWMTA, GWMTAVS, and VS will all be in the same location. On Linux, GWMTA and GWMTAVS will be in the same location, with libgwvsmod.so (Linux equivalent of VS) in the library directory instead.
Note: The VS program is the only GWAVA program that doesn’t reside in the <GWAVA4>assetsbin direcotory.