SMTP, and X.400 Address and, GAL are not being added to user properties when mailbox created.

When is RUS set to run?  Continuously or on a schedule?

Are the Exchange management tools installed on the computer where you're creating the accounts?

Are you being prompted to create a mailbox for the user during account creation?

RUS runs continuously and I am creating users and mailboxes on the exchange server itself.
I have a feeling its something the previous admin changed that is causing the problem. I am tempted to rerun the exchange install process to see if it fix the problem but don't want to affect the current users an mailboxes.

Have you checked the settings on the recipient policies to make sure that the users you are creating are note being excluded by the LDAP filter?

I wouldn't re-run the Exchange installer except as an absolute last resort, it will probably do more harm than good, and considering all of Exchange's setttings are stored in AD probably won't fix the problem.

Forgot to put this in my last post:

Managing Recipient Policies
http://searchexchange.techtarget.com/originalContent/0,289142,sid43_gci1119797,00.html

Look at the multiple recipient policy section, it talks about the effects of filters and multiple recipient policies.

Yea I agree reinstalling is a last  option. Will create an additional RUS object and see what happens.

Issues for ticket:
When I use ADSI editor and go to the RUS distinguished name and check the properties of the object I don't see attributes like:
msExchDoFullReplication and a lot of msExch attributes are blank
Note selected all options to show mandatory, optional attributes.

Some of the additional steps I have taken in troubleshooting this issue:
RUss troubleshooting.
http://msexchangeteam.com/archive/2004/07/07/175444.aspx
To begin logging the events of interest to the application log, increase logging on the following objects to Maximum on the Exchange server responsible for the domain RUS you've chosen:
        MSExchangeAL\LDAP Operations
        MSExchangeAL\Address List Synchronization
        MSExchangeSA\Proxy Generation (Exchange 2003 only)
Setup monitoring for the above.
Sites with suggested method ot troubleshooting:
http://msexchangeteam.com/archive/2004/07/07/175444.aspx
http://msexchangeteam.com/archive/2004/07/15/184356.aspx
     repadmin /showmeta "<distinguishedName of RUS>" >rusmeta.txt
http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html

Worked with Microsoft ran Exchange baseline
downloaded Exchange best practice Analyzer
http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyzers/default.mspx

Ran Run update service again.
Created test accounts that were populated with SMTP and X400 information
Will test again in the morning with new accounts if sucessful will close this case and keep points
As of now just building notes on case for anyone that may run into this issue in the future.

Hope these notes are helpful to someone, I was sucessfully able to resolve this issues.

Also check the following if you have these problems, was a critical part of the solution.
Use ADSI edit and verify the following permissions
1) Exchange admin group did not have full permissions to this folder CN=Company name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DomainName,DC=com. Give exchange admin group foll control.
2) The RUS service update number was always ahead of number assigned to some client so it would skip those changes. set rus to update every hr temporarly and make changes to see if the uSNChaged is higher than the last update created by RUS u can do this using the RUS troubleshooting to log LDAP, ASL, and Proxy data listed above.  
3) the property value for each client that was not getting stamped was set to not accept update from parent. go into the user accout in AD User and Computer, enable view of advanced features, for each user getting updated verify the security | Advanced  | allow inheritable permissions to propagate is checked. If you see permission errors in the logs this is causing that problem.