Discussion:
IMAP and GWAVA
(too old to reply)
Jack Cunha
2009-10-06 22:52:40 UTC
Permalink
NE 6.5; GW 6.5. Just set up a GWAVA 4.5 SMTP scanner inside
BorderManager and before GWIA (BM now NATs the A record public IP
address to the internal GWAVA address, rather than to the internal GWIA
address). I assume as a consequence of the public IP address now
pointing to the GWAVA box and not directly to GWIA, IMAP now doesn't
work b/c it cannot connect to the GWIA ("mail.domain.com is not an IMAP
4 server"). Is there a work around?
Michael Bell
2009-10-07 03:34:05 UTC
Permalink
Post by Jack Cunha
NE 6.5; GW 6.5. Just set up a GWAVA 4.5 SMTP scanner inside
BorderManager and before GWIA (BM now NATs the A record public IP
address to the internal GWAVA address, rather than to the internal GWIA
address). I assume as a consequence of the public IP address now
pointing to the GWAVA box and not directly to GWIA, IMAP now doesn't
work b/c it cannot connect to the GWIA ("mail.domain.com is not an IMAP
4 server"). Is there a work around?
http://forums.novell.com/novell-product-support-forums/bordermanager/bm-packet-filtering/40190-bm-3-8-port-forwarding.html
Jack Cunha
2009-10-08 00:56:22 UTC
Permalink
Post by Michael Bell
Post by Jack Cunha
NE 6.5; GW 6.5. Just set up a GWAVA 4.5 SMTP scanner inside
BorderManager and before GWIA (BM now NATs the A record public IP
address to the internal GWAVA address, rather than to the internal
GWIA address). I assume as a consequence of the public IP address now
pointing to the GWAVA box and not directly to GWIA, IMAP now doesn't
work b/c it cannot connect to the GWIA ("mail.domain.com is not an
IMAP 4 server"). Is there a work around?
http://forums.novell.com/novell-product-support-forums/bordermanager/bm-packet-filtering/40190-bm-3-8-port-forwarding.html
The link provided describes the BM port forwarding workaround where
there was only one public IP address. May I assume in my case, where I
have several, that the relevance of the TID is to the public IP
dedicated to my A record which now points to GWAVA, and no longer to
GWIA? If so, is that public IP again NATted to GWIA so that IMAP works,
yet the port 25 inbound mail is at the same time port forwarded to the
GWAVA internal address? Finally, how, if at all, does this relate to
the filter exceptions in place opening port 25 to inbound mail to GWAVA?
Michael Bell
2009-10-08 01:50:26 UTC
Permalink
Post by Jack Cunha
Post by Michael Bell
Post by Jack Cunha
NE 6.5; GW 6.5. Just set up a GWAVA 4.5 SMTP scanner inside
BorderManager and before GWIA (BM now NATs the A record public IP
address to the internal GWAVA address, rather than to the internal
GWIA address). I assume as a consequence of the public IP address
now pointing to the GWAVA box and not directly to GWIA, IMAP now
doesn't work b/c it cannot connect to the GWIA ("mail.domain.com is
not an IMAP 4 server"). Is there a work around?
http://forums.novell.com/novell-product-support-forums/bordermanager/bm-packet-filtering/40190-bm-3-8-port-forwarding.html
The link provided describes the BM port forwarding workaround where
there was only one public IP address. May I assume in my case, where I
have several, that the relevance of the TID is to the public IP
dedicated to my A record which now points to GWAVA, and no longer to
GWIA? If so, is that public IP again NATted to GWIA so that IMAP works,
yet the port 25 inbound mail is at the same time port forwarded to the
GWAVA internal address? Finally, how, if at all, does this relate to
the filter exceptions in place opening port 25 to inbound mail to GWAVA?
I don't understand BM (which I consider a secondrate firewall). I'm
merely pointing out that port forwarding/generic proxies are the obvious
workaround. In most firewalls you simply say "Port 143" goes to this
internal ip address. Which would be your gwia.

Loading...