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

Mail not being delivered to domain user from external senders

We have a user on an Exchange 2003 server that cannot receive external mail.  He is receiving internal mail no problem but when anyone tries to send from outside the organisation they receive a undeliverable report with the text of 'invalid recipient'.

We have tried deleting this users account and then recreating but still the problem occurs.  I have had a look in the event log on the exchange server and we have the following message listed there.

"Received error while processing address space. Examine the connector with this address space and make sure it is legal. If unsure, delete it and recreate via UI. This should ensure it is correct. Address Space = (X500:/o=/ou=kdclondon/*) Hr = c0040385"

Does anyone have any ideas?

Cheers

Neil
0
tower269
Asked:
tower269
  • 10
  • 10
1 Solution
 
daveforsterCommented:
Looks like you have the wrong connector setup in AD.  Check his AD account and make sure that you have an SMTP address for the user.
0
 
tower269Author Commented:
No, I have already checked there he has his correct email address on the email addresses tab and it is set as his primary address.  He has other email aliases setup on here also but these email addresses also fire back a NDR.
0
 
daveforsterCommented:
Is there an old x500 address in the list?  Try removing that.  I'm sure that Exchange 2003 doesn't have the x500 connector and it can't do anthing with it.  Have you migrated from 2000 lately?

Cheers,

Dave
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
tower269Author Commented:
Thanks for your siggestions. No we only have smtp and one X400 email addresses listed and all has been working fine until mid last week.  Nothing changed in network setup or software in quite some time.
0
 
daveforsterCommented:
Check all of your Default Recipient Policies to see if anything there is inheriting an x500 address.  The error above is suggesting that exchange is trying to route the message through a connector that it doesn't know.  Is anyone else having this problem, or just the one user?
0
 
tower269Author Commented:
Affecting one other user but only on an alias address he uses so not so much of a problem at the moment.  Nothing rogue in default recipient policies other than smtp and x400 addresses.  There are some entries for MSMail and CCMail in there but these are unchecked and not going out to the users.  Cannot remove these either.
0
 
daveforsterCommented:
Does the main affected user have any aliases?  Is this his default SMTP address that is the problem?  Can you send external mail to any of the other aliases?
0
 
tower269Author Commented:
Yes he does have some alises setup but we are getting bounceback messages from these also.
0
 
daveforsterCommented:
What exactly is the message that is coming back?  Can you post it here?
0
 
tower269Author Commented:
The message the send receives is below  and the error message from the event log on the exchange machine is in my original post.

Your message did not reach some or all of the intended recipients.

Subject: Test external email
Sent: 23/06/2008 10:09

The following recipient(s) could not be reached:

  iain.moffat@xxxxxxx.co.uk on 23/06/2008 10:10
  There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
  <mainserver.qqqqqqq.local #5.5.0 smtp;550 Invalid recipient <iain.moffat@xxxxxx.co.uk> (#5.1.1)>

I have blanked out there domain name and also our domain name from this message but these are both reporting the correct information.
0
 
daveforsterCommented:
Do you have any hosted mail scanning system?  Or anything that the mail would pass through before it reaches Exchange?
0
 
tower269Author Commented:
yes the mail goes through messagelabs before being delivered to the server.
0
 
daveforsterCommented:
Do you have the sync setup on the messagelabs side of things so that it syncs with AD and if it doesn't find it it will deny the message?  Can you check the MessageLabs side of things?
0
 
daveforsterCommented:
Also is this account in a different OU in AD than the others by any chance?
0
 
tower269Author Commented:
just to add another point we have just tried creating a totally new user and we are getting the same problem with this account.
0
 
daveforsterCommented:
Yeah, this makes me think that messagelabs isn't seeing the account and it's turning the traffic away.
0
 
tower269Author Commented:
as far as we are aware Messagelabs do not sync with our AD they merely filter the mail then forward it onto the IP of our mail server.
0
 
daveforsterCommented:
However, there is a setting that does do this.  Can you check?
0
 
tower269Author Commented:
we are getting messagelabs to check and will let you know what thye say.  Thanks again for your help so far.
0
 
tower269Author Commented:
Thanks for help on this it did turn out to be messagelabs.  Finally got access to the control panel and added email address and problem solved.

Cheers
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

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