Alternative to mulitple connection documents?

Our company has approximately ten servers distributed across different sites but connected over the internet (using 512kb ADSL connections). Replication uses a hub and spoke topology and that hub is the incoming smtp gateway but for Notes to Notes mail routing we prefer for mail to go directly from one server to another to reduce network traffic on the hub.

I would like to know if there is a way of getting mail to route from any server to any server without me having to create a connection document for each possible mail routing path. At present if there isn’t a connection document then the mail either gets held in the mail.box or else it gets routed to the mail.box of the first available server in alphabetical order.

We can create dozens of connection documents if necessary but as new servers come on board and ip addresses change it does make it difficult to administer.

Any suggestions would be welcomed.

Subject: Sure, put all the servers into the same “Notes Network” and mail routes automatically.

Port

Protocol

Notes Network

Net Address

Enabled

TCPIP

TCP

SameForAllServers

YourServer

ENABLED

Subject: RE: Sure, put all the servers into the same “Notes Network” and mail routes automatically.

Thanks,

I’ve started implementing this now. I had been following my Notes 4.5 training which said only servers on the same LAN should be in the same NNN but I suppose with all our servers being on broadband there is no reason why not. This allows for a much more efficient mail routing topology while saving time on administration.

Subject: As long as you have permanant connections (no Dialup) then that is the way to go.