scsyeg
asked on
Bounce back emails
We created a new email for a user in Exchange and she is intermitentll unable to receive emails. We are getting reports of bouncebacks saying that the account does not exist. At this point we have confirmed:
- email address is active
- can send and receive from some emails
- recreated mailbox
- changed SMTP to a temp account and back
We get the following bounceback from internal senders
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: XXXXEMAILSRVR.XXXX.local
IMCEAEX-_O=XXXX+20EXCHANGE
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
Original message headers:
Received: from XXXXEMAILSRVR.XXXX.local ([fe80::XXXX:XXXX:XXXX:bf5
XXXXEMailSrvr.XXXX.local ([fe80::XXXX:XXXX:XXXX:bf5
14.02.0247.003; Thu, 19 Jun 2014 14:55:35 -0600
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: <<SENDER>@XXXX.ca>
To: "user (<USER>@XXXX.ca)" <<USER>@XXXX.ca>
Subject: FW: RE: Testing
Thread-Topic: RE: Testing
Thread-Index: Ac+LHclKKKtHaJs9T0S31IuDv3
Date: Thu, 19 Jun 2014 14:55:35 -0600
Message-ID: <372C933C3935864DA54B1A577
References: <372C933C3935864DA54B1A577
<6699536307840E449E4A47902
In-Reply-To: <6699536307840E449E4A47902
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <372C933C3935864DA54B1A577
MIME-Version: 1.0
X-Originating-IP: [192.XXX.XXX.115]
- email address is active
- can send and receive from some emails
- recreated mailbox
- changed SMTP to a temp account and back
We get the following bounceback from internal senders
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: XXXXEMAILSRVR.XXXX.local
IMCEAEX-_O=XXXX+20EXCHANGE
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
Original message headers:
Received: from XXXXEMAILSRVR.XXXX.local ([fe80::XXXX:XXXX:XXXX:bf5
XXXXEMailSrvr.XXXX.local ([fe80::XXXX:XXXX:XXXX:bf5
14.02.0247.003; Thu, 19 Jun 2014 14:55:35 -0600
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: <<SENDER>@XXXX.ca>
To: "user (<USER>@XXXX.ca)" <<USER>@XXXX.ca>
Subject: FW: RE: Testing
Thread-Topic: RE: Testing
Thread-Index: Ac+LHclKKKtHaJs9T0S31IuDv3
Date: Thu, 19 Jun 2014 14:55:35 -0600
Message-ID: <372C933C3935864DA54B1A577
References: <372C933C3935864DA54B1A577
<6699536307840E449E4A47902
In-Reply-To: <6699536307840E449E4A47902
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <372C933C3935864DA54B1A577
MIME-Version: 1.0
X-Originating-IP: [192.XXX.XXX.115]
Gareth Gudger
Do you have any anti-spam solutions in place protecting against directory harvest attacks?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Outlook may be using bad cached settings. To turn Cached Exchange Mode off:
On the Tools menu, clickAccount Settings.
On the E-mail tab, click the Exchange account, and then click Change.
Under Microsoft Exchange server, clear the Use Cached Exchange Mode check box.
Exit and restart Office Outlook 2007.
You can also refer to the below article to troubleshoot this issue:
http://www.msexchange.org/tutorials/Understanding-LegacyExchangeDN.html
On the Tools menu, clickAccount Settings.
On the E-mail tab, click the Exchange account, and then click Change.
Under Microsoft Exchange server, clear the Use Cached Exchange Mode check box.
Exit and restart Office Outlook 2007.
You can also refer to the below article to troubleshoot this issue:
http://www.msexchange.org/tutorials/Understanding-LegacyExchangeDN.html
I think Gareth has it nailed.
Make sure the people who are emailing her are not using a stored mail address for her. have each person (including the person that got you that bounce back) type the address out manually.
If outlook cache mode is on it may not be updating the address book properly and therefore is holding an old address. so if some people are getting bounce backs and others are not check to see if they are in cache mode.. make sure you pick only from the gal. and before you send make sure that the address outlook shows is the current address you have for this user
Should get it solved nice and quick :)
Make sure the people who are emailing her are not using a stored mail address for her. have each person (including the person that got you that bounce back) type the address out manually.
If outlook cache mode is on it may not be updating the address book properly and therefore is holding an old address. so if some people are getting bounce backs and others are not check to see if they are in cache mode.. make sure you pick only from the gal. and before you send make sure that the address outlook shows is the current address you have for this user
Should get it solved nice and quick :)
Its almost impossible to clear the entry from cache for all users or cannot think of communicating to all users to select the user from address book. You can convert this email address and add it as X500 address and it will be resolved.
/O=XXXX EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIP
1. Open Exchange Management Console and select User mailbox properties.
2. Go to Email Addresses tab and click Add->Custom Address.
3. Under Email Address, paste the address given above and Email Type should be X500.
Users dont have to select it from the address book and the problem will be solved.
/O=XXXX EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIP
1. Open Exchange Management Console and select User mailbox properties.
2. Go to Email Addresses tab and click Add->Custom Address.
3. Under Email Address, paste the address given above and Email Type should be X500.
Users dont have to select it from the address book and the problem will be solved.
ASKER
To answer your questions
- They do have an external SPAM Filter - this is not the error message that comes up from the SPAM filter
- Issue is with internal senders
- didn't clear from suggested contacts, but had one of the users reply to a message I sent (which goes through) The sender having the issues got a bounceback, I did not, this would bypass the suggested contacts no?
- Going to every user (150 of them) to disable cached mode/clear suggested contacts isn't feasible
For this step:
2. Edit the properties of the user to match the one specified under "IMCEAEX-_O=XXXX+20EXCHANG
Where in the users properties am I making this change?
I will also have the user try OWA and I have added the email account as suggested by Rajitha14 and am testing now
- They do have an external SPAM Filter - this is not the error message that comes up from the SPAM filter
- Issue is with internal senders
- didn't clear from suggested contacts, but had one of the users reply to a message I sent (which goes through) The sender having the issues got a bounceback, I did not, this would bypass the suggested contacts no?
- Going to every user (150 of them) to disable cached mode/clear suggested contacts isn't feasible
For this step:
2. Edit the properties of the user to match the one specified under "IMCEAEX-_O=XXXX+20EXCHANG
Where in the users properties am I making this change?
I will also have the user try OWA and I have added the email account as suggested by Rajitha14 and am testing now
ASKER
Update:
- OWA worked with no issues,
- adding the mail account as per Rajitha14 and restarting Outlook did not work (added "/O=XXXX EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIP
- clearing the email address from the Suggested Contacts seemed to work.
I am not sure where to make the changes that Rod is suggesting.
- OWA worked with no issues,
- adding the mail account as per Rajitha14 and restarting Outlook did not work (added "/O=XXXX EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIP
- clearing the email address from the Suggested Contacts seemed to work.
I am not sure where to make the changes that Rod is suggesting.
<User> must be replaced with the user name in your delivery failure. The email address type must be X500 and not the <USER> as X500
To do this, open the recipient in Exchange Management Console, go to the E-Mail Address tab, click on the drop-down next to "Add" and choose "Custom Address".
Enter /O=XXXX EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIP
Where <USER> will be the PREVIOUS user alias. For example, if the previous user was rodrigo.prazeres@contoso.c
If this was a deleted user, Is the deleted user still under the disconnected mailbox section of EMC?
Enter /O=XXXX EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIP
Where <USER> will be the PREVIOUS user alias. For example, if the previous user was rodrigo.prazeres@contoso.c
If this was a deleted user, Is the deleted user still under the disconnected mailbox section of EMC?
ASKER
This ended up being the fix. I needed to get some more outside help to change the settings for the old mailbox, but this did resolve it. Thank you
I have a similar issue. The email address in question works when the user sends it to her. The user also added the email in question to a group and when she sends to that group it gets bounced back every time.
The user has removed and added the email address to the group a few times and it doesn't fixed it. I asked her if she could remake the group but she does not want to do that because of the number of people in the group. any ideas on what I can do. It is only happening with this one user and only in one group. Other than that the email in question works fine.
The user has removed and added the email address to the group a few times and it doesn't fixed it. I asked her if she could remake the group but she does not want to do that because of the number of people in the group. any ideas on what I can do. It is only happening with this one user and only in one group. Other than that the email in question works fine.