freedomit-glow-buttons-ubuntu


open-source goodness for your desktop

shared code | shared efforts | shared principles | zero purchase cost
talk to Freedom IT today about getting ubuntu onto YOUR computer

It’s free
and open source

Shared code, shared efforts, shared principles. No cost.

KB - Scalix Email Server

Scalix Recovery After an Abrupt Stop

Some tips for dealing with Scalix after an abrupt stop to the server (eg: power outage, hardware failure, etc):

  • CDA Server remains (becomes) in Aborted state:
(Thanks to www.cyberpro.com.au for the original tip)

From time to time the CDA Server in scalix can crash and fall into an aborted state. I have seen this happen a lot after power interruptions. If you are using ommaint then you will be notified about it.

What does the CDA Server do?

The Client Directory Access (CDA) Server builds access tables for Scalix directories to provide sorted lists of directory entries.
The Outlook client used with Scalix requires sorted entries in the Address Books. This enables “typedown” functionality when selecting addresses in the interface. The CDA Server is used to provide the sorted lists of directory entries.

How to resolve:

"service scalix status" shows "CDA Server Aborted"

# omoff cda

# rm /var/opt/scalix/??/s/sys/omcda.lock

where "??" is the instance name (normally created from the first and last letter of the hostname of the server).

# omon cda

# service scalix status (should show started)

(You shouldn't need to but in some cases you may need to force the state of the cda server to off before starting again. Use "omreset -o off cda")

  • Run omscan
I find it beneficial to always run the following after the scalix server has not been shutdown cleanly:
# omscan -AAfvx

Scalix 11.x + Postfix + Postgrey on Centos 4.x/5.x

I've managed to get postfix running in front of Scalix, allowing me to do greylisting.Here's the procedure I followed (after 2 or 3 days of attempts!):
This assumes you currently have Scalix 11 + sendmail working (as standard) on Centos 4/5. I also have amavis running as per HowTos/Amavisd

* Before starting backup your working  /etc/amavisd.conf to /etc/amavisd.conf-SENDMAIL and /var/opt/scalix/mi/s/sys/smtpd.cfg to /var/opt/scalix/mi/s/sys/smtpd.cfg-SENDMAIL. Copy these over to filename-POSTFIX respectively. Then create links to the real filenames. That way if anything goes awry it's real easy to swap back: just change the symbolic link to point to the appropriate file.


  • Postfix Integration: Follow the HowTos/Complete Postfix Wiki article. There are a couple of clarifications/changes I made to this howto:

Upgrading Scalix 10/FC4 to 11/FC5

I found this quote on the Scalix Community Forums from Florian, a Scalix 'product guy', regarding upgrading Scalix 10/FC4 to Scalix 11/FC5. I assume it would be necessary if going to CENTOS 5 (original link):

"This sounds like you didn't uninstall Scalix 10 before you upgraded your Fedora. You should have done that as the binaries are not compatible. You'll now need to manually remove the RPMs using the RPM --erase command. I would then also suggest that you clear out all scalix* subdirectories under /opt and /etc/opt - all you would leave intact would be /var/opt/scalix which contains your actual data.


If you then run the scalix installer and perform a typical installation, it should detect your pre-existing data and offer to preserve it.

Please have a backup before you do all this - but assume you made one before upgrading the OS anyway. "

Hmmmmmm.

Impossible?
impossible is just a big word thrown around by small people who find it easier to live in a world they've been given, than to explore the power they have to change it.

impossible is not a fact.
it's an opinion.
impossible is not a declaration.
it's a dare.
impossible is potential.
impossible is temporary.
impossible is nothing.