• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1025
  • Last Modified:

Exchange 2003 Messages Bouncing

Hi, I am having problems with a Windows 2003 SP2 Server with Exchange 2003 SP2 on it.  It keeps randomly bouncing messages with the following error;

            The e-mail address could not be found.  Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address.  Check the address and try again.
            <Exchangeserver.domainname #5.1.0>

I thought first of all that it might be a problem with the Nickname file on users but replying to the received message sometimes gets this error.  I have turned on Exchange logging and cannot see the message in the Exchange log, I also confirmed with our ISP that they did not see the message go through their mail servers but they did my other 4 messages to that recipient.

The server was originally promo'd in from a Windows 2000 domain and all 2000 servers have now bee removed from the domain.  There is just this Exchange server and another Windows 2003 Std server in the domain, any ideas folks before I raise a case with Bill Gates N Co....

Ta
0
DClayden
Asked:
DClayden
  • 4
  • 3
1 Solution
 
SembeeCommented:
Is this internal or external email?
Do you have recipient filtering enabled?

Simon.
0
 
DClaydenAuthor Commented:
Hiya, we do not have recipient filtering enabled and the bounces can come from both external and internal addresses sent to the Global Address List.

Thanks
0
 
DClaydenAuthor Commented:
Just turned upp all MS EX Logging and now get the following when a message bounces....
Event Type:      Warning
Event Source:      MSExchangeTransport
Event Category:      Exchange Store Driver
Event ID:      327
Date:            16/11/2007
Time:            11:09:25
User:            N/A
Computer:      EXCHANGE
Description:
The following call : EcSaveChangesMessage to the store failed. Error code : -1605. MDB : 34fc9079-aebd-4262-880e-8890c0a2a451. FID : 2-7106. MID : 1-60B410. File : .

For more information, click http://www.microsoft.com/contentredirect.asp.

AND
Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      NDR
Event ID:      3009
Date:            16/11/2007
Time:            11:09:25
User:            N/A
Computer:      EXCHANGE
Description:
A non-delivery report with a status code of 5.1.0 was generated for recipient rfc822;emailaddy@domain.com (Message-ID <061736F1B096E24A9837FED6B818CB4D60B410@exchangeserver.domainname>).    
Cause: This is categorizer failure caused by a bad address.
For more information, click http://www.microsoft.com/contentredirect.asp.  
Solution: Either the recipient address is incorrectly formatted or the categorizer was not able to properly resolve the recipient. Checking the recipient address and re-sending the message is the first step to resolving this error.  
Data:
0000: bb f9 ff ff               »ùÿÿ    

Any ideas?

0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
SembeeCommented:
Have you got journaling enabled?

Simon.
0
 
DClaydenAuthor Commented:
I dont think so.  I have had a look online to see how to tell and I cant see any signs of it.  Do you think an offline defrag will help?  Straighten things out maybe, any other ideas?

Thanks again....
0
 
SembeeCommented:
I would be surprised if an offline defrag would help. That is database maintenance, this is a transport error.

You may want to look at this eventid.net report on the error: http://www.eventid.net/display.asp?eventid=327&eventno=1730&source=MSExchangeTransport&phase=1

It shows a number of possible causes including rules. For rules it could also be event sinks, which are installed by third party tools.

Simon.
0
 
DClaydenAuthor Commented:
Hiya, I have got this sorted today via Microsoft Support.  It took a lot of testing and a 3 hour conversation to get it going!  All it needed in the end was an ISinteg.  All working now though, it seemed the databases had corruptions...

Great!  Thanks for your suggestions though.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now