Cool Solutions

Using a GWIA Relay through an Appliance


November 27, 2007 1:00 am






A Forum reader recently asked:

“I am trying to install an IronPort spam filter appliance between my GWIA 7.0, and the firewall. I get inbound email but cannot send outbound. I have no internal DNS, and I use my ISP’s DNS. It is set in the RESOLV file and has been working fine for years. My GWIA sends directly out the firewall using the DNS set in the RESOLV file. I only allow outbound port 25 traffic from the GWIA address.

I need to redirect the outbound port 25 traffic from my GWIA to the private side of the IronPort appliance, and let it send out thru the firewall to the Internet. Do I need to set the IP of the private side of the IronPort as the relay, using either a /mn switch in the GWIA.cfg file (or ConsoleOne, GWIA Properties, SMTP/MIME, Settings, Relay Host for Outbound messages)? I’m assuming then that the IronPort will look up the address using DNS (either my ISP’s or the core Internet), and send the mail out. Or do I need to do something more? “

And here’s the response from Tim Heywood …


The GWIA expects by default to send directly to the Internet; it does not have a relay in the way, so we need to tell it. As you are using GroupWise 7, we want to use ConsoleOne to insert the changes, as with GroupWise 7.0.1 the GWIA.CFG is no longer updated.

In the GWIA pages of ConsoleOne Properties, under the SMTP/MIME tab, you will see that there are two entries in the middle of the page where you can add hostnames – one for your GWIA and the second (lower) one for the relay. If you use an IP number, then the system is slightly quicker, as the hostname is not looked up each time.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.