"Recipient name not found at destination" for loca

[grahamk]

I have a user who's emails are randomly rejected, with admin receiving this message:

Message could not be delivered to the following recipient:

<Username>@tdl.com.au

because: Recipient name not found at destination
Reporting-MTA: smtp; mail.tdl.com.au
DSN-Gateway: dns; mail.tdl.com.au

Final-Recipient: rfc822;<Username>@tdl.com.au
Action: failed
Status: 5.1.1
x-scalix-Reason-Code: 100


I forward the message to the user, and it works. I have noticed that this has happened at least 5 times in 3 days. I have checked and double checked that the address is correct. Any ideas?

[grahamk]

The sender (another local user) gets a message like this:

----------------------------- ERROR REPORT -----------------------------
Message could not be delivered to the following recipient:

Honor Shelton / scalix/CN=Honor Shelton

because: 'Recipient name not found at destination' [OM 9300]

The message was forwarded to the local Error Manager:
sxadmin / mail/CN=sxadmin
------------------------------------------------------------------------


Looking at this, what I notice is that its sending it to the wrong mailnode. I dont understand the concept of mailnodes very well, but what I can tell you is that I have changed the mailnode for this user.

I had a scalix server for testing, and this was one of the users on the test box. I exported the user data, and when i wanted to import it, i couldnt because the mailnode name was different on the new server. So I added the old mailnode, changed the user to be on that mailnode, imported the data, and changed the mailnode for that user back to the required mailnode name. What have I done wrong, or not done?

[grahamk]

When I change the user to be in the mailnode "scalix" emails are received successfully. It seems that users who are using MAPI cant send when the mailnode is changed to the other mailnode name "mail".

[grahamk]

I had the other mailnode listed still, and for some reason that mailnode was being looked up. I fixed the issue by deleting the other mailnode.

If someone reads this post who has some idea about what might have been going on, I am still interested to know.

Regards

Graham