"No Proxy for Recipient" Outlook message

It looks like it is trying to use a x.400 address.

I the address is in your global address book. Open up your exch admin, open up the properties for that receipient. Check their e-mail address. Make sure that their default e-mail adress is a smtp address.

It looks like their default address is a x.400 address, which is why you are getting this error.

then try this...

Microsoft Exchange Server, version 5.5

--------------------------------------------------------------------------------

SYMPTOMS
An event similar to the following may be logged in the application event log:

Event ID:3150
Source: MSExchangeMTA
Type: Warning
Category: X.400 Service
Description:
An internal MTA error occurred. Object 00000000 failed integrity verification. DB Attribute: 0. OM attribute: 0. Entity Name: /o=Site/ou=Server/cn=Configuration/cn=Connections/cn=Internet Mail Connector (SERVERNAME). [XAPI GATEWAY 30 1 130 (14).
The incoming message is lost and the sender does not receive a non-delivery report (NDR).

CAUSE
This issue can occur if the Internet Mail Service builds an invalid X.400 message. The message is invalid because the MTS Identifier (MTS-ID) is missing the global domain identifier; only the local string identifier is present.

This can occur if the X.400 address of the administrator mailbox for the Internet Mail Service is comprised of uppercase characters, for example:

C=US; A=ADMD; P=PRMD; S=Administrator
The Internet Mail Service can only process the "c=," "a=," and "p=" if they are lowercase characters.

RESOLUTION
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, please see the following article in the Microsoft Knowledge Base:

Q191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

WORKAROUNDTo work around this issue, edit the E-mail Addresses raw property of the administrator mailbox for the Internet Mail Service, and change the "C=," "A=," and "P=" in the X.400 address to "c=," "a=," and "p=."

STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

The only other thing I would try (since you opened up the exch admin in raw mode and verified the values)

would be to 1, go ahead and recreate the x.400 address in the admins mailbox for the IMS.

2. Delete the contact out of the OAB, create the contact in the GAB with the correct smtp address.

Try sending to that address.

My point being, is that it is in the x.400 address somewhere. There is no way around that truth.

I did come across some odd "ghost" behavior of exchange whereit orphaned a recipient. I was forced to create a new recipient with a new name and same smtp adress. This may be along those same lines. Try creating a new contact in the OAB with a different name but with the same smtp address.