Scalix and spamassassin

[anneb]

Hi,

I'm installing Scalix 11.2 on Suse Enterprise server v10 and everything works great till I try to set up the Spamassassin module.

Working through the howto's and documentation I get right to the point of

chkconfig --add spamassassin
chkconfig --add spamass-milter
chkconfig --level 345 spamassassin on
chkconfig --level 345 spamass-milter on
/etc/init.d/spamassassin start
/etc/init.d/spamass-milter start

and all I get is

unknown service on both spam-milter and spamassin.

I have followed the documentation to the letter and get no errors at all through the install till i get to that point

and normally what happens then is Scalix locks up and won't send or receive mail.

I'm very new to Linux so if anyone could give me a clue as to what is going wrong I would be obliged

Happy New Year

[kanderson]

From the top of my head, those look like Red Hat instructions. Suse (If I recall correctly) calls them different names.

At a command line, type:

/etc/init.d/spam and then hit tab twice. This will auto complete the name with what you're after. You'll likely find that rather than spamassassin, it's called spamd or something like that. They're the same thing.

Kev.

[anneb]

Hi Kev,

Thanks for replying, I have given up on trying to get spam filtering to work,

I now use fetchmail to get mail from my isp and my mail goes through their spam filters

I may have another try at getting the spam fitering running on Scalix but not in the near future

[pinnks]

I too have been trying to get spamassassin working with Scalix 11.

I seem to bomb out when trying to compile/configure the milter. It suggests that I do not have libmilter. I thi=oght this was part of sendmail-devel, which is installed.

Anyone have any ideas or a step-by-step guide to installing Spamassassin with Sclix on SUSE 10.2?

Thanks

[kanderson]

PLEASE don't use Suse 10.2 in production. PLEASE.

You will be frustrated with it when it's time to upgrade, and you'll blame Scalix rather than accepting that this is NOT meant for production.

For the Scalix dev team, Please give some thought to dropping support COMPLETELY (as in, no binaries offered) for anything other than SLES, RH and CentOS.

People who want Suse can choose SLES.
People who want RH can choose RH.
People who don't want to pay for an OS can choose Cent, and pick either Gnone or KDE as they see fit.

In regards to your question, I think you'll find most people of the experienced people here are not running Scalix on Suse 10.2 (or any Suse other than SLES) because instructions for 10.2 will be invalid as soon as the next Scalix release comes out, supporting 10.3, but not 10.2. Because it's a constantly moving target, it's really hard to document for.

Having said that, as a general rule, the instructions do work.

Kev.

[mikevl]

Hi

I would agree with Kevin. The number of disasters and support issues and time that is wasted on FC and OpenSUSE is enormous.

RHEL
SLES
or
CentOS are good

Mike