Largely, the requirements for all versions of GWAVA are the same.

System Requirements

• GWAVA 3.x or later must have NetWare 5.1, 6.0, or 6.5, plus the latest patches for NetWare.
• Disk space usage is 40 MB on the workstation, 38 MB on the server. (This excludes archive and log files, as well any spam/ham corpus built.) Most of this space is taken by the compiled.pcr file, which is optional (but greatly decreases the load time of the anti-spam engine)
• Memory usage on the server is about 8 MB without the anti-spam engine, and 38 MB with the anti-spam engine active
• A third-party anti-virus scanner product installed on the server
• GWAVA must be installed on the same server as your Message Transfer Agent (MTA).
• The GroupWise MTA must be version 5.5.2 or greater (06/99 date stamp). 5.5 Enhancement Pack, GroupWise 6.x and 7.x are all supported.
• The GroupWise MTA must be local to its domain.
• TCP/IP must be installed and configured on the servers running GWAVA even if the MTA is using UNC links to domains
• Long filename support must be enabled on the server with the GWAVA directories.
• /Attachmsg must be in the GWIA.CFG. It is by default.

• GroupWise 5.5 (non-EP) - SP5
• GroupWise 5.5 (EP) - SP5
• GroupWise 6.0 - SP 4
• GroupWise 6.5 - SP2

1. Internet Addressing should be enabled. This is set in the Internet Addressing options under GroupWise System Operations in NWADMIN or ConsoleOne. If this is not enabled, GWAVA may not be able to send notification messages to the system administrator (or to other notification recipients).
2. Your GWIA or SMTP server should be configured to allow relaying of mail messages from the GWAVA server. If relaying is disabled, you can make an exception for GWAVA. Alternatively, GWAVA 2.1 and above support SMTP AUTH, which allows authenticated relaying with GroupWise 6.0 and above.
3. Set GWAVA subdirectories, as well as all the GWVSCAN directories to Immediate Purge of Deleted Files (a general Novell recommendation for any GroupWise server). This will prevent your GWAVA server from becoming too busy with old files in temporary directories. If you experience an issue with NGW-VSCAN-CONTROLLER errors when unloading or restarting the MTA, this is the issue.
4. Novell has recently identified a bug in a program file that is essential to GWAVA's functionality called GWMTAVS.NLM. Novell has updated the file; however, you must also apply the GroupWise 5.5 Service Pack FTF in order to take advantage of the updated NLM for GWAVA. GroupWise 6 and above do not require this procedure; the fix is already built in.
   
   Here is the GWMTAVS.NLM procedure:
   
   1. Unload the GroupWise agents (POA, MTA)
   2. Rename SYS:SYSTEM\GWMTAVS.NLM
   3. Download and install the following GroupWise 5.5 Agent FTF from Novell at: http://support.novell.com/servlet/tidfinder/2964030
   4. Download and install the Updated GWMTAVS.NLM from Novell at: http://support.novell.com/servlet/tidfinder/2963978
   5. Edit the MTA startup file for the domain and add the following switch indicating the TCP port on which you would like to have the MTA listen for communication from GWMTAVS. At the bottom of the startup file after the other vs switches, add /vsport=7108.
   6. Re-load the GroupWise agents
   7. NOTE: The Agent FTF (in step 3), for Support Pack 3 or later is required to be able to configure the MTA to work with the new virus scan NLM.