There is a problem with forwarding messages to new subscribers created beyond a certain date. There have been no known changes to the system with the exception of an upgrade from Unity 3.1.3 to 3.1.4.
Background detail Exchange 2000 SP1, Windows 2000 SP2
The subscribers mailboxes work in every other fashion. eg. receive email messages, add, delete messages.
The forwarding of messages is attempted from the TUI directly to either a name or extension of another user on the local system.
This isn't restricted to just forwarding messages, is it? If you log in as a subscriber and address a new message by name or ID directly does it also fail to find the user? What about finding them by name in the alpha directory? Can you dial their ID from the opening greeting as an outside caller and get their mailbox that way?
When the lookup fails does it just come back and say "There are no matching names" or the like here when you do that? Any errors in the applicaiton event log when such a search fails to turn these users up?
It appears to be restricted to sending messages. The message received is:
recipients email address does not exist" If new user try again in a few minutes.
This user's mailbox is accessable via the outside line thru reception of via direct call to Unity backdoor. Additionally, the alpha directory recognizes the user on a dial by name.
ah... so it's not a problem of finding the user it's a matter of Unity thinking there's something wrong with the destination mailbox and balking on you. Different issue entirely...
ok, is there any errors in the application event log when you attempt to forward or address messages and you get that failure message?
anything unusual about these new users (i.e. are they in a child domain or a container in AD different from the other users)?
There are no errors in the application log associated with the time of testing but there are a couple of errors overall.
MSExchange FBPublish 8197: Error initializing session for virtual machine Unity. The error number is 0x 80070005 make sure Exchange Store is running. This error is frequent and happens every couple of hours.
There is nothing unusual about AD.
I've never seen an Exchange error message that referenced a "virtual machine" - I ran this by my messaging boys and they hadn't seen it either but they dug up these notes on MSDN that sound awfully similiar to what you're seeing:
What SP do you have applied to Exchange?
The best I can suggest is to run through those tech net articles and to try and figure out what's making Exchange unhappy - I have a real strong feeling this is the source of your problem.
Is there a problem with the E2K Recipient Update Service (RUS)? This is responsible for updating the users AD account with an smtp address, once that address is their Unity notices the change and writes it to the SQL database.
Check to see if the AD accounts failing have SMTP address, if they don't try running the E2K RUS. If they do have SMTP address then their is a problem with Unity synching with AD.
He's actually running Exchange 2000 SP2. He opened a TAC case, and I'm currently attempting to access his server.