Page 1 of 1

Problems with Scalix and MWES Version 2.8.1.4

Posted: Wed Sep 10, 2014 8:41 am
by jacs1222
I search logs of mwes i found this:
2014-09-09 15:09:39 [2977954704] Error: SMTPChannel::ConnectToRelay - TCPSocketException - TCPSocket::SelectReadWrite - timed out (30000) while reading from the socket on (x.x.x.x) :: failed with code 110: Connection timed out
2014-09-09 15:09:39 [2977954704] Error: SMTPChannel::ObjectThreadMethod - SMTPChannelException - SMTPChannel::Welcome - No MTA server available

System check result:

Description Result Solution
SMTP Failed The check noticed you are not running MWES on x.x.x.x port 25. Possible reason.
Not enough privileges binding to this port. Please fix this then restart MWES
MTA Failed No MTA found on x.x.x.x port 26. Please fix this then re test
FirstAlert Passed None
Domains Passed None
Admin Account Passed None
License Server Passed None

help me please.. thanks you

Re: Problems with Scalix and MWES Version 2.8.1.4

Posted: Wed Sep 10, 2014 10:07 am
by nick.bolton
You need to change the Scalix port and/or binding port.

The install instructions are here: http://www.firetrust.com/en/products/ma ... structions

Re: Problems with Scalix and MWES Version 2.8.1.4

Posted: Wed Sep 10, 2014 10:15 am
by jacs1222
My configuration
proxy name: ejemplo.com
proxy port : 25

mta..hostname: x.x.x.x
port: 26

webhostname: ejemplo.com
port : 4044

Other error when restart mwesd is:
Starting Mailwasher Enterprise Server: /opt/mwes/mwes.run: /lib/libssl.so.0.9.8: no version information available (required by /opt/mwes/mwes.run)

Re: Problems with Scalix and MWES Version 2.8.1.4

Posted: Wed Sep 10, 2014 11:13 am
by nick.bolton
Can you leave the proxy hostname and mta hostname blank, then they'll bind to all available interfaces, especially if you're using NAT (as the DNS will translate to the outside address, which the server doesnt have).

Have you adjusted the Scalix ports?

For the Libssl error - make sure you have the correct binary - 32 or 64bit.
You can find out by typing: "uname -a" ... it'll show what architecture it is.