RE: Multiple domains.
Absolute madness last night. I was making the new policys which include the legacy domain names, some how EVERY single email address for EVERY single recipient in the whole organisation had there email address wiped, all that remained was the X400 addresses. What gives? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
Because you made a policy that actually applied to EVERY single recipient that told it to do that. Any new policy you make will be assigned a higher priority than your default policy, and will overwrite it for the recipients that the query that it's based upon (General screen, Modify, Find Now) applies to. Make one recipient policy. Add all the proper addresses. Apply it to nobody. And check (general modify find now) that it applies to nobody. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Tuesday, June 17, 2003 2:37 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. Subject: RE: Multiple domains. Absolute madness last night. I was making the new policys which include the legacy domain names, some how EVERY single email address for EVERY single recipient in the whole organisation had there email address wiped, all that remained was the X400 addresses. What gives? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
Okay, let me get this straight I think there is a problem with terminology between us, mostly on my behalf because I'm a little bit thick, but bear with me as I think I have it slightly sussed. Policy applies to = Filter Rules. i.e. in my default policy I have (mailnickname=*). Therefore what lies beneath that policy applies to everyone with a nickname that matches the criteria *, therefore everybody. So the email addresses in this policy is @interserveis.co.uk because our domain is interserveis.co.uk. As the filter rules match everyone the policy should be applied to everyone, therefore receiving an interserveis.co.uk email address. Now, the second policy that I have made, the filter rules for this are Blank, so I'm guessing that there is no match and the policy applies to nobody? Under this policy I have created the legacy domain names @kwikform.co.uk and @ukconstruction.co.uk. This is all working as I wanted it too now, when I create a new user they only receive a @interserveis.co.uk email addy and all kwikform/ukconstruction email addys we create are routing fine and none existent emails are being bounced. However, this still doesn't explain to me why every single email address from my entire organisation was deleted, I'm also scared to change anything again in case it resets them again. To get them back I simply changed the @interserveis.co.uk policy to @interserveis1.co.uk, set it back again and when it asked to update I said yes. That method has not allowed for all the none standard email addresses we had nore any of the kwikform ones that were setup. Perhaps you can comment on my methods and ensure that I am doing correctly? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: 17 June 2003 12:34 To: Exchange Discussions Subject: RE: Multiple domains. Because you made a policy that actually applied to EVERY single recipient that told it to do that. Any new policy you make will be assigned a higher priority than your default policy, and will overwrite it for the recipients that the query that it's based upon (General screen, Modify, Find Now) applies to. Make one recipient policy. Add all the proper addresses. Apply it to nobody. And check (general modify find now) that it applies to nobody. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Tuesday, June 17, 2003 2:37 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. Subject: RE: Multiple domains. Absolute madness last night. I was making the new policys which include the legacy domain names, some how EVERY single email address for EVERY single recipient in the whole organisation had there email address wiped, all that remained was the X400 addresses. What gives? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
How about making it real easy: Add all the SMTP addresses to your default policy, leave the check in the checkbox doodad that says this server's responsible for this address space, and take the check out of the little checkbox doodad that applies it. Delete any additional policy. Done. -tom -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 8:56 AM To: Exchange Discussions Subject: RE: Multiple domains. Okay, let me get this straight I think there is a problem with terminology between us, mostly on my behalf because I'm a little bit thick, but bear with me as I think I have it slightly sussed. Policy applies to = Filter Rules. i.e. in my default policy I have (mailnickname=*). Therefore what lies beneath that policy applies to everyone with a nickname that matches the criteria *, therefore everybody. So the email addresses in this policy is @interserveis.co.uk because our domain is interserveis.co.uk. As the filter rules match everyone the policy should be applied to everyone, therefore receiving an interserveis.co.uk email address. Now, the second policy that I have made, the filter rules for this are Blank, so I'm guessing that there is no match and the policy applies to nobody? Under this policy I have created the legacy domain names @kwikform.co.uk and @ukconstruction.co.uk. This is all working as I wanted it too now, when I create a new user they only receive a @interserveis.co.uk email addy and all kwikform/ukconstruction email addys we create are routing fine and none existent emails are being bounced. However, this still doesn't explain to me why every single email address from my entire organisation was deleted, I'm also scared to change anything again in case it resets them again. To get them back I simply changed the @interserveis.co.uk policy to @interserveis1.co.uk, set it back again and when it asked to update I said yes. That method has not allowed for all the none standard email addresses we had nore any of the kwikform ones that were setup. Perhaps you can comment on my methods and ensure that I am doing correctly? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Re: Multiple domains.
How about using the Black Hole DL trick instead? Create a Distribution Group with no members, add the no longer valid SMTP addresses to this group, then hide the group from the Exchange address lists. The emails will come in and disappear w/o generating a NDR. - Original Message - From: Neil Doody [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Monday, June 16, 2003 6:10 AM 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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
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=exchangetext_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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
Please point me in the right direction if you could, after I have made the Policy, what says who it applies to? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 15:58 To: Exchange Discussions Subject: RE: Multiple domains. The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
leave it blank. Or create a query that won't find anyone. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:36 AM To: Exchange Discussions Subject: RE: Multiple domains. Please point me in the right direction if you could, after I have made the Policy, what says who it applies to? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 15:58 To: Exchange Discussions Subject: RE: Multiple domains. The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
Im at a loss again here. I create the new recipient Policy, I call it something. I then proceed to enter the address space, which is @kwikform.co.uk in the Email Addresses tab. That tells exchange to accept @kwikform.co.uk emails. I don't see any other tab apart from filter users, is that what you mean? Im using exchange 2000. -Original Message- From: Fyodorov, Andrey [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 16:45 To: Exchange Discussions Subject: RE: Multiple domains. leave it blank. Or create a query that won't find anyone. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:36 AM To: Exchange Discussions Subject: RE: Multiple domains. Please point me in the right direction if you could, after I have made the Policy, what says who it applies to? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 15:58 To: Exchange Discussions Subject: RE: Multiple domains. The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_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=exchangetext_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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
on the General page, there is a button called [Filter rules] you could just ignore that button. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:50 AM To: Exchange Discussions Subject: RE: Multiple domains. Im at a loss again here. I create the new recipient Policy, I call it something. I then proceed to enter the address space, which is @kwikform.co.uk in the Email Addresses tab. That tells exchange to accept @kwikform.co.uk emails. I don't see any other tab apart from filter users, is that what you mean? Im using exchange 2000. -Original Message- From: Fyodorov, Andrey [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 16:45 To: Exchange Discussions Subject: RE: Multiple domains. leave it blank. Or create a query that won't find anyone. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:36 AM To: Exchange Discussions Subject: RE: Multiple domains. Please point me in the right direction if you could, after I have made the Policy, what says who it applies to? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: 16 June 2003 15:58 To: Exchange Discussions Subject: RE: Multiple domains. The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_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=exchangetext_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=exchangetext_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=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
Is there a way of configuring it so that your bounces do not come from [EMAIL PROTECTED] instead of postmaster@(default recipient policy)? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 7:58 AM To: Exchange Discussions The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] This email message may contain information that is confidential and proprietary to Babcock Brown or a third party. If you are not the intended recipient, please contact the sender and destroy the original and any copies of the original message. Babcock Brown takes measures to protect the content of its communications. However, Babcock Brown cannot guarantee that email messages will not be intercepted by third parties or that email messages will be free of errors or viruses. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Multiple domains.
http://victori.hypermart.net/rpm.html -Original Message- From: Carmila Fresco [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:31 PM Posted To: swynk Conversation: Multiple domains. Subject: RE: Multiple domains. Is there a way of configuring it so that your bounces do not come from [EMAIL PROTECTED] instead of postmaster@(default recipient policy)? -Original Message- From: Tom Meunier [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 7:58 AM To: Exchange Discussions The recipient policy doesn't have to apply to anybody (much less everybody) - they just need to BE there. Make a recipient policy that applies to nobody that has all those domains. Get rid of the connector. Problem solved. They'll bounce properly at that point. -Original Message- From: Neil Doody [mailto:[EMAIL PROTECTED] Posted At: Monday, June 16, 2003 5:11 AM Posted To: MSExchange Mailing List Conversation: Multiple domains. 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=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] This email message may contain information that is confidential and proprietary to Babcock Brown or a third party. If you are not the intended recipient, please contact the sender and destroy the original and any copies of the original message. Babcock Brown takes measures to protect the content of its communications. However, Babcock Brown cannot guarantee that email messages will not be intercepted by third parties or that email messages will be free of errors or viruses. _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_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=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
