Last Wednesday I upgraded a GWAVA 3.72 installation on a Netware 6.5 SP7 Groupwise 7.0.2 server to GWAVA version 4.0. The upgrade seemed to go just fine, but users were unable to send or receive Internet email, even after rebooting the server.
The GWAVA installation guide said to ensure the /smtphome switch in the sys:\system\gwia.cfg file reflected the correct path to the GWIA third directory. My path was set correctly in the following format:
/smtphome-\\ServerName\VolumeName\domaindirectory\wpgate\gwia\3rd
where servername is the name of the Groupwise server running the GWIA, VolumeName is the volume the gwia software is loaded on, and domaindirectory is the directory the Groupwise Domain is located in.
I removed the \\ServerName\ portion of the path and added a colon after the volume name which changed my smtphome path to:
/smtphome-VolumeName:\DomainDirectory\wpgate\gwia\3rd
and restarted my Groupwise server. Mail was then able to be sent and received from the Internet, and GWAVA was functioning properly.
Note that in Groupwise 7, the gwia.cfg overrides gwia object settings configured in ConsoleOne. Also, your gwia.cfg file may be located in a directory other than it’s default sys:\system. You can verify the path to the corerct gwia.cfg file by viewing the contents of your sys:\system\gwia.ncf file.
{ 3 comments… read them below or add one }
I can see your problem. It’s cause your using GWAVA. If you can get that out of there you should be great!
Too funny, Joe -
According to your IP Address of 64.254.233.111, you’re from Messaging Architects! Want to get me a deal on GWGuardian for my client so they can get GWAVA out of there?
- Julie
Too funny, Joe-
A MA guy trolling the internets looking for places to bash GWAVA.
Then you use the incorrect form of “you’re.”
Very impressive.