Re: Email issues with two Exchange SBS2003
- From: Andres A <aardila@xxxxxxxxxxxxx>
- Date: 26 Apr 2007 13:37:35 -0700
My apologies. Yesterday's was my first post and since it did not show
up immediately I thought Google Groups had lost my post. Now I
understand how it works and look forward to using this group more
often :-)
Thanks!
On Apr 25, 11:23 am, "Cris Hanna [SBS-MVP]"
<crisnospamha...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
is there some reason you started a new thread on this?
You started one yesterday and a couple of us responded to this
--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues
"Andres A" <aard...@xxxxxxxxxxxxx> wrote in message
news:1177514148.917779.51780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have an SBS2003 in our home office with Exchange, which handled all
email for the organization. We recently opened a new location and
installed SBS2003, but the owners wanted the same domain
(mycomany.com) for the users on the new location. We placed ShieldMX
as our MX server which is configured to sort and relay email to the
two locations based on a predetermined list of users & their
respective location. This part is working perfectly.
The problem arises when the two locations try to email each other
returning an NDR with 5.1.1 error code "The e-mail account does not
exist at the organization this message was sent to. Check the e-mail
address, or contact the recipient directly to find out the correct
address." Because SBS believes that it is the only server that handles
email for mycompany.com I edited the delivery policy removing the
mycompany.com domain. When I did this, however, the servers would not
accept incoming messages, returning "Failure: 550 5.7.1 Unable to
relay for x...@xxxxxxxxxxxxx" in the SMPT transaction. I went back
and added the domain to the delivery policy, this time unchecking the
"This Exchange organization is responsible for all mail delivery to
this address" but users continued to get the error message.
It was suggested to me to route outbound SMTP traffic through a smart
host, so I got DynDNS' MailHop Outbound. However, upon checking the
tracking logs within Exchange, I see that the message does not get as
far as the SMTP connector. Once it reaches the Categorizer it sends
the NDR to the user.
Any help would be tremendously appreciated! Many thanks in advance :-)- Hide quoted text -
- Show quoted text -
.
- References:
- Email issues with two Exchange SBS2003
- From: Andres A
- Re: Email issues with two Exchange SBS2003
- From: Cris Hanna [SBS-MVP]
- Email issues with two Exchange SBS2003
- Prev by Date: Re: Problem with ISA, I think ...
- Next by Date: Re: Problem with ISA, I think ...
- Previous by thread: Re: Email issues with two Exchange SBS2003
- Next by thread: SP1 fails to install - error Update.inf-Make Sure Cryptograph
- Index(es):
Relevant Pages
|