Page 1 of 1

Scalix 11.3 - no route configured for the recipient address

Posted: Wed Jan 30, 2008 7:27 am
by steves
We moved upgraded from Scalix 10.x to 11.3, used ombackup/omrestore to get the data out of the mailboxes.

We have a problem sending emails internally, to our own domain users.

We can send emails to external domains not a problems, even receiving emails from external domains not a problem.

May be I have missed something.

Use use Centos 5, sendmail, Mailscanner (similar setup to the previous one we had)

Any directions?

Thanks in advance

Steve

Re: Scalix 11.3 - no route configured for the recipient addr

Posted: Wed Jan 30, 2008 10:15 am
by les
steves wrote:We moved upgraded from Scalix 10.x to 11.3, used ombackup/omrestore to get the data out of the mailboxes.

We have a problem sending emails internally, to our own domain users.

We can send emails to external domains not a problems, even receiving emails from external domains not a problem.

May be I have missed something.

Use use Centos 5, sendmail, Mailscanner (similar setup to the previous one we had)

Any directions?

Thanks in advance

Steve


Looks like your mailnode has changed.

In 10 it was like mail,domain, based on the server hostname. In 11 its now only based on mail.

Changing mailnodes has implications for internal delivery.

The following post shows how to reset the mailnode and what else is necessary.

viewtopic.php?t=7286&highlight=route+configured+recipient+address

Posted: Wed Jan 30, 2008 11:08 am
by Valerion
Also, be careful of type-down addresses on the client, as well as forwarding/replying to existing mail if you changed your mailnode. The information could be captured there as well.

Posted: Wed Jan 30, 2008 4:54 pm
by les
Valerion wrote:Also, be careful of type-down addresses on the client, as well as forwarding/replying to existing mail if you changed your mailnode. The information could be captured there as well.


Definitely. Replying to old mail when the mailnode changes will not be successful. You then need to implement a different SR_RESOLVE_MASK in general.cfg.
The docs explain that setting and if you search the forums you should find plenty of info on that parameter.