I think that technically it doesn't make the server think the domain as local it just allows relaying to that domain, so when an email is sent in the server allows for its transport, then it finds itself as the the destination and attempts delivery to itself.
Or something like that. Ill try the policy thing, look into how to make it apply to nobody. -----Original Message----- From: Fyodorov, Andrey [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 16:23 To: Exchange Discussions Subject: RE: Multiple domains. I never thought that adding the domain names to Address Space and checking "allow relaying to these domains" would make Exchange think that these are local domains. I only use recipient policies to anchor domains as local. -----Original Message----- From: Neil Doody [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 6:11 AM To: Exchange Discussions Subject: Multiple domains. Okay, weve got more than one local domain on the exchange server, only one domain is actually used for the servers, i.e. the active directory, the other domains are just legacy internet domains with the MX record set as our exchange server. To allow delivery of emails to people in the exchange organisation you can either use recipient policies with the desired domain, or alternatively add a new connector, add the address space and tick "allow relaying to these domains". We have gone for the latter option as we do not want legacy email addresses created automatically within the domain, we only want people who we manually create email addresses to receive email from the legacy domain. However, the problem is we are now getting a large mail queue for the legacy domains as the server is attempting to relay the messages to the end user but the email address does not exist within our organisation. That is people are trying to send emails, i.e. spammers to email addresses that previously existed and the server is continually trying to relay that email back to itself and were getting all sorts of delay notifications etc. What I was wondering is how I can tell the server to realise that the email address doesn't exist and bounce it away ? Or perhaps im going about this whole thing the wrong way, maybe someone can enlighten me :) _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
