No route configured for address

[propagandhi]

I have deployed a third node in our scalix network, and when I send mail to users on that node from other mailnodes, I get this:

Message could not be delivered to the following recipient:

user@domain.com

because: No route configured for the recipient address
Reporting-MTA: smtp; mailnode1.domain.com
DSN-Gateway: dns; mailnode1.domain.com

Final-Recipient: rfc822;user@domain.com
Action: failed
Status: 5.4.4
x-scalix-Reason-Code: 101

Could somebody please offer some advice, I really need to sort this out asap.

[Valerion]

You are not giving a lot of info here.

1) Are your routes set up correctly?
2) Are your dirsync set up correctly?
3) Can you send to the TEST user on the remote machine?
4) Are your sendmail configuration (mailertable) correct?
5) What does your audit log and sendmail logfile say?

[deyjvu]

Reopening this topic as I am seeing exactly this error on a new server I just setup and imported the accounts from an old server.

Current is 11.4.3 and the old version was 11.2.0.

The new server is on a new mailnode and new server name but the IA address has stayed the same. Only a few emails have this problem (thank goodness) but they appear to be the messages going from one local user to another local user. The error is in the non-delivery message in sxadmin's mailbox:

Reporting-MTA: smtp; mail2.domain.com
DSN-Gateway: dns; mail2.domain.com

Final-Recipient: rfc822; johnsmith@domain.com
Action: failed
Status: 5.4.4
x-scalix-Reason-Code: 101

I suspect it is the sending users address book in Outlook may have an old entry for this local user and that they need to update the entry in their address book to the new one? I am adding this for others reference. Hope it helps you. Once I have this confirmed I'll update.

[Valerion]

Maybe it's an old typedown in the Outlook "To/Cc/Bcc" field.

[les]

I may be completely wrong here but it sort of sounds like this might apply in your situation......

changing mailnodes and reimporting old mail means you cant reply to old mail messages unless you change the following in general.cfg and restart scalix (Note: the comments below are my own wording so i don't have to remember everything off the top of my head). I had a similar situation a couple of years back where i had to reinstall a scalix server, and, before i knew it was a bad idea, i decided to change the mailnode from "mail,domain" to "mail". After sxmboximp'ing all old mail user complained they couldn't reply to old mail messages. Changing the address resolve mask to not match the mailnode did the trick.
I've never had to use this again (never made the same mistake of changing mailnodes ;} ), but i always keep it in my template.

# Change address lookup tables
# Needed if old mail is imported from a different mailnode
# and users want to reply to old mail internally successfully.
# This will do lookups based on surname, givenname, middle initials and generation qualifier only.
# It wont try to match the mailnode.
# Not normally needed.
# p.s. its a bad idea to change mailnodes
# SR_RESOLVE_MASK=S/G/I/Q

Hope that helps.

[deyjvu]

Thanks Les, that sure fits my situation. I'll give it a try and yes I had changed mailnodes.

Cheers,