Any exchange guru's here?
I have a small question and cannot find a answer to my question.
On the HUB or Edge server, we have a send connector sending all our external mail to a smart host. (Actually just an Ironport device - spam filter) We have a second line, second Ironport device. We do not want this to be load balanced, it should only be used in case there is a problem with either the primary link, primary ironport device. (we have good reason so dont go there
)
Exchange 2007/2010 send conenctors are not link state aware so when the primary line goes down, the mail jsut start queing. I read on one of the technet articles that some people are creating mx records in DNS and using this for outgoing email, as the send connector will always check mx, then a records, in that order.
Has anyone tried this? Is anyone got the same problem?
thanks
I have a small question and cannot find a answer to my question.
On the HUB or Edge server, we have a send connector sending all our external mail to a smart host. (Actually just an Ironport device - spam filter) We have a second line, second Ironport device. We do not want this to be load balanced, it should only be used in case there is a problem with either the primary link, primary ironport device. (we have good reason so dont go there
)Exchange 2007/2010 send conenctors are not link state aware so when the primary line goes down, the mail jsut start queing. I read on one of the technet articles that some people are creating mx records in DNS and using this for outgoing email, as the send connector will always check mx, then a records, in that order.
Has anyone tried this? Is anyone got the same problem?
thanks
Last edited: