Email routing redundant

Server A has 2 connection documents to Server B and Server C with 2 different routing cost , one is set as 1 (A->B)and the other is 3(A->C). each with “Push” of routing type.When server B shutdown, email in Server A will pend and won’t deliver to Server C. How could email can deliver to Server C automatically when B is down ? I want to keep priority of B and C, that’s , B is the primary receiver server from Server A and Server C is the secondary receiver server from Server A.

Does there any solution solve the problem? (Please don’t tell me set routing cost with the same value. Thank you.)

Subject: Email routing redundant

Kevins,

See the following technote: http://www-1.ibm.com/support/docview.wss?rs=463&context=SSKTMJ&context=SSKTWP&q1=routing+cost&uid=swg21091859&loc=en_US&cs=utf-8&lang=en

It seems that the main connection document should have a routing cost of 0, and the backup connection document a routing cost of 1.

I haven’t tried this myself… (the advice from IBM is not to fiddle with the routing costs: they usually work fine at the defaults).

Another point: If the servers are on the same LAN, its possible to put A & B in the same NotesNamedNetwork (no connection document needed for mail routing). Then you could define a connection document for A->C (in a different NNN) that would work according to your definitions.

Subject: RE: Email routing redundant

Dear BenThanks and I appreciate your recommendation and material.

It is reasonable.