Scalix Forums

Posted: **Sat Jan 06, 2007 5:46 am**

Hi All,

I have set up my first Scalix 11 Enterprise server. However it will be talking to a V10 server for all outgoing mail and DIRSYNC

I have noticed that the Scalix to Scalix messages from the V11 server to the v10 server fail.

I get this error from the router on the v10 machine whenever a dirsync or mail message is passed to it:

Code: Select all

# omshowlog -p 60 -s router

ERROR                          Service Router(Incoming Trans) 01.06.07 09:15:04
[OM 8307] Incomplete arpa message saved in file
   ~/xport.errs/001kna0


ERROR                          Service Router(Incoming Trans) 01.06.07 09:33:27
[OM 8307] Incomplete arpa message saved in file
   ~/xport.errs/001knl0


ERROR                          Service Router(Incoming Trans) 01.06.07 09:34:08
[OM 8307] Incomplete arpa message saved in file
   ~/xport.errs/001knm0


ERROR                          Service Router(Incoming Trans) 01.06.07 09:35:34
[OM 8307] Incomplete arpa message saved in file
   ~/xport.errs/001kno0

The ~/xport.errs/ files look like this:

Code: Select all

scalix-encoded-message-v2
~to~
>SMINTFC:scalix@malman-scalix.malmaison.com
~from~
>scalix@mallpl-scalix.malmaison.com
~pri~
0
~tf~
M`+QA3@````$```![```$3``````````H``,````````"``0``````0````$`
M```````````"``````````!M=6QT:7!A<G0O86QT97)N871I=F4[8F]U;F1A
M<GD](BTM+2T]7U!A<G1?-U\S,#DR.3DP."XQ,38X,#<V,3,R.#`Q(@````"<
M```S+``````````H```Q,S<Q,#4T-"XR-S$Q-C@P-S8Q,S(X,#(N2F%V84UA
M:6PN<F]O="AA*6UA;&QP;"US8V%L:7@N;6%L;6%I<V]N+F-O;0`Q,S<Q,#4T
M-"XR-S$Q-C@P-S8Q,S(X,#(N2F%V84UA:6PN<F]O="AA*6UA;&QP;"US8V%L
M:7@N;6%L;6%I<V]N+F-O;0`````6```RR``````````H19]M9```````'0``
M*UP`````````*'1E<W0T``!)034```````!K```G$``````````H````````
M``````````````````!L<&QT97-T'1T='4U!3$Q03!T='1T='1T='1T='1T=
M'1T='1T7;'!L=&5S=!<7%QT=;'!L=&5S=$!M86QM86ES;VXN8V]M`````'4`

.............etc

So nothing works currently. I have searched for [OM 8307] in the forum but no mention. What is happening here?? Is V11 not backwardly compatible to V10?

Any advice much appreciated.

Cheers!

C

Posted: **Sun Jan 07, 2007 5:59 am**

OK perhaps I should have RTFM :lol:

.

The relevant section from the release notes:

With the 11.0 release, the interchange character set used for storing ORN's has been changed from T61 to UTF8. This means that when communicating with legacy Scalix machines (Scalix 10.0 and earlier) via the Sendmail Interface (SMINTFC), character set conversion needs to take place.

To achieve interoperability with legacy machines, the SMINTFC routes need to be flagged with a new "Version Number" field, which can be set with a new "-v" option to omaddrt/ommodrt and which can be viewed with the pre-existing "-f" option to omshowrt. When creating a NEW route to a Scalix 1.0.x machine, the version number should be set to "0" or "1". If creating a SendMail interface route to another 11.0 machine, the route version should be set to "2". In multi-server environment, if a machine is upgraded to 11.0, initially all interface routes will remain as version 0. But as soon as it receives a message on one of those routes which it detects to be an 11.0 message, then the Sendmail Interface Service automatically upgrades that route to version 2. This way, as other machines in the network are upgraded, Sendmail interface communication continues to work.

After tagging the routes correctly the errors have stopped and mail is transferring OK .

Cheers

C

Scalix Forums

Scalix 11 to Scalix 10 scalix to scalix communication fails

Scalix 11 to Scalix 10 scalix to scalix communication fails

Solved