Installation of scalix successful and now?

[Pool4Sky]

Hi @ all,

I've installed the scalix server on a opensuse 10.1 distribution successful.
Now I would like configure sendmail and fetchmail but I don't know.
Please can I get a configurationguide, which let it be work correct?
Thank you.

greetings Pool4Sky
P.S. Sorry for my bad english.

[florian]

please search the forum for fetchmail. There will be plenty of information available on configuration.

Florian.

[Pool4Sky]

@florian,

thank you for your answer.
Now the scalix server, fetchamil and sendmail works fine. I wrote a little tutorial with the steps, but in german.
Later..
I've installed mailwasher. It seem to work. How can I test it?

greetings Pool4Sky

[florian]

are you sure you don't find any test spam messages that you can send to yourself anywhere? usually, just writing a short message with lots of funny characters in the subject and some words describing little blue pills and other such things in the body of the message will do....

Florian.

[Pool4Sky]

@florian

i tested the mailwasher with an email with the follow subject:

@@@ hier kannst du X kaufen und dich mit mir treffen @@@

The statistic of the mailserver is:

System Statistics

Show statistics for all messages
Show statistics for messages received in the past month
Show statistics for messages received between and

Statistics for all messages
Number of emails received 0
Number of emails from globally whitelisted addresses 0
Number of emails from personally whitelisted addresses 0
Number of emails marked with a header field 0 (0.0%)
Number of emails quarantined without notification 0 (0.0%)
Number of emails quarantined, and the sender notified 0 (0.0%)

Reason for filtering
Of those 0 filtered emails:
0 (0.0%) were from addresses on the global address blacklist
0 (0.0%) were from addresses on personal address blacklists
0 (0.0%) were listed by real-time blackhole list services
0 (0.0%) were listed by the FirstAlert! service
0 (0.0%) were guessed to be junk by statistical analysis

FirstAlert! category breakdown:

Junk Mail Submissions
Number of messages submitted by users as junk messages: 0
Number of invalid junk message submissions: 0
Number of junk messages uploaded to FirstAlert!: 0

Day-by-day statistics
Download day-by-day statistics in CSV format
Download day-by-day statistics in XML format

I think, my mailwasher doesn't work correct. Is it right?
What can I do?

greetings Pool4Sky

P.S. I configured it with this howto: http://www.scalix.com/wiki/index.php?ti ... Mailwasher

[florian]

it looks a little bit like it - yes.

now, i have never used mailwasher with scalix and the how-to has been written by member of the scalix community. i think there is a long thread on mailwasher here on the forum. I would suggest that you add to that thread and look for help there - the mailwasher fans will be much faster in figuring out what's going on here.

One thing maybe, how did you send that mail? mailwasher will only get to see things that come in externally.....

Florian.

[Pool4Sky]

@florian

I use mailwasher because I think that is an alternative spam program.
I installed scalix on a OpenSUSE 10.1 distribution and I read that the spanassassin doesn't work with it. I read the scalix pdf and tried to download spamass-milter and sendmail-devel.
But these rpms are only for fedora core.
I'm looking for a scalix spam program which works internally and/or externally. Can you help me?

greetings Pool4Sky

[florian]

spamass-milter is only one way to get going with SpamAssassin. Another great method is actually to use Amavis (i.e. amavisd-new) - which is also available for SuSE. See the contributed How-To at http://www.scalix.com/wiki/index.php?ti ... os/Amavisd for details.

Otherwise, you would need to download the sourcecode for spamass-milter and compile it yourself on your SUSE box - which shouldn't be too difficult either.

Please note that because all these methods will make the anti-spam tools plugin to sendmail, this will only affect incoming and outgoing internet mail. internal mail can be made subject to virus scanning using the Service Routers Anti-Virus interface, however, they cannot be run through sendmail for anti-spam integration.

We currently have no plans to change this architecture, mainly because internal spam is currently no real concern for our typical customers.

Florian.

[Pool4Sky]

Hi @ all,

just I delete mailwasher and installed amavisd-milter like howto.
By step >>sudo chkconfig --add amavisd-milter<< I get an error: "script amavisd-milter is broken: missing end of LSB comment" What does it mean? I read this file but I don't see a comment error. What should I do now?

However, in the howto at this point:

>>cd /usr/local/src && tar xvzf /path/to/amavisd-milter-1.x.x.tar.gz
cd amavisd-milter-1.x.x
./configure && make && sudo make install<<

My output of terminal is:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for ranlib... ranlib
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for an ANSI C99-conforming __func__... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking whether to check for GCC pthread/shared inconsistencies... yes
checking whether -pthread is sufficient with -shared... yes
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for mode_t... yes
checking for size_t... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for d_namlen in struct dirent... checking for ANSI C header files... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct tm.tm_zone... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for sys/types.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for sys/stat.h... (cached) yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking sysexits.h usability... yes
checking sysexits.h presence... yes
checking for sysexits.h... yes
checking for unistd.h... (cached) yes
checking for sem_init in -lrt... yes
checking if POSIX semaphores are working... yes
checking fts.h usability... yes
checking fts.h presence... yes
checking for fts.h... yes
checking for arc4random... no
checking for daemon... yes
checking for fts_open... yes
checking for mkdtemp... yes
checking for strlcpy... no
checking for inet_ntop... yes
checking for inet_aton... yes
checking for socket... yes
checking for gethostbyname... yes
checking if ld accepts --rpath... yes
checking for sendmail install directory... default
checking libmilter/mfapi.h usability... yes
checking libmilter/mfapi.h presence... yes
checking for libmilter/mfapi.h... yes
checking for smfi_main in -lmilter... yes
checking if files required by libmilter are present... yes
checking for smfi_insheader... yes
checking for smfi_opensocket... yes
checking for smfi_progress... yes
checking for smfi_quarantine... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for EILSEQ... yes
checking for EOVERFLOW... yes
checking whether AF_INET6 is declared... yes
checking whether INET6_ADDRSTRLEN is declared... yes
checking for struct sockaddr_in6... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating amavisd-milter/Makefile
config.status: creating compat/Makefile
config.status: creating autoconf
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
p4s-emailsvr-suse-oss101:/usr/local/src/amavisd-milter-1.2.1 # make && make install
make all-recursive
make[1]: Entering directory `/usr/local/src/amavisd-milter-1.2.1'
Making all in compat
make[2]: Entering directory `/usr/local/src/amavisd-milter-1.2.1/compat'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1/compat'
Making all in amavisd-milter
make[2]: Entering directory `/usr/local/src/amavisd-milter-1.2.1/amavisd-milter'make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1/amavisd-milter'
make[2]: Entering directory `/usr/local/src/amavisd-milter-1.2.1'
make[2]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1'
make[1]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1'
Making install in compat
make[1]: Entering directory `/usr/local/src/amavisd-milter-1.2.1/compat'
make[2]: Entering directory `/usr/local/src/amavisd-milter-1.2.1/compat'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1/compat'
make[1]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1/compat'
Making install in amavisd-milter
make[1]: Entering directory `/usr/local/src/amavisd-milter-1.2.1/amavisd-milter'make[2]: Entering directory `/usr/local/src/amavisd-milter-1.2.1/amavisd-milter'test -z "/usr/local/sbin" || mkdir -p -- "/usr/local/sbin"
/usr/bin/install -c 'amavisd-milter' '/usr/local/sbin/amavisd-milter'
test -z "/usr/local/man/man8" || mkdir -p -- "/usr/local/man/man8"
/usr/bin/install -c -m 644 './amavisd-milter.8' '/usr/local/man/man8/amavisd-milter.8'
make[2]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1/amavisd-milter'
make[1]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1/amavisd-milter'
make[1]: Entering directory `/usr/local/src/amavisd-milter-1.2.1'
make[2]: Entering directory `/usr/local/src/amavisd-milter-1.2.1'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1'
make[1]: Leaving directory `/usr/local/src/amavisd-milter-1.2.1'

It doesn't created a directory like /var/amavis and I can't find this directory.
In the /etc/sysconfig/amavisd-milter file exits a variable like AMAVISD_HOME="/var/amavis" but I've not this directory.
Where can I find this? And should it resolve my problem?

greetings Pool4Sky

[kanderson]

Mailwasher will need to receive a hundred messages and you'll have to categorize them before it starts actually filtering email.

After the mail has been received, you'll need to categorize it as well.

Kev.