RE: [Assp-user] Set-up Problems Mercury and GroupWise

[Ged W. <gw...@gh...>]

Are you using ETRN or do you have a dedicated internet connection?  

In your old configuration did groupwise forward all outgoing mail to a relay
host?  If not then I would think you could remove the relay host from
Mercury and just let it use DNS to deliver outgoing mail.  Maybe I am
missing something here but I think that should work, as long as Mercury
knows that the paratransit.net domain is local and forwards local mail to
192.168.1.9 you shouldn't have a problem.

It is my understanding that you can make it work with GWIA if you are
running Groupwise on a NT 4.0 or higher windows box, but I would not
recommend it.  Having your SMTP server and ASSP on a different server is the
way to go IMHO, and when Mercury is used in conjunction with F-prot for DOS
it adds a nice secondary level of Anti-virus protection.

Ged


-----Original Message-----
From: David Churchill [mailto:dc...@pa...]
Sent: Friday, January 30, 2004 9:12 AM
To: ass...@li...
Subject: [Assp-user] Set-up Problems Mercury and GroupWise


I'm have some difficulty getting ASSP set up properly with Mercury/32
and GroupWise.

Everything is behind my Firewall/NAT box with my MX record pointing to
its external (public) interface.

ASSP is on a separate box (private IP 192.168.1.20) with Mercury/32.

GroupWise is on yet another box (private IP 192.168.1.9)

Currently without ASSP my Firewall/NAT box forwards all connections on
port 25 to 192.168.1.9

I have attempted to set up Mercury/ASSP as follows but can't send
outgoing mail:

Incoming:
Internet -> ASSP -> Mercury -> GroupWise -> Clients (Seems to work
fine)

Outgoing:
Clients -> GroupWise -> ASSP -> Mercury -> Internet (Doesn't seem to
work)

My settings in ASSP are:
SMTP Destination: 127.0.0.1:125 (Mercury is configured to listen on
this port)
Listen Port: 25
Accept All Mail: 127.0.0.1|192.168.1.9|192.168.1.
Local Domains: paratransit.net

Mercury Settings:
Allow Relay From: 127.0.0.1
SMTPC Client Relay Host: 192.168.1.9 (I think this may be the problem
as it's looping mail back to my GroupWise Server), But if I put anything
different here how will Mercury know to route incoming mail to my
GroupWise box?

GroupWise:
Relay Host: 192.168.1.20

Firewall/NAT box:
Forward all connections incoming on public interface port 25 to
192.168.1.20

Outgoing messages were undeliverable with the following errors:
Too many hops 
551 Forwarding to remote hosts disabled
Since GroupWise doesn't seem to display the message headers I can't see
exactly where the errors are coming from.

I'm wondering with GroupWise's GWIA why can't I do this (and eliminate
Mercury):

Internet -> ASSP -> GroupWise -> Client
Client -> GroupWise -> ASSP -> Internet  (use ASSP Relay Host Setting
point to my ISP's Smart Relay to connect to the Internet)

Any help would be appreciated.
Thanks,



David Churchill
Technical Services Manager
Paratransit Services
4810 Auto Center Way, Ste Z
Bremerton, WA  98312
(360) 377-7176 ext. 201
Mobile: (360)340-5961
dc...@pa...

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004
 
  

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.572 / Virus Database: 362 - Release Date: 1/27/2004