Posts Tagged ‘Mailrouting’

network comm failover to a cluster

We have sites in South America where network connectivity is very unreliable. We have MPLS lines connecting the remote offices in those locations, and we also have Internet access from each of the offices.

When setting up our replication/mail routing architecture in these locations where connectivity is unstable we got a little creative.

First, we have our hub servers in the Home office in Hong Kong. These hub servers do all of the replication from Hub to spoke. This cuts down on the overall replication overhead on the network. The idea is that cluster cache doesn’t have to be rebuilt every time if we have only the hubs replicating to the spokes. At the end of the day, network utilization and time required to replicate is actually lower.

We also put clusters in each site. This alleviates downtime in the event that one of the servers goes down. Since we have clusters, we can set the connection document to replicate with the cluster instead of the individual servers. This provides much benefit because replication still occurs if one server is down. It also reduces the network utilization in half because replication will only occur one time, to the cluster, instead of twice to each individual server. Read the rest of this entry »

how to re-route all of your mail through another hub server

We have two hub servers in our environment that are clustered.

We use these as replication hubs to all of our spokes (local and remote sites). Additionally, these act as sort of a mail hub since all of our remotes sites are not directly connected to our home office site. Lastly, they also serve as outbound SMTP gateways.

Any mail that is sent from Chile to a user in Spain gets routed through Hong Kong since their is not a direct connection from Chile to Spain.

All servers in each site are in their own NNN (Notes Named Network). The Hong Kong site servers are in their own NNN. The hubs are in their own NNN.

This allows us to route mail through Hong Kong where necessary using mail connection documents. Read the rest of this entry »

Skipping message because ReadyToSweep

Yesterday was a rough day being a Domino mail server admin.

First, let me explain our environment. Most of our company is on Domino and Notes 6.5.1.-6 (mostly Notes 6.5.4).

There is one division that refuses to move to Notes because they love outlook, and their main excuse is that there is the 100 mail rule limitation of Notes. They actually use email as a system like I’ve never seen. They manage a fleet of ships, and each ships sends different kinds of messages, these messages are sent to groups that are nested several times, so many many people receive them. Some people need them for one reason or another. These messages also go into a linux application server and are search able via a web interface.

So basically, they cannot live without having sometimes 200 mail rules. They are pushing electronic mail to the boundaries. I’m sure there is a better way for them to do all of this, but who has the time to pitch a better idea to them, especially when they have no budget. Read the rest of this entry »


I'm currently available
for Lotus Notes / Domino consulting engagements.


Connect with me: