Ahh, the joys of "Inbound Only" and "Outbound Only" IMCs...
A few issues here. First, as you've found, the Inbound Only setting doesn't do a whole lot of anything. Its a strange bug that never seemed to get fixed, but the work arounds are simple. Second, since you're dealing with site routing (multiple sites), part of the issue here is that, for its given address space (on the Address SPace tab - and it is most likely * [wildcard]), this IMC is the lowest cost path out. Keep in mind that since the Inbound only setting doesn't cut it, cost will count. By default, all connectors have a cost of 1, and all costs are additive. In other words, assuming all your connectors have costs of 1, the IMC on the other side of the X.400 link will have an apparent cost of 2 for the users on this box (1 for the IMC and 1 for the X.400), while this one is costed at one. The maximum cost is 100, so go ahead and set it to 100 (Address Space Tab). Third, mail routing will happen via the most specific match of address space, with * being the least specific. Another method (and more foolproof than adjusting the cost) is to set this IMC with an address space that cannot be matched, which will result in it never getting selected. For historical reasons, the easiest way to ensure this is to change the address space for the connector from "*" to "clownpenis.fart". After making any of these changes, you need to restart the service for the change to take effect. Roger ------------------------------------------------------ Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com > -----Original Message----- > From: Lloyd, D (Dave) (IT Systems) > [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 16, 2001 12:06 AM > To: Exchange Discussions > Subject: IMS questions > > > Hi all, I need a bit of help! > > We've recently added an IMS connector to one of our servers > and configured > it for Incoming only. An SMTP relay server then pokes mail > through port 25 > to pass to exchange mail boxes. This all works ok and was > created soley to > receive mail from a new e-banking network. > > The problem is that outgoing SMTP addressed mail should NOT > go to the IMS, > since it should use our x400 backbone. This is because there > is no Internet > connection available for the connector yet. > Over the last week or so, users have started complaining that > Internet mail > is not getting out. > Tracking specific messages show that the mail appears to hit > the IMS. Since > it has no Internet connection it cannot go anywhere. However, other > messages successfully hit the X400 and get out to the > Internet as planned. > > My questions are thus: > I have enabled logging on the IMS, but where do they get > stored? Event logs > have nothing. Can the tracking.logs be interpreted by an > application to > make them easier to understand? > Why would any mail hit the IMs at all if it is configured > for Inbound only? > Under the Address Space Tab, we set the cost to 100 and the scope to > Location. I just read about troubleshooting outgoing mail, > and it mentioned > that if Address is too restrictive it will play a part. It > suggests setting > t to *. * is the default and is what ours was. Thinking > this might be a > key, I have set it to a fictitious domain of .nowhereatall. > My thinking is > that any mail NOT destined for .nowhereatall will > automatically be routed > via x400 and not IMS. Does this sound correct? > What do the Delivery Restrictions do/apply to? I could > accept mail from > no-one, but would this affect the incoming from e-banking? > > If anyone has any ideas, please advise. We're running Exchange 5.5 > (Enterprise) SP3 on NT4 SP5 > > cheers > Dave > > ================================================================== > De informatie opgenomen in dit bericht kan vertrouwelijk zijn en > is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht > onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en > de afzender direct te informeren door het bericht te retourneren. > ================================================================== > The information contained in this message may be confidential > and is intended to be exclusively for the addressee. Should you > receive this message unintentionally, please do not use the contents > herein and notify the sender immediately by return e-mail. > > > ================================================================== > > > _________________________________________________________________ > 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]
