Can't receive mail after upgrading from 2.2rc2 to 2.2 release: Even more information

Thomas Arendsen Hein thomas at intevation.de
Fri Jul 18 09:27:58 CEST 2008


* Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 18:18]:
> so after some more checking I'm quite sure that clamav is the reason for
> the mail error. Even it is started with the /kolab/bin/openpkg rc all
> start, if I check the status it is still not active:
>
> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start
>
> OpenPKG: start: clamav.
>
> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status
>
> OpenPKG: status: clamav.
> clamav_enable="yes"
> clamav_usable="unknown"
> clamav_active="no"
>
> So, how can I make clamav start?

Or rather: why does your correct way of starting clamav fail?

There is /kolab/var/clamav/clamd.log or your could try manually
executing /kolab/bin/clamscan

You might want to try manually updating the virus database:
# su - kolab-r
$ freshclam

> P.s.: Sorry for writing so many mails today...

With this and my other two mails you might be able to get a working
system again, but there is something wrong on your machine or
installation which causes all this.

If this should be used for production I strongly recommend to get
professional support from the Kolab Konsortium (which Intevation is
part of) or at least help from another person or company with some
experience in troubleshooting mail server installations.

See http://www.kolab-konsortium.de/

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner




More information about the users mailing list