several servers

[bfilipe]

Hi all,
I was wondering...
May I install two Scalix Community versions on two different machines?
And in that scenario, may I use 25 Premium accounts on each of them? Is it legal?

Best Regards.
B Filipe

[ScalixSupport]

It is legal but if you're looking to provide a hosting service, you need to request permission from Scalix first.

Cheers

Dave

[bfilipe]

Hi,
First of all thanks for your swift reply, specially on a Saturday.
Second's: The idea is to install two servers in two different locations connected via VPN.
That isn't considered hosting, is it? By hosting you mean suppliyng emails for people which don't belong to my organization, right?
(Sorry if this is a stupid question, but I just want to be sure.)

I've followed this thread http://www.scalix.com/community/viewtop ... rver+route

The directory replications works fine, but i'm unable to send mails from one server to the other.

Best Regards,
B Filipe

[ScalixSupport]

To answer the first question, what you describe would be permitted under the Community Edition license.

Server to Server routing is a feature of Enterprise Edition if you want to maintain the best fidelity but you can still use SMTP between the two machines with Community Edition however you lose MAPI properties because of the Community Edition limitations.

I'd be interested to know how you managed to get dirsync working without the SMINTFC ( Scalix Transport ) route being configured.

Cheers

Dave

[bfilipe]

Wel, like i said i've followed this: http://www.scalix.com/community/viewtop ... rver+route


I got upt to this:

[root@scalix ~]# omshowrt -q all
UNIX internet MIME
UNIX internet,tnef TNEF
LOCAL scalix,dsii
SMINTFC scalix2,dsii scalix@scalix2.test.pt

and this:

SMINTFC internet scalix@scalix.test.pt
SMINTFC internet,* scalix@scalix.test.pt
SMINTFC scalix,dsii scalix@scalix.test.pt
LOCAL scalix2,dsii

Trying to send a message and this appears in the audit.log


unix-in
time 1142186337 Sun Mar 12 17:58:57 2006 +0
originator <1.1@devel.test.pt>
unix-message-id 24451742.1142186336956.JavaMail.root@scalix.test.pt
ua-message-id 24451742.1142186336956.JavaMail.root(a)scalix.test.pt
subject teste
recipient-to 1 2 / scalix2, dsii/CN=1 2 <1.2@devel.test.pt>
recipient-cc 1 1 / scalix, dsii/CN=1 1 <1.1@devel.test.pt>

routing
time 1142186337 Sun Mar 12 17:58:57 2006 +0
type 0 message
priority 0 normal
sensitivity 0 normal
importance 0 normal
created-locally 0
hop-count 1
ua-message-id 24451742.1142186336956.JavaMail.root(a)scalix.test.pt
mta-message-id 24451742.1142186336956.JavaMail.root(a)scalix.test.pt
subject teste
originator 1 1 / scalix, dsii/CN=1 1
part-size 379
part-type 1166 DISTRIBUTION LIST
part-size 5
part-type 1167 TEXT
part-size 278
part-type 2133 HTML
recipient-to 1 2 / scalix2, dsii/CN=1 2
ack-req 0 none
queue SMINTFC:scalix@scalix2.test.pt
recipient-cc 1 1 / scalix, dsii/CN=1 1
ack-req 0 none
queue LOCAL
max-nest-depth 0
message-size 2584
part-count 3
delivered-count 2

SAC is at scalix, scalix2 only has res

Adding a user to scalix2 via scalix results in the user beeing added.
in /opt/scalix-tomcat/logs/scalix-res.log i get this:

2006-03-11 16:44:57,252 DEBUG [CmdExecution.executeCmd:137] ENVIRONMENT: LANG=en_US.UTF-8 OM_CHAR=UTF-8 OMCURRENT=scalix2
2006-03-11 16:44:57,253 DEBUG [CmdExecution.executeCmd:139] COMMAND: /opt/scalix/bin/omaddu -n CN=3 2/G=3/S=2/OU1=scalix2/OU2=
dsii/INTERNET-ADDR="3 2" <3.2@devel.test.pt> --class full 3.2@devel.test.pt -l AMERICAN
2006-03-11 16:44:57,885 DEBUG [RESDispatcherServlet.dumpResponse:285] ---> RES Sending Response XML Document <-----
2006-03-11 16:44:57,886 DEBUG [RESDispatcherServlet.dumpResponse:292] <?xml version="1.0" encoding="UTF-8"?>
<ResResponse>
<Command name="omaddu">
<Status>OK:0</Status>
<Output>
<Line value="omaddu : The user was added successfully"/>
</Output>
</Command>
</ResResponse>

2006-03-11 16:44:57,935 DEBUG [RESDispatcherServlet.dumpRequest:258] ---> RES Incoming Request Headers <----
2006-03-11 16:44:57,936 DEBUG [RESDispatcherServlet.dumpRequest:263] content-type:text/xml; charset=utf-8
2006-03-11 16:44:57,936 DEBUG [RESDispatcherServlet.dumpRequest:263] user-agent:Scalix CAA/Ubermanager 1.0
2006-03-11 16:44:57,937 DEBUG [RESDispatcherServlet.dumpRequest:263] host:scalix2.test.pt
2006-03-11 16:44:57,937 DEBUG [RESDispatcherServlet.dumpRequest:263] accept:text/html, image/gif, image/jpeg, *; q=.2, */*; q=
.2
2006-03-11 16:44:57,937 DEBUG [RESDispatcherServlet.dumpRequest:263] connection:keep-alive
2006-03-11 16:44:57,938 DEBUG [RESDispatcherServlet.dumpRequest:263] content-length:282
2006-03-11 16:44:57,938 DEBUG [RESDispatcherServlet.dumpRequest:266] ---> RES Incoming Request XML Document (Not a secure requ
est, OK) <-----
2006-03-11 16:44:57,939 DEBUG [RESDispatcherServlet.dumpRequest:277] <?xml version="1.0" encoding="UTF-8"?>
<ReqRequest>
<Command instance="scalix2" name="ommodent">
<Parameters enc="false">
<param flag="-n" value="HOST-FQDN=scalix2.test.pt/CNTRY=US"/>
<param flag="-e" value="CN=3 2/G=3/S=2/OU1=scalix2/OU2=dsii"/>
</Parameters>
</Command>
</ReqRequest>


2006-03-11 16:44:57,939 DEBUG [CmdExecution.executeCmd:137] ENVIRONMENT: LANG=en_US.UTF-8 OM_CHAR=UTF-8 OMCURRENT=scalix2
2006-03-11 16:44:57,940 DEBUG [CmdExecution.executeCmd:139] COMMAND: /opt/scalix/bin/ommodent -n HOST-FQDN=scalix2.test.pt
/CNTRY=US -e CN=3 2/G=3/S=2/OU1=scalix2/OU2=dsii
2006-03-11 16:44:58,127 DEBUG [RESDispatcherServlet.dumpResponse:285] ---> RES Sending Response XML Document <-----
2006-03-11 16:44:58,128 DEBUG [RESDispatcherServlet.dumpResponse:292] <?xml version="1.0" encoding="UTF-8"?>
<ResResponse>
<Command name="ommodent">
<Status>OK:0</Status>
<Output>
<Line value="[OM 16961] Modified 1 entry in the Directory"/>
</Output>
</Command>
</ResResponse>


Does this help in any way?

Best Regards,
B Filipe

[ScalixSupport]

What you are seeing is a feature of SAC.

For each RES process that registers with SAC/UberManager, when an entry is added to the directory, skeleton information is added to each of the other servers. The intention in this case is that dirsync will fill in the rest of the details at a later time. Because you don't have dirsync agreements configured, there will be no extra information.

That's not a problem as such if you are happy with the information as it stands there is no need for any of the extra stuff.

Cheers

Dave

[florian]

To be clear, Support for a true multi-server configuration is a Enterprise Edition only feature. This includes

- full fidelity message routing with reliable receipts, etc. and full support for transparent cross-server groupware features such as delegate access, free/busy lookup, etc.
- directory synchronisation using DIRSYNC
- public folder replication using BBSYNC
- centralized administration using Scalix Admin Console

as Dave said, basically if you run two Community Edition servers you can have them communicate via SMTP, but this will basically give you the same functionality as if you were connecting to another company also using Scalix.

cheers,
F.

[bfilipe]

So, this part of the post i've followed is only valid for the enterprise version?

Begin quote

For this to work, you need an import agreement on one side and an export agreement on the other.

On ServerA: omaddds -i -m +DIRSYNC/serverB,mailnode -t "010000 00:00"
On ServerB: omaddds -e -m +DIRSYNC/serverA,mailnode

This sets up the import agreement on serverA and an export agreement on serverB. The -t option specifies when this agreement should come into effect. The format is yymmdd hh:mm.

To do this the other way around:

On ServerA: omaddds -e -m +DIRSYNC/serverB,mailnode
On ServerB: omaddds -i -m +DIRSYNC/serverA,mailnode -t "010000 00:00"

On both machines add the following to /var/opt/scalix/sys/general.cfg:

DS_CUST_SEND_REQ_NOW=TRUE
DS_CUST_MSGQ_TIMEOUT=2

This tells dirsync that it needs to make the update requests as soon as the service is started rather than waiting for a timeout.
You will need to restart the dirsync service but you should also enable auditing so that you can see the messages being transferred between machines:

omconfaud dirsync 15
omoff -d 0 dirsync ; sleep 1; omon dirsync

You can then review the messages in /var/opt/scalix/logs/audit to check that the mail is flowing correctly.

End quote

Best regards,
B Filipe

[florian]

Yes.

This is based on the SMINTFC configuration for routing messages between Scalix servers with full fidelity; SMINTFC and the corresponding service is only available in Scalix Enterprise Edition.

Cheers,
F.