Please disregard. I found the reason. I had set up some additional address spaces on routing group B connectors when I was troubleshooting some other issues way in the past, and subsequently forgot about it. Getting old sucks :(
-----Original Message----- From: Andrey Fyodorov Sent: Friday, January 10, 2003 1:21 PM To: Exchange Discussions Subject: Leaking Routing Group Hi all. Just saw some weird stuff. I have multiple administrative groups. Let's call them administrative group A and administrative group B. Each administrative group has its own routing group - RG A and RG B respectively. The SMTP connectors in RG B are set to service only RG B (connector scope) A user whose home server is in administrative group A (routing group A) sent a message to an internet address. For some weird reason, the message chose to go via a front-end server that belongs to administrative group B (routing group B) How could this happen? _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
