trath
asked on
Exchange 2007 - Users can send email outside but not internally
I installed a new exchange 2007 domain and they can email outside their company but anyone on the inside they cannot send email to. The message just gets kiked back to them saying "This recipient e-mail address was not found in the recipient e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the recipient e-mail address and try resending this message, or provide the following diagnostic text to your system administrator"
Diagnostic information for administrators:
Generating server: ortho1.siortho.local
IMCEAEX-_O=ORGANIZATION_OU =ORTHO_CN= RECIPIENTS _CN=PERSON NEL_CN=RBA RR@siortho .local
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou nd; not found ##
Original message headers:
Received: from ortho1.siortho.local ([10.22.1.15]) by ortho1.siortho.local
([10.22.1.15]) with mapi; Mon, 13 Aug 2007 11:15:14 -0600
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
To: "', Dr. Rolandooo'"
<IMCEAEX-_O=ORGANIZATION_O U=ORTHO_CN =RECIPIENT S_CN=PERSO NNEL_CN=re cipientsna me@theirdo main.local >
Date: Mon, 13 Aug 2007 11:15:13 -0600
Subject: test 2
Thread-Topic: test 2
Thread-Index: AcfdzYLNnttZo8RaQpuxi9r7v8 OsPw==
Message-ID: <983D2594A1460744A342FA621 91F625F049 7862E@orth o1.siortho .local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <983D2594A1460744A342FA621 91F625F049 7862E@orth o1.siortho .local>
MIME-Version: 1.0
Diagnostic information for administrators:
Generating server: ortho1.siortho.local
IMCEAEX-_O=ORGANIZATION_OU
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
Original message headers:
Received: from ortho1.siortho.local ([10.22.1.15]) by ortho1.siortho.local
([10.22.1.15]) with mapi; Mon, 13 Aug 2007 11:15:14 -0600
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
To: "', Dr. Rolandooo'"
<IMCEAEX-_O=ORGANIZATION_O
Date: Mon, 13 Aug 2007 11:15:13 -0600
Subject: test 2
Thread-Topic: test 2
Thread-Index: AcfdzYLNnttZo8RaQpuxi9r7v8
Message-ID: <983D2594A1460744A342FA621
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <983D2594A1460744A342FA621
MIME-Version: 1.0
Are we talking about brand new messages created by selecting recipients from the GAL or are we talking about replies or accepting auto completed addresses in Outlook?
ASKER
Exactly.
Exactly what? You need to tell us which one of the two options is applicable.
ASKER
It is excactly what you said it was. When they choose someone from the GAL they get the erro, if they send to somone outside their company name@domain.com it will go through. This is for new mail
What I meant originally was whether it was a Compose or a Reply operation that was causing the problem. I already knew that external=good, internal=bad. I was trying to get at what the users were doing internally (i.e. Compose a new or reply).
1) Can you send internal messages with OWA?
2) Can you send internal messages with Outlook if you completely recreate the domain? (I'm making an assumption that you're perhaps just modifying the user profile)
1) Can you send internal messages with OWA?
2) Can you send internal messages with Outlook if you completely recreate the domain? (I'm making an assumption that you're perhaps just modifying the user profile)
Lets check your EAP and accepeted domain...
Do you have them setup correct?
What is your setup like,
I see in the error
@theirdomain.local>
@siortho.local <-- authoratative?
Do you have them setup correct?
What is your setup like,
I see in the error
@theirdomain.local>
@siortho.local <-- authoratative?
ASKER
Yes accepted domains is athoratative, EAP has a policy in it for both doamin.local and domain.com
both domain.local and domain.com are authoratative?
ASKER
Yes they both are.
did the user have a cached entry in OL? have you tried to send from OWA
Whilst we're at it you should delete the domain.local. Since you have a domain.com in there as well the .local serves no purpose. (To pre-empt what's going through your mind: No, there is no such thing as an Internal and an External address in Exchange)
ASKER
Could it be that I need to add a MX record into their DNS?
intenal routing will not use an MX.... has this ever worked? what changed?
ASKER
Yes it did work it used to be exchange 5.5 but did a new install of Exchange 2007
have you run an exbpa to see if you get any errors?
ASKER
Yes and it ran clean.
Can you answer the questions I posted about OWA and a new profile. I'm pretty certain you'll be able to work ok with OWA. Check it out and advise....
ASKER
I am trying to get them to try it using OWA now. It is luch time here so things are moving slowly.
ok, now we may be getting some where..... So you have Exchange 5.5 how did you get the users moved to 2007?
Are you users sending from contacts? I know you said GAL above...
Also, have you tried from OWA vs Outlook?
Are you users sending from contacts? I know you said GAL above...
Also, have you tried from OWA vs Outlook?
ASKER
I havent verified from the receiver yet, but i didnt get a bounceback error. It look like it worked through OWA.
ASKER
They didnt want to pay to have that done by a consulting company specializing in exchange, so they paid me a lesser consultant to do it. So we did not migrate any user info off the old server. This is a new clean install
Yes Atig. That's where I was going at 6:37. I'll lay odds that they're either replying (no can do due to LegacyExchangeDN) or composing new mails and selecting users who were added from the GAL into the Contacts folder (again with the old LegacyExchangeDN ploy)
Price of a pint says that OWA will be fine, although the testing with a brand new profile won't be a good test because the users will follow old practices and select users from where they are familiar. You and I are probably on the same page in that the users aren't actually using the GAL.
Price of a pint says that OWA will be fine, although the testing with a brand new profile won't be a good test because the users will follow old practices and select users from where they are familiar. You and I are probably on the same page in that the users aren't actually using the GAL.
Almost sounds like a user tried to send from a contact..
yep..... I am on the same page as CZDCT thinking its related to the legacydn and cache in the clients OL or a contact.
when the new message was being typed did it autocomplete?
when the new message was being typed did it autocomplete?
ASKER
They are typing in their name and OL completes it, also it still will not work if they type in the address in internet form name@doamin.com for internal adressing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So if that is the case unchecking the cache mode in OL would resolve it. Correct
Yeah, you need to have the users tear all of the contacts out of their Outlook Contacts.
Create a test user that cannot possibly exist in the users contacts folders and wait for it to get an SMTP address. Then use Outlook to put a message in with the SMTP address and send it. Bets are that it will get delivered ok.
Create a test user that cannot possibly exist in the users contacts folders and wait for it to get an SMTP address. Then use Outlook to put a message in with the SMTP address and send it. Bets are that it will get delivered ok.
ASKER
How exactly do i delete the cache?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So if they go into mail in control panel and delete the outlook contacts profile, will that do it?
ASKER
OK Ill try it
another way to save this would be copy the exchange legacy dn over
you can do a csv export from 5.5 and use EMS in import to 2007 and that will fix this problem and make life simple.
If they only have a few users you can hand jam it
you can do a csv export from 5.5 and use EMS in import to 2007 and that will fix this problem and make life simple.
If they only have a few users you can hand jam it
Yeah, but let's not run before we can walk here. The poster needs to read up on why it's not working and why LegacyExchangeDN matters. I wouldn't be too happy about guiding Trath through that little job right now.
This is a good case in point on You Pay For What You Get in terms of consultancy costs. Mind you, there are enough gaping exceptions to that rule :-)
This is a good case in point on You Pay For What You Get in terms of consultancy costs. Mind you, there are enough gaping exceptions to that rule :-)
ASKER
Hold on there, LOL! I realize that most people that post here are little more than CD swappers, I upgraded their 2000 domain to 2003, and installed Exchange 2007 to the point that it is almost working, all by myself with no real guidance. I think that make me a little bit more elite than the average "consultant".
Oh, and I habe not heard back from them yet on if that fixed the issue or not.
Oh, and I habe not heard back from them yet on if that fixed the issue or not.
If you're ok with it then sure, go ahead. It's not the most difficult thing in AD to do but you need to take care.
:)