Link to home
Start Free TrialLog in
Avatar of msjlogicjunction
msjlogicjunction

asked on

Email's delivered via outlook bounce back for exchange user, non-outlook emails are not bounced back

I'm using SBS 2011, which is the combination of Server 2008 R2 and Exchange 2010.

I simulated what would happen if a user would quit the company then come back soon after.
I removed the user's account via the "Small Business Server Standard 2011 Standard Console", I selected not to remove all email or shared documents.
I pulled the users computer off the domain, verified the user was no longer in Active Directory and deleted the users PC.
I tested the users account using (OWA) Outlook Web Access & Gmail to simulate emails inside & outside the company, all tests were fine.
Here is the problem, the next day, when people use Outlook 2010 to send the user an email, the email instantly bounces back, I log into OWA, and can't replicate their errors.

This is what the bounced back email says
==============
Diagnostic information for administrators:

Generating server: ServerName.DomainName.local

IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=John+20Doe@DomainName.local
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:
===============
I can send direct messages to him via OWA, Gmail, and using my Android (exchange).
I can reply to a message John sends to me in Outlook 2010.
If I (or any user) send a message to John from Outlook it gets returned with the above error message.
I spent about 4 hours looking into this
----
I removed the users account a second time, this time removing all files and email. The above issue still exists.

Any advice would be very helpfull
ASKER CERTIFIED SOLUTION
Avatar of Jamie McKillop
Jamie McKillop
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It's all in the timing :(
Avatar of msjlogicjunction
msjlogicjunction

ASKER

time and the manual removal of the 'bad' account was all that was needed to fix the problem.