"LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
> Two firms merged, one using SBS 2003 with Exchange.  Using Exchange we
> want
> to continue you accept mail from olddomain.com and also accept mail from
> newdomain.com.  MX records for Olddomain and Newdomain are Identical. User
> names are constant.  In exchange manager I expanded Recipients – selected
> Recipients policies – selected E-Mail Addresses tab and entered the new
> domain name.  Mail sent to the new domain is being returned with the
> following error message:
>
> SMTP error from remote mail server after RCPT TO:<vi***@newdomain.com>:
>    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
>    554 No relaying allowed - psmtp
>
> Any insight in how to correct this problem?
>
> Thank you
>

"Ed Crowley [MVP]" wrote:

> You updated the default recipient policy with your change, correct?
>
> What happens when you communicate directly with your Exchange server from
> inside your network:
>
> telnet servername 25
> helo you.company.com
> mail from:***@company.com
> rcpt to:***@newdomain.com
> data
> This is a test.
> ..
> quit
>
> If you can connect directly to the Exchange server and this is successful
> (with the appropriate text substitutions), then something between the
> Internet and your Exchange server is rejecting the domain.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
> > Two firms merged, one using SBS 2003 with Exchange.  Using Exchange we
> > want
> > to continue you accept mail from olddomain.com and also accept mail from
> > newdomain.com.  MX records for Olddomain and Newdomain are Identical. User
> > names are constant.  In exchange manager I expanded Recipients – selected
> > Recipients policies – selected E-Mail Addresses tab and entered the new
> > domain name.  Mail sent to the new domain is being returned with the
> > following error message:
> >
> > SMTP error from remote mail server after RCPT TO:<vi***@newdomain.com>:
> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
> >    554 No relaying allowed - psmtp
> >
> > Any insight in how to correct this problem?
> >
> > Thank you
> >
>
>

"LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
> Thank you for the responce.
>
> When I Helo myname.olddomain.com I receive the following response:
> 250 servername.domainname.local Hello [ip address]
>
> when I helo myname.newdomain.com I receive the following response:
> 501 5.5.4 Invalid Address
>
> I am not sure what this means.
>
> Thank you
>
>
>
> "Ed Crowley [MVP]" wrote:
>
>> You updated the default recipient policy with your change, correct?
>>
>> What happens when you communicate directly with your Exchange server from
>> inside your network:
>>
>> telnet servername 25
>> helo you.company.com
>> mail from:***@company.com
>> rcpt to:***@newdomain.com
>> data
>> This is a test.
>> ..
>> quit
>>
>> If you can connect directly to the Exchange server and this is successful
>> (with the appropriate text substitutions), then something between the
>> Internet and your Exchange server is rejecting the domain.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> ..
>>
>> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
>> > Two firms merged, one using SBS 2003 with Exchange.  Using Exchange we
>> > want
>> > to continue you accept mail from olddomain.com and also accept mail
>> > from
>> > newdomain.com.  MX records for Olddomain and Newdomain are Identical.
>> > User
>> > names are constant.  In exchange manager I expanded Recipients –
>> > selected
>> > Recipients policies – selected E-Mail Addresses tab and entered the new
>> > domain name.  Mail sent to the new domain is being returned with the
>> > following error message:
>> >
>> > SMTP error from remote mail server after RCPT TO:<vi***@newdomain.com>:
>> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
>> >    554 No relaying allowed - psmtp
>> >
>> > Any insight in how to correct this problem?
>> >
>> > Thank you
>> >
>>
>>

"Ed Crowley [MVP]" wrote:

> The HELO doesn't matter.  It's the response to the rcpt to: that matters.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
> > Thank you for the responce.
> >
> > When I Helo myname.olddomain.com I receive the following response:
> > 250 servername.domainname.local Hello [ip address]
> >
> > when I helo myname.newdomain.com I receive the following response:
> > 501 5.5.4 Invalid Address
> >
> > I am not sure what this means.
> >
> > Thank you
> >
> >
> >
> > "Ed Crowley [MVP]" wrote:
> >
> >> You updated the default recipient policy with your change, correct?
> >>
> >> What happens when you communicate directly with your Exchange server from
> >> inside your network:
> >>
> >> telnet servername 25
> >> helo you.company.com
> >> mail from:***@company.com
> >> rcpt to:***@newdomain.com
> >> data
> >> This is a test.
> >> ..
> >> quit
> >>
> >> If you can connect directly to the Exchange server and this is successful
> >> (with the appropriate text substitutions), then something between the
> >> Internet and your Exchange server is rejecting the domain.
> >> --
> >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> ..
> >>
> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> >> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
> >> > Two firms merged, one using SBS 2003 with Exchange.  Using Exchange we
> >> > want
> >> > to continue you accept mail from olddomain.com and also accept mail
> >> > from
> >> > newdomain.com.  MX records for Olddomain and Newdomain are Identical.
> >> > User
> >> > names are constant.  In exchange manager I expanded Recipients –
> >> > selected
> >> > Recipients policies – selected E-Mail Addresses tab and entered the new
> >> > domain name.  Mail sent to the new domain is being returned with the
> >> > following error message:
> >> >
> >> > SMTP error from remote mail server after RCPT TO:<vi***@newdomain.com>:
> >> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
> >> >    554 No relaying allowed - psmtp
> >> >
> >> > Any insight in how to correct this problem?
> >> >
> >> > Thank you
> >> >
> >>
> >>
>
>

"LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
news:C30E36C6-788A-40A7-B21E-ADFF841A9A3C@microsoft.com...
> The response to the rcpt to:myn***@newdomain.com was
> 250 2.1.5. myn***@newdomain.com
> data
> 354 Start mail input; end with <CRLF>.<CRLF>
> THIS IS A TEST
>
> no response - What is the <CRLG>?
>
> thank you for your assistance.
>
>
>
>
> "Ed Crowley [MVP]" wrote:
>
>> The HELO doesn't matter.  It's the response to the rcpt to: that matters.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> ..
>>
>> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
>> > Thank you for the responce.
>> >
>> > When I Helo myname.olddomain.com I receive the following response:
>> > 250 servername.domainname.local Hello [ip address]
>> >
>> > when I helo myname.newdomain.com I receive the following response:
>> > 501 5.5.4 Invalid Address
>> >
>> > I am not sure what this means.
>> >
>> > Thank you
>> >
>> >
>> >
>> > "Ed Crowley [MVP]" wrote:
>> >
>> >> You updated the default recipient policy with your change, correct?
>> >>
>> >> What happens when you communicate directly with your Exchange server
>> >> from
>> >> inside your network:
>> >>
>> >> telnet servername 25
>> >> helo you.company.com
>> >> mail from:***@company.com
>> >> rcpt to:***@newdomain.com
>> >> data
>> >> This is a test.
>> >> ..
>> >> quit
>> >>
>> >> If you can connect directly to the Exchange server and this is
>> >> successful
>> >> (with the appropriate text substitutions), then something between the
>> >> Internet and your Exchange server is rejecting the domain.
>> >> --
>> >> Ed Crowley MVP
>> >> "There are seldom good technological solutions to behavioral
>> >> problems."
>> >> ..
>> >>
>> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> >> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
>> >> > Two firms merged, one using SBS 2003 with Exchange.  Using Exchange
>> >> > we
>> >> > want
>> >> > to continue you accept mail from olddomain.com and also accept mail
>> >> > from
>> >> > newdomain.com.  MX records for Olddomain and Newdomain are
>> >> > Identical.
>> >> > User
>> >> > names are constant.  In exchange manager I expanded Recipients –
>> >> > selected
>> >> > Recipients policies – selected E-Mail Addresses tab and entered the
>> >> > new
>> >> > domain name.  Mail sent to the new domain is being returned with the
>> >> > following error message:
>> >> >
>> >> > SMTP error from remote mail server after RCPT
>> >> > TO:<vi***@newdomain.com>:
>> >> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
>> >> >    554 No relaying allowed - psmtp
>> >> >
>> >> > Any insight in how to correct this problem?
>> >> >
>> >> > Thank you
>> >> >
>> >>
>> >>
>>
>>

"Ed Crowley [MVP]" wrote:

> Enter all of the commands as I typed them except substitute your own
> addresses and domains:
>
> telnet servername 25
> helo you.company.com
> mail from:***@company.com
> rcpt to:***@newdomain.com
> data
> This is a test.
> ..
> quit
>
> The reason you got no response is that you didn't enter a dot (.) on a line
> by itself.  That's what <CRLF>.<CRLF> means--CRLF = Carriage Return Line
> Feed, or the Enter key when you're using Windows telnet.
>
> Post back everything you got back.  The best way is to copy the text content
> of the command window into your reply message.
>
> Still, what you've posted indicates that your server is receiving mail for
> newdomain.com, which I kind of suspected because the bounce message you
> first posted doesn't look like an Exchange reply.  Do you have any other
> SMTP hosts between the Internet and your Exchange server, such as an
> antispam filter, antivirus host, or "smart" firewall that's doing SMTP
> inspection?
>
> If you post the real name of newdomain, I can look to see if it looks like
> Exchange is doing the answering.  Or, you're welcome to look up
> newdomain.com's MX record, retrieve the IP addresses of the corresponding A
> records, and doing your own telnet session from an Internet host to each of
> newdomain.com's e-mail servers.  You can learn a lot from just the initial
> banner--it might tell you that you haven't hit your Exchange server.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> news:C30E36C6-788A-40A7-B21E-ADFF841A9A3C@microsoft.com...
> > The response to the rcpt to:myn***@newdomain.com was
> > 250 2.1.5. myn***@newdomain.com
> > data
> > 354 Start mail input; end with <CRLF>.<CRLF>
> > THIS IS A TEST
> >
> > no response - What is the <CRLG>?
> >
> > thank you for your assistance.
> >
> >
> >
> >
> > "Ed Crowley [MVP]" wrote:
> >
> >> The HELO doesn't matter.  It's the response to the rcpt to: that matters.
> >> --
> >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> ..
> >>
> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> >> news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
> >> > Thank you for the responce.
> >> >
> >> > When I Helo myname.olddomain.com I receive the following response:
> >> > 250 servername.domainname.local Hello [ip address]
> >> >
> >> > when I helo myname.newdomain.com I receive the following response:
> >> > 501 5.5.4 Invalid Address
> >> >
> >> > I am not sure what this means.
> >> >
> >> > Thank you
> >> >
> >> >
> >> >
> >> > "Ed Crowley [MVP]" wrote:
> >> >
> >> >> You updated the default recipient policy with your change, correct?
> >> >>
> >> >> What happens when you communicate directly with your Exchange server
> >> >> from
> >> >> inside your network:
> >> >>
> >> >> telnet servername 25
> >> >> helo you.company.com
> >> >> mail from:***@company.com
> >> >> rcpt to:***@newdomain.com
> >> >> data
> >> >> This is a test.
> >> >> ..
> >> >> quit
> >> >>
> >> >> If you can connect directly to the Exchange server and this is
> >> >> successful
> >> >> (with the appropriate text substitutions), then something between the
> >> >> Internet and your Exchange server is rejecting the domain.
> >> >> --
> >> >> Ed Crowley MVP
> >> >> "There are seldom good technological solutions to behavioral
> >> >> problems."
> >> >> ..
> >> >>
> >> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> >> >> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
> >> >> > Two firms merged, one using SBS 2003 with Exchange.  Using Exchange
> >> >> > we
> >> >> > want
> >> >> > to continue you accept mail from olddomain.com and also accept mail
> >> >> > from
> >> >> > newdomain.com.  MX records for Olddomain and Newdomain are
> >> >> > Identical.
> >> >> > User
> >> >> > names are constant.  In exchange manager I expanded Recipients –
> >> >> > selected
> >> >> > Recipients policies – selected E-Mail Addresses tab and entered the
> >> >> > new
> >> >> > domain name.  Mail sent to the new domain is being returned with the
> >> >> > following error message:
> >> >> >
> >> >> > SMTP error from remote mail server after RCPT
> >> >> > TO:<vi***@newdomain.com>:
> >> >> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
> >> >> >    554 No relaying allowed - psmtp
> >> >> >
> >> >> > Any insight in how to correct this problem?
> >> >> >
> >> >> > Thank you
> >> >> >
> >> >>
> >> >>
> >>
> >>
>
>

"LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
news:E6B97F47-5010-4667-8E4F-18A595426CF1@microsoft.com...
> Hello and thank you again for your assistance.
>
> The SBS server domain is Cuddy.local
> The SBS Server 2003 running Exchange named ZEUS
> The working old SMTP domain is cuddylaw.com
> My email address is vi***@cuddylaw.com
> The new SMTP domain which is NOT working is cuddymccarthy.com
> My new email address which is NOT working is vi***@cuddymccarthy.com
>
> Below is a copy of the commands and results from your post.
>
> 220 zeus.Cuddy.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959
> ready
> at  Thu, 22 Jan 2009 21:55:41 -0700
> helo vince.cuddylaw.com
> 250 zeus.Cuddy.local Hello [192.168.0.16]
> mail from:vi***@cuddylaw.com
> 250 2.1.0 vi***@cuddylaw.com....Sender OK
> rcpt to:vi***@cuddymccarthy.com
> 250 2.1.5 vi***@cuddymccarthy.com
> data
> 354 Start mail input; end with <CRLF>.<CRLF>
> This is a test
> .
> 250 2.6.0 <ZEUShnHcWhlEqwdD8sM00000d7e@zeus.Cuddy.local> Queued mail for
> deliver
> y
> ..
> 500 5.3.3 Unrecognized command
> Quit
> 221 2.0.0 zeus.Cuddy.local Service closing transmission channel
>
>
> Thank you again for any assistance you can provide.
>
>
>
>
>
> "Ed Crowley [MVP]" wrote:
>
>> Enter all of the commands as I typed them except substitute your own
>> addresses and domains:
>>
>> telnet servername 25
>> helo you.company.com
>> mail from:***@company.com
>> rcpt to:***@newdomain.com
>> data
>> This is a test.
>> ..
>> quit
>>
>> The reason you got no response is that you didn't enter a dot (.) on a
>> line
>> by itself.  That's what <CRLF>.<CRLF> means--CRLF = Carriage Return Line
>> Feed, or the Enter key when you're using Windows telnet.
>>
>> Post back everything you got back.  The best way is to copy the text
>> content
>> of the command window into your reply message.
>>
>> Still, what you've posted indicates that your server is receiving mail
>> for
>> newdomain.com, which I kind of suspected because the bounce message you
>> first posted doesn't look like an Exchange reply.  Do you have any other
>> SMTP hosts between the Internet and your Exchange server, such as an
>> antispam filter, antivirus host, or "smart" firewall that's doing SMTP
>> inspection?
>>
>> If you post the real name of newdomain, I can look to see if it looks
>> like
>> Exchange is doing the answering.  Or, you're welcome to look up
>> newdomain.com's MX record, retrieve the IP addresses of the corresponding
>> A
>> records, and doing your own telnet session from an Internet host to each
>> of
>> newdomain.com's e-mail servers.  You can learn a lot from just the
>> initial
>> banner--it might tell you that you haven't hit your Exchange server.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> ..
>>
>> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> news:C30E36C6-788A-40A7-B21E-ADFF841A9A3C@microsoft.com...
>> > The response to the rcpt to:myn***@newdomain.com was
>> > 250 2.1.5. myn***@newdomain.com
>> > data
>> > 354 Start mail input; end with <CRLF>.<CRLF>
>> > THIS IS A TEST
>> >
>> > no response - What is the <CRLG>?
>> >
>> > thank you for your assistance.
>> >
>> >
>> >
>> >
>> > "Ed Crowley [MVP]" wrote:
>> >
>> >> The HELO doesn't matter.  It's the response to the rcpt to: that
>> >> matters.
>> >> --
>> >> Ed Crowley MVP
>> >> "There are seldom good technological solutions to behavioral
>> >> problems."
>> >> ..
>> >>
>> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> >> news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
>> >> > Thank you for the responce.
>> >> >
>> >> > When I Helo myname.olddomain.com I receive the following response:
>> >> > 250 servername.domainname.local Hello [ip address]
>> >> >
>> >> > when I helo myname.newdomain.com I receive the following response:
>> >> > 501 5.5.4 Invalid Address
>> >> >
>> >> > I am not sure what this means.
>> >> >
>> >> > Thank you
>> >> >
>> >> >
>> >> >
>> >> > "Ed Crowley [MVP]" wrote:
>> >> >
>> >> >> You updated the default recipient policy with your change, correct?
>> >> >>
>> >> >> What happens when you communicate directly with your Exchange
>> >> >> server
>> >> >> from
>> >> >> inside your network:
>> >> >>
>> >> >> telnet servername 25
>> >> >> helo you.company.com
>> >> >> mail from:***@company.com
>> >> >> rcpt to:***@newdomain.com
>> >> >> data
>> >> >> This is a test.
>> >> >> ..
>> >> >> quit
>> >> >>
>> >> >> If you can connect directly to the Exchange server and this is
>> >> >> successful
>> >> >> (with the appropriate text substitutions), then something between
>> >> >> the
>> >> >> Internet and your Exchange server is rejecting the domain.
>> >> >> --
>> >> >> Ed Crowley MVP
>> >> >> "There are seldom good technological solutions to behavioral
>> >> >> problems."
>> >> >> ..
>> >> >>
>> >> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
>> >> >> > Two firms merged, one using SBS 2003 with Exchange.  Using
>> >> >> > Exchange
>> >> >> > we
>> >> >> > want
>> >> >> > to continue you accept mail from olddomain.com and also accept
>> >> >> > mail
>> >> >> > from
>> >> >> > newdomain.com.  MX records for Olddomain and Newdomain are
>> >> >> > Identical.
>> >> >> > User
>> >> >> > names are constant.  In exchange manager I expanded Recipients –
>> >> >> > selected
>> >> >> > Recipients policies – selected E-Mail Addresses tab and entered
>> >> >> > the
>> >> >> > new
>> >> >> > domain name.  Mail sent to the new domain is being returned with
>> >> >> > the
>> >> >> > following error message:
>> >> >> >
>> >> >> > SMTP error from remote mail server after RCPT
>> >> >> > TO:<vi***@newdomain.com>:
>> >> >> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
>> >> >> >    554 No relaying allowed - psmtp
>> >> >> >
>> >> >> > Any insight in how to correct this problem?
>> >> >> >
>> >> >> > Thank you
>> >> >> >
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>

"Ed Crowley [MVP]" wrote:

> Exchange is accepting mail for the secondary domain.  Now you can try the
> second test, do the same thing from the Internet, connecting to the server
> in the A record referred to by your MX record.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> news:E6B97F47-5010-4667-8E4F-18A595426CF1@microsoft.com...
> > Hello and thank you again for your assistance.
> >
> > The SBS server domain is Cuddy.local
> > The SBS Server 2003 running Exchange named ZEUS
> > The working old SMTP domain is cuddylaw.com
> > My email address is vi***@cuddylaw.com
> > The new SMTP domain which is NOT working is cuddymccarthy.com
> > My new email address which is NOT working is vi***@cuddymccarthy.com
> >
> > Below is a copy of the commands and results from your post.
> >
> > 220 zeus.Cuddy.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959
> > ready
> > at  Thu, 22 Jan 2009 21:55:41 -0700
> > helo vince.cuddylaw.com
> > 250 zeus.Cuddy.local Hello [192.168.0.16]
> > mail from:vi***@cuddylaw.com
> > 250 2.1.0 vi***@cuddylaw.com....Sender OK
> > rcpt to:vi***@cuddymccarthy.com
> > 250 2.1.5 vi***@cuddymccarthy.com
> > data
> > 354 Start mail input; end with <CRLF>.<CRLF>
> > This is a test
> > .
> > 250 2.6.0 <ZEUShnHcWhlEqwdD8sM00000d7e@zeus.Cuddy.local> Queued mail for
> > deliver
> > y
> > ..
> > 500 5.3.3 Unrecognized command
> > Quit
> > 221 2.0.0 zeus.Cuddy.local Service closing transmission channel
> >
> >
> > Thank you again for any assistance you can provide.
> >
> >
> >
> >
> >
> > "Ed Crowley [MVP]" wrote:
> >
> >> Enter all of the commands as I typed them except substitute your own
> >> addresses and domains:
> >>
> >> telnet servername 25
> >> helo you.company.com
> >> mail from:***@company.com
> >> rcpt to:***@newdomain.com
> >> data
> >> This is a test.
> >> ..
> >> quit
> >>
> >> The reason you got no response is that you didn't enter a dot (.) on a
> >> line
> >> by itself.  That's what <CRLF>.<CRLF> means--CRLF = Carriage Return Line
> >> Feed, or the Enter key when you're using Windows telnet.
> >>
> >> Post back everything you got back.  The best way is to copy the text
> >> content
> >> of the command window into your reply message.
> >>
> >> Still, what you've posted indicates that your server is receiving mail
> >> for
> >> newdomain.com, which I kind of suspected because the bounce message you
> >> first posted doesn't look like an Exchange reply.  Do you have any other
> >> SMTP hosts between the Internet and your Exchange server, such as an
> >> antispam filter, antivirus host, or "smart" firewall that's doing SMTP
> >> inspection?
> >>
> >> If you post the real name of newdomain, I can look to see if it looks
> >> like
> >> Exchange is doing the answering.  Or, you're welcome to look up
> >> newdomain.com's MX record, retrieve the IP addresses of the corresponding
> >> A
> >> records, and doing your own telnet session from an Internet host to each
> >> of
> >> newdomain.com's e-mail servers.  You can learn a lot from just the
> >> initial
> >> banner--it might tell you that you haven't hit your Exchange server.
> >> --
> >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> ..
> >>
> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> >> news:C30E36C6-788A-40A7-B21E-ADFF841A9A3C@microsoft.com...
> >> > The response to the rcpt to:myn***@newdomain.com was
> >> > 250 2.1.5. myn***@newdomain.com
> >> > data
> >> > 354 Start mail input; end with <CRLF>.<CRLF>
> >> > THIS IS A TEST
> >> >
> >> > no response - What is the <CRLG>?
> >> >
> >> > thank you for your assistance.
> >> >
> >> >
> >> >
> >> >
> >> > "Ed Crowley [MVP]" wrote:
> >> >
> >> >> The HELO doesn't matter.  It's the response to the rcpt to: that
> >> >> matters.
> >> >> --
> >> >> Ed Crowley MVP
> >> >> "There are seldom good technological solutions to behavioral
> >> >> problems."
> >> >> ..
> >> >>
> >> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
> >> >> news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
> >> >> > Thank you for the responce.
> >> >> >
> >> >> > When I Helo myname.olddomain.com I receive the following response:
> >> >> > 250 servername.domainname.local Hello [ip address]
> >> >> >
> >> >> > when I helo myname.newdomain.com I receive the following response:
> >> >> > 501 5.5.4 Invalid Address
> >> >> >
> >> >> > I am not sure what this means.
> >> >> >
> >> >> > Thank you
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Ed Crowley [MVP]" wrote:
> >> >> >
> >> >> >> You updated the default recipient policy with your change, correct?
> >> >> >>
> >> >> >> What happens when you communicate directly with your Exchange
> >> >> >> server
> >> >> >> from
> >> >> >> inside your network:
> >> >> >>
> >> >> >> telnet servername 25
> >> >> >> helo you.company.com
> >> >> >> mail from:***@company.com
> >> >> >> rcpt to:***@newdomain.com
> >> >> >> data
> >> >> >> This is a test.
> >> >> >> ..
> >> >> >> quit
> >> >> >>
> >> >> >> If you can connect directly to the Exchange server and this is
> >> >> >> successful
> >> >> >> (with the appropriate text substitutions), then something between
> >> >> >> the
> >> >> >> Internet and your Exchange server is rejecting the domain.
> >> >> >> --
> >> >> >> Ed Crowley MVP
> >> >> >> "There are seldom good technological solutions to behavioral
> >> >> >> problems."
> >> >> >> ..
> >> >> >>
> >> >> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
> >> >> >> > Two firms merged, one using SBS 2003 with Exchange.  Using
> >> >> >> > Exchange
> >> >> >> > we
> >> >> >> > want
> >> >> >> > to continue you accept mail from olddomain.com and also accept
> >> >> >> > mail
> >> >> >> > from
> >> >> >> > newdomain.com.  MX records for Olddomain and Newdomain are
> >> >> >> > Identical.
> >> >> >> > User
> >> >> >> > names are constant.  In exchange manager I expanded Recipients –
> >> >> >> > selected
> >> >> >> > Recipients policies – selected E-Mail Addresses tab and entered
> >> >> >> > the
> >> >> >> > new
> >> >> >> > domain name.  Mail sent to the new domain is being returned with
> >> >> >> > the
> >> >> >> > following error message:
> >> >> >> >
> >> >> >> > SMTP error from remote mail server after RCPT
> >> >> >> > TO:<vi***@newdomain.com>:
> >> >> >> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
> >> >> >> >    554 No relaying allowed - psmtp
> >> >> >> >
> >> >> >> > Any insight in how to correct this problem?
> >> >> >> >
> >> >> >> > Thank you
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
>
>

"LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
news:DE84E9CF-4FB3-4F97-A3A6-BA002880C57A@microsoft.com...
> Hello – The problem is resolved.
>
> A long time ago we used Postini to filter out spam.  It was my
> understanding
> that the Postini service was cancelled when we installed spam filters on
> our
> exchange server.  Our ISP never cancelled the service.  When we registered
> our new domain I requested the domain be setup like our old domain.  Since
> the new domain was NOT register with Postini – Postini bounced back the
> emails.  The ISP forwarded the new domain name directly to our server and
> it
> is accepting mail fine.
>
> On a personal note I would like to thank you so much for the time and
> effort
> spent assisting me in this problem.  Your efforts to determine the problem
> was NOT our server were instrumental in resolving the problem.  THANK YOU.
>
>
> "Ed Crowley [MVP]" wrote:
>
>> Exchange is accepting mail for the secondary domain.  Now you can try the
>> second test, do the same thing from the Internet, connecting to the
>> server
>> in the A record referred to by your MX record.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> ..
>>
>> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> news:E6B97F47-5010-4667-8E4F-18A595426CF1@microsoft.com...
>> > Hello and thank you again for your assistance.
>> >
>> > The SBS server domain is Cuddy.local
>> > The SBS Server 2003 running Exchange named ZEUS
>> > The working old SMTP domain is cuddylaw.com
>> > My email address is vi***@cuddylaw.com
>> > The new SMTP domain which is NOT working is cuddymccarthy.com
>> > My new email address which is NOT working is vi***@cuddymccarthy.com
>> >
>> > Below is a copy of the commands and results from your post.
>> >
>> > 220 zeus.Cuddy.local Microsoft ESMTP MAIL Service, Version:
>> > 6.0.3790.3959
>> > ready
>> > at  Thu, 22 Jan 2009 21:55:41 -0700
>> > helo vince.cuddylaw.com
>> > 250 zeus.Cuddy.local Hello [192.168.0.16]
>> > mail from:vi***@cuddylaw.com
>> > 250 2.1.0 vi***@cuddylaw.com....Sender OK
>> > rcpt to:vi***@cuddymccarthy.com
>> > 250 2.1.5 vi***@cuddymccarthy.com
>> > data
>> > 354 Start mail input; end with <CRLF>.<CRLF>
>> > This is a test
>> > .
>> > 250 2.6.0 <ZEUShnHcWhlEqwdD8sM00000d7e@zeus.Cuddy.local> Queued mail
>> > for
>> > deliver
>> > y
>> > ..
>> > 500 5.3.3 Unrecognized command
>> > Quit
>> > 221 2.0.0 zeus.Cuddy.local Service closing transmission channel
>> >
>> >
>> > Thank you again for any assistance you can provide.
>> >
>> >
>> >
>> >
>> >
>> > "Ed Crowley [MVP]" wrote:
>> >
>> >> Enter all of the commands as I typed them except substitute your own
>> >> addresses and domains:
>> >>
>> >> telnet servername 25
>> >> helo you.company.com
>> >> mail from:***@company.com
>> >> rcpt to:***@newdomain.com
>> >> data
>> >> This is a test.
>> >> ..
>> >> quit
>> >>
>> >> The reason you got no response is that you didn't enter a dot (.) on a
>> >> line
>> >> by itself.  That's what <CRLF>.<CRLF> means--CRLF = Carriage Return
>> >> Line
>> >> Feed, or the Enter key when you're using Windows telnet.
>> >>
>> >> Post back everything you got back.  The best way is to copy the text
>> >> content
>> >> of the command window into your reply message.
>> >>
>> >> Still, what you've posted indicates that your server is receiving mail
>> >> for
>> >> newdomain.com, which I kind of suspected because the bounce message
>> >> you
>> >> first posted doesn't look like an Exchange reply.  Do you have any
>> >> other
>> >> SMTP hosts between the Internet and your Exchange server, such as an
>> >> antispam filter, antivirus host, or "smart" firewall that's doing SMTP
>> >> inspection?
>> >>
>> >> If you post the real name of newdomain, I can look to see if it looks
>> >> like
>> >> Exchange is doing the answering.  Or, you're welcome to look up
>> >> newdomain.com's MX record, retrieve the IP addresses of the
>> >> corresponding
>> >> A
>> >> records, and doing your own telnet session from an Internet host to
>> >> each
>> >> of
>> >> newdomain.com's e-mail servers.  You can learn a lot from just the
>> >> initial
>> >> banner--it might tell you that you haven't hit your Exchange server.
>> >> --
>> >> Ed Crowley MVP
>> >> "There are seldom good technological solutions to behavioral
>> >> problems."
>> >> ..
>> >>
>> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in message
>> >> news:C30E36C6-788A-40A7-B21E-ADFF841A9A3C@microsoft.com...
>> >> > The response to the rcpt to:myn***@newdomain.com was
>> >> > 250 2.1.5. myn***@newdomain.com
>> >> > data
>> >> > 354 Start mail input; end with <CRLF>.<CRLF>
>> >> > THIS IS A TEST
>> >> >
>> >> > no response - What is the <CRLG>?
>> >> >
>> >> > thank you for your assistance.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > "Ed Crowley [MVP]" wrote:
>> >> >
>> >> >> The HELO doesn't matter.  It's the response to the rcpt to: that
>> >> >> matters.
>> >> >> --
>> >> >> Ed Crowley MVP
>> >> >> "There are seldom good technological solutions to behavioral
>> >> >> problems."
>> >> >> ..
>> >> >>
>> >> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:BB760FEA-31CD-457C-8F25-815E3F68E6B6@microsoft.com...
>> >> >> > Thank you for the responce.
>> >> >> >
>> >> >> > When I Helo myname.olddomain.com I receive the following
>> >> >> > response:
>> >> >> > 250 servername.domainname.local Hello [ip address]
>> >> >> >
>> >> >> > when I helo myname.newdomain.com I receive the following
>> >> >> > response:
>> >> >> > 501 5.5.4 Invalid Address
>> >> >> >
>> >> >> > I am not sure what this means.
>> >> >> >
>> >> >> > Thank you
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > "Ed Crowley [MVP]" wrote:
>> >> >> >
>> >> >> >> You updated the default recipient policy with your change,
>> >> >> >> correct?
>> >> >> >>
>> >> >> >> What happens when you communicate directly with your Exchange
>> >> >> >> server
>> >> >> >> from
>> >> >> >> inside your network:
>> >> >> >>
>> >> >> >> telnet servername 25
>> >> >> >> helo you.company.com
>> >> >> >> mail from:***@company.com
>> >> >> >> rcpt to:***@newdomain.com
>> >> >> >> data
>> >> >> >> This is a test.
>> >> >> >> ..
>> >> >> >> quit
>> >> >> >>
>> >> >> >> If you can connect directly to the Exchange server and this is
>> >> >> >> successful
>> >> >> >> (with the appropriate text substitutions), then something
>> >> >> >> between
>> >> >> >> the
>> >> >> >> Internet and your Exchange server is rejecting the domain.
>> >> >> >> --
>> >> >> >> Ed Crowley MVP
>> >> >> >> "There are seldom good technological solutions to behavioral
>> >> >> >> problems."
>> >> >> >> ..
>> >> >> >>
>> >> >> >> "LoneWizard" <LoneWiz***@discussions.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:5167B920-AF10-44C0-94E4-DDB36B527B46@microsoft.com...
>> >> >> >> > Two firms merged, one using SBS 2003 with Exchange.  Using
>> >> >> >> > Exchange
>> >> >> >> > we
>> >> >> >> > want
>> >> >> >> > to continue you accept mail from olddomain.com and also accept
>> >> >> >> > mail
>> >> >> >> > from
>> >> >> >> > newdomain.com.  MX records for Olddomain and Newdomain are
>> >> >> >> > Identical.
>> >> >> >> > User
>> >> >> >> > names are constant.  In exchange manager I expanded
>> >> >> >> > Recipients –
>> >> >> >> > selected
>> >> >> >> > Recipients policies – selected E-Mail Addresses tab and
>> >> >> >> > entered
>> >> >> >> > the
>> >> >> >> > new
>> >> >> >> > domain name.  Mail sent to the new domain is being returned
>> >> >> >> > with
>> >> >> >> > the
>> >> >> >> > following error message:
>> >> >> >> >
>> >> >> >> > SMTP error from remote mail server after RCPT
>> >> >> >> > TO:<vi***@newdomain.com>:
>> >> >> >> >    host cuddylaw.com.s8a1.psmtp.com [64.18.7.10]:
>> >> >> >> >    554 No relaying allowed - psmtp
>> >> >> >> >
>> >> >> >> > Any insight in how to correct this problem?
>> >> >> >> >
>> >> >> >> > Thank you
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>