I have two servers. Server A inside our company and Server B outside by an isp.
I use Server B to offer our employees webmail.
Server A is our gateway to send mail to internet. The two servers are connected by 1352 through a VPN. Firewall config: only Server A can initiate replication!!
This is what I want to achieve:
I want all mail (Notes mail + mail for external internet domains) that is sent by users on server B to be routed through Server A.
So Server A will do all the delivery.
Does anybody have any idea how to accomplish this? (with the difficulty that Server B cannot initiate a connection throught tcp 1352 / Notes replication)
Hi Wiard,Kinda strange request since B is already in the wild. But this is how it goes: set-up 2 connection documents for mail routing: A->B, Pull-Push, B->A Pull-Wait. This way B knows it can route through A, but simply needs to wait. You are facing an interesting problem: Since routing is initiated by A you either experience delays on sending or keep your servers and lines busy through constant polling. Eventually you are better off to implement the measures on B that you have on A (and make you want to route through A).
Unfortunally we can’t change the setup. Our IT policy doesn’t allow incoming connections on 1352, not even from the host on the ISP segment. The setup we’re trying to create is actually to avoid connections from the internet to our infrastructure, but we still want to give road-warriors access to their mailboxes.
All mailboxes live on server A and only a couple of mailboxes are being replicated from A to B (just some roadwarriors).
We just tried the Pull-Push vs Pull-Wait setup, but when I send an email from server B to a mailbox that resides on A, the mail router can’t seem to deliver the mail to mail.box, because it can’t connect to the destination server. This is pretty strange, because B should wait for a Pull request from A, not?
At first, I forgot to fill in an IP (because B shouldn’t connect on it’s own), but then the message couldn’t be delivered, because the destination server was an unknown TCP/IP host…
stw