Deleted User/Email still in memory
Hi,
We use to host a domain mail on a serverA. Now that domain mail is hosted on ServerB. Both are running Exchange 2007.
If i try to send mail from DomainA to DomainB it still get a delivery failure report that it is trying to send to serverA
i have removed the EmailAddresspolicies and Accepted domains from serverA.
Why will the deleted mailbox be stuck somewhere? And moreimportantlywhere?
October 27th, 2009 5:12pm
How the mailflow is happening? do you have connector in between?Vinod
|CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2009 6:17pm
Hey Dear,What we understood from this is - both server have the mailbox and if the user who is having mailbox on server A, Whlie sending the mail to the user"s who is having mailbox on server B is not able get mails, Here you must need a connector between one to another, For better explaination please share the delivery notice failure message.Cheers,
Know more about Messaging :-)
October 27th, 2009 10:22pm
Issue description: Exchange 2007 has been installed in the domain a and domain b, both domains stay in the same forest. Now, the mail flow has failed from domain a to domain b, am I understand correctly?
Check info:
1. Please describe more about AD/exchange topology
2. Quote: removed the Email Address policies and Accepted domains from serverA
You have removed accepted domain entry of serverA (DomainA) from domainBs exchange 2007 server? Why?
3. Quote: Why will the deleted mailbox be stuck somewhere
Didnt you mentioned about the mail flow issue before? Why talking about deleted mailboxes now? Please describe more details about the issue
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2009 6:55am
Hi, this one is quite hard to explain.
The message i get is that the mailbox does not exciston serverA. That is correct. is does not excist on server a bacause i move it to serverB. It is a separate domain and all the mail for that domain must goto serverB. A separe server. The only thing that is the same is that it is located in the same network.
I dont have a connector between the two server's. Is this required. I only have one outgoing connector for all my mail.
James: i removed the excepting for the email policy's because serverA should not except the emails anymore? is that not right?
Mention about it before: First time i have this issues. Had issues before but that has been sorted. The mailbox is not really stuck but if i type in userb@domainb.co.za it auto populates the field with his username. if you double click on it you can see that it is trying to send to userA@domainA.co.za.
Error msg:
Delivery has failed to these recipients or distribution lists:
Michele Hornsby The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: SVVDAC001.dac.local
IMCEAEX-_O=DAC+20SYSTEMS_OU=First+20Administrative+20Group_cn=Recipients_cn=MicheleH@dac.co.za #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Original message headers:
Received: from SVVDAC001.dac.local ([fe80::a4dc:f918:c5e:5527]) by SVVDAC001.dac.local ([fe80::a4dc:f918:c5e:5527%10]) with mapi; Tue, 27 Oct 2009 17:27:30 +0200 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: Danie Claassen <Daniec@dac.co.za> To: Michele Hornsby <IMCEAEX-_O=DAC+20SYSTEMS_OU=First+20Administrative+20Group_cn=Recipients_cn=MicheleH@dac.co.za> Date: Tue, 27 Oct 2009 17:27:29 +0200 Subject: test Thread-Topic: test Thread-Index: AcpXGf73rB499jqjTj6Dqdcgt3Ub2A== Message-ID: <9CFCE48E838A204D88D67F326F04BDAF206244A99C@SVVDAC001.dac.local> Accept-Language: en-US, en-ZA Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: <9CFCE48E838A204D88D67F326F04BDAF206244A99C@SVVDAC001.dac.local> MIME-Version: 1.0
October 28th, 2009 8:31am
Quote: serverA should not except the emails anymore
So, serverA has been decommissioned? Theres only one exchange 2007 on the serverB?
Please see my post in this thread, enable the email policy on the problematic mailboxes, apply the policy, and verify if the correct SMTP address has been generated in the proxyAddress attribute. Then, test the issue again
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2009 9:14am
Ok, will have a look at that now.
No, serverA and ServerB is running exchange.
ServerA is the exchange for Dac.local and serverB is the exchange for Wappoint.local.
Wappoint.local was hosted on serverA but has now moved to serverB with it's own Exchange running.
I alsonoticedthat we get the same error message (5.1.1)when sending mail to a certain support user. That user use to be a distribution group. We deleted the group and created it as a user. If we send mail to it from a external account it works but not if we try to send to it inside dac.local...
i think this is related, Going to look at the other thread now. Thanks
October 28th, 2009 10:42am
Hi James.
Where do i find theproxyAddress
The CMDlet do i just run under the exchange management shell.
Prob stupid question but what do i need to edit in the cmdlet or do i run it as is?
Get-MailContact -OrganizationalUnit OU=Internal,OU=Contacts,OU=Microsoft Exchange Objects,DC=b-f,DC=net | Where {$_.EmailAddressPolicyEnabled -eq $False} | Set-MailContact -EmailAddressPolicyEnabled $True
The problem looks like it the the globaladdresslist that do not update.
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2009 4:09pm
For the proxyAddress attribute, you can verify it from ADSI Editor
a. Launch ADSI Editor
b. In the Default naming context container, locate the problematic AD user object entry, right-click it, select Properties
c. Then, you can check the proxyAddress attribute in the Attribute Editor tab
As for the cmdlet, we will need to run if the EmailAddressPolicyEnabled parameter had been set to false. So, please verify the setting by using the cmdlet below
Get-Mailbox ProblematicMailboxName |Fl EmailAddressPolicyEnabled
October 30th, 2009 4:50am
Hi,
Not sure now if it was that that fixed it but it is working now.
Ill keep a eye on it and if it happens again i will try your solution James.
Thanks!!
Free Windows Admin Tool Kit Click here and download it now
November 2nd, 2009 10:08am