It should - we do it all the time with a half dozen domains -
unfortunately I'm not the exchange guy so I may not have answers on what
else may need to be done.
From: Jeff Brown [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2008 1:14 PM
To: MS-Exchange
So, from the outside, you tried to send an e-mail to your MX record
for mail.primarydomain.com, and you got an "unable to relay" NDR
(bounce) message? Was that address local to that MX record? If yes,
you probably have a spam filter issue.
Note: TXT records are for specifying SPF or SenderID in
Recipient Policy needs to be updated with the new domain info...
On Jan 24, 2008 1:14 PM, Jeff Brown <[EMAIL PROTECTED]> wrote:
> I have a secondary domain setup in my exchange environment, only a couple
> of folks using that domain email.
>
> Got an ndr that says unable to relay for mail.primary
-
From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2008 4:21 PM
To: MS-Exchange Admin Issues
Subject: Re: MX/txt record confusion
So, from the outside, you tried to send an e-mail to your MX record
for mail.primarydomain.com, and you got an "unable to relay&q
using-powershell.aspx>
>
> Thanks...
>
> Regards,
>
> Michael B. Smith
> MCSE/Exchange MVP
> http://TheEssentialExchange.com
>
>
> -Original Message-
> From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 24, 2008 4:21 PM
> To: MS-E
Admin Issues
Subject: Re: MX/txt record confusion
Whoops. Thought I caught that. Done.
On Jan 24, 2008 4:28 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
> Would you please update the link in that article to:
>
>
<http://theessentialexchange.com/blogs/michael/archive/20
An employee who uses an @secondarydomain. address sent a message to someone
and their mail server did the reverse lookup and bounced the message. The
smpt message says, mail.primarydomain.com #5.5.0 smtp;553 sorry, relaying
denied from your location and then has to correct IP address listed at
PROTECTED]
Sent: Thursday, January 24, 2008 2:05 PM
To: MS-Exchange Admin Issues
Subject: Re: MX/txt record confusion
An employee who uses an @secondarydomain. address sent a message to someone
and their mail server did the reverse lookup and bounced the message. The smpt
me
