Yes you do. -----Original Message----- From: Richard Stovall [mailto:[email protected]] Sent: Thursday, March 22, 2012 8:31 PM To: MS-Exchange Admin Issues Subject: Re: Proxy addresses for new (external) domain
Don't you need a defined recipient policy which includes the new domain in order to accept e-mail into an Exchange 2003 organization, as opposed to manually adding proxy addresses to individual accounts for domains that don't currently exist in a recipient policy? On Thu, Mar 22, 2012 at 7:55 PM, Jim von Stein <[email protected]> wrote: > We’re running Server 2003/2008R2 domain with Exchange 2003 standard. > We have a “dual” domain going, with soastc.local used internally on > private address space and soastc.org external. My Exchange server is > configured to receive soastc.org mail and pass it on to users in the > .local domain. So far so good, everything is working. > > > > After 34 years, they decide to change the name of the organization. I > registered a domain for the new name, and of course, they want to be > able to receive e-mail at the new domain name as well as the old one > (at least for now). I dug out “Mastering Exchange Server 2003” and > started reading up. I ran across the claim in the book that I can just > assign proxy addresses, even with different domains to users, as long > as I point the MX record for the new domain at my server. I did that, > and gave myself a kairosnw.org address, but when I try to send to it from > outside, I get this: > > > > > > ----- The following addresses had permanent fatal errors ----- > <[email protected]> > (reason: 550 Requested action not taken: mailbox unavailable) > > ----- Transcript of session follows ----- ... while talking to > smtp.kairosnw.org.: >>>> RCPT To:<[email protected]> > <<< 550 Requested action not taken: mailbox unavailable > 550 5.1.1 <[email protected]>... User unknown > > > Reporting-MTA: dns; webmail.userservices.net > Received-From-MTA: DNS; localhost.localdomain > Arrival-Date: Thu, 22 Mar 2012 16:16:50 -0700 > > Final-Recipient: RFC822; [email protected] > Action: failed > Status: 5.1.1 > Remote-MTA: DNS; smtp.kairosnw.org > Diagnostic-Code: SMTP; 550 Requested action not taken: mailbox > unavailable > Last-Attempt-Date: Thu, 22 Mar 2012 16:16:50 -0700 > > > > So, is the book wrong? Am I missing some part of the picture? It would > appear that if I want to assign a second IP address to my Exchange > Server, I can create a second SMTP Virtual Server for the second > domain, but I’m not sure that I want to do that (especially if I don’t have > to). > > > > Suggestions? Advice? > > > > Jim v. > > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
