asked on

X.400 eMail Routing

I have 2 exchange 2003 servers in two sites, in their own routing groups with no mailbox's.
I have resource servers in multipule domains bellow these, with the mailbox's on and all are working ok with SMTP eMail.

My problem is routing eMail received from the x400 connector, I get a message that the sender has a malformed or missing mail attribute, if I have a mailbox on the server with the x400 connector, I dont get this problem, so I know the information is there.

Any idea's

Tony J

I haven't worked with X.400 for some time but you do need to be exceptionally careful that all of the X400 attributes are indeed correct.

For example, I've seen country code set to OO but for one user it was 00. Such an easy to make, but hard to spot, problem.

colinmussett

ASKER

I have been through all the connectors and read several articles, and what I have should work to my mind, but I am still getting NDR's, all other email is routing without any problem, its just x400 messages that give the problem.

Will leave this open for a few more days, but will have to resort to MS support if I dont get anything further.

Tony J

I was thinking about your X.400 email address configuration too.

Realise they should get created automatically but I've seen cases where they don't.

colinmussett

ASKER

I agree, have seen the problem and also resolved that with a delete and re-create the affected account, but this does not resolve this current problem.

For some reason it know the address the message should go to as in the NDR it gives back the correct SMTP address of the account it should have been delivered to, if I send an SMTP message it arrives perfectly, this leads me to think the information is there.

Really at a loss with this now and have to resolve the problem.

Tony J

Could you give me more details from the NDR? What's the error code in it?

colinmussett

ASKER

error code 5.1.7 for recipient rfc822:<smtp address>
cause: the sender has a malformed or missing mail attribute in the Directory Service (DS).

Tony J

Hmmm - does their SMTP mail address actually exist within their AD account?

Also might be worth firing up ADSIEDIT if it appears there and checking their "Mail" attiribute.

colinmussett

ASKER

yes, have been in adsiedit also to make sure that the mail attribute is there, its very confusing

Tony J

Also, don't know if there's anything useful here:

http://technet.microsoft.com/en-us/library/bb124074(EXCHG.65).aspx

Tony J

Also do you have message tracking enabled? That can be a help when X.400 stops playing.

colinmussett

ASKER

yes, I have tracking enable which is why i know the message comming in has the correct information, its just not reading/routing correctly for some reason, its something really silly, getting very stressed with it ....

Tony J

Any chance you could post a screen shot of one of the message tracking logs?

Blank out anything you don't want seen.

I understand your stress levels with this - X.400 is horrible and unfortunately there's little support or information for it these days.

Tried restarting the MTA etc?

Tony J

Has anything changed on your X.400 connectors? Are they configured to use IP or Name of the far end? Assuming you're using IP and X25?

Can the far end IP/Name be pinged/resolved?

Do messages fail in both directions?

colinmussett

ASKER

nothing has changed with the connectors, and the connections have connected routing groups, which all appear to be correct. can ping and telnet to the ports in all dirrections, its a bit of an odd one.

Messages fail inbound only, outbound appears to work fine.

ASKER CERTIFIED SOLUTION

colinmussett

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial