clamassassin - centos 4.3

Discussion in 'Installation/Configuration' started by wcsmith, Aug 16, 2006.

  1. porjo

    porjo New Member

    There is no output - just comes back to the prompt.

    I can see in /tmp 109 empty files beginning with the prefix sess_ and owned by root. What are these for?
     
  2. afmachado

    afmachado New Member

    [SOLVED] clamscan error 50

    Hello,
    I am using a Xen VM with ispconfig.
    This kind of clamscan error 50 happened at one of my machines because of misconfigurations of ownership and permissions of mail and user directories and files.
    Spamassassin and ClamAV are very strict about its directories and files permissions and ownership.

    First, corrected the ownership and permissions of /var/mail/username mail file (postfix):
    Code:
    chown boletins:mail /var/mail/boletins
    chmod 664 /var/mail/boletins
    
    WEIRD: You should configure permissions this way. THEN postfix will automatically modify for stricter security when the first msg arrive to the inbox.
    I do not know, yet, why it did not work when using the final permissions at first place... The log files showed that postfix reconfigured the files this way ... :confused:


    Code:
    [email protected]:~$ ls -la /var/mail
    
    -rw-------   1 boletins     mail     556 2007-11-19 14:02 boletins
    
    
    Then, you should verify the user directories and files for ownership and permissions.

    Code:
    localhost:~# cd /var/www/web1/user/boletins
    localhost:/var/www/web1/user/boletins# chmod 755 /var/www/web1/user/boletins
    localhost:/var/www/web1/user/boletins# pwd
    /var/www/web1/user/boletins
    localhost:/var/www/web1/user/boletins# chmod 700 .spamassassin
    localhost:/var/www/web1/user/boletins# chmod 600 .spamassassin/*
    localhost:/var/www/web1/user/boletins# chmod -R 700 .pyzor
    localhost:/var/www/web1/user/boletins# chmod 600 .pyzor/*
    localhost:/var/www/web1/user/boletins# chmod -R 775 web
    localhost:/var/www/web1/user/boletins# chmod 755 .razor
    localhost:/var/www/web1/user/boletins# chmod 644 .razor/*
    localhost:/var/www/web1/user/boletins# chmod 600 .razor/identity-*
    localhost:/var/www/web1/user/boletins# chmod 600 Sent
    chmod: cannot access `Sent': No such file or directory
    localhost:/var/www/web1/user/boletins# chmod 600 Trash
    localhost:/var/www/web1/user/boletins# chmod 600 .bash_history
    localhost:/var/www/web1/user/boletins# chmod 644 .mailboxlist
    localhost:/var/www/web1/user/boletins# ls -la
    total 148
    drwxr-xr-x   6 boletins web1  4096 Nov 18 16:23 .
    drwxrwxrwx  10 suporte  web1  4096 Nov 19 06:39 ..
    -rw-r--r--   1 root     root   103 Nov 19 08:14 .antivirus.rc
    -rw-r--r--   1 root     root   782 Nov 19 08:14 .autoresponder.rc
    -rw-------   1 boletins web1    95 Mar  3  2007 .bash_history
    -rw-------   1 boletins web1    24 Nov 19 08:14 .forward
    -rw-r--r--   1 root     root 67866 Nov 19 08:14 .html-trap.rc
    -rw-r--r--   1 root     root  3889 Nov 19 08:14 .local-rules.rc
    -rw-r--r--   1 boletins web1     6 Feb 24  2007 .mailboxlist
    -rw-r--r--   1 root     root   204 Nov 19 08:14 .mailsize.rc
    -rw-r--r--   1 root     root   451 Nov 19 08:14 .procmailrc
    drwx------   2 boletins web1  4096 Dec 29  2006 .pyzor
    -rw-r--r--   1 root     root   656 Nov 19 08:14 .quota.rc
    drwxr-xr-x   2 boletins web1  4096 Nov 16 18:02 .razor
    drwx------   2 boletins web1  4096 Nov 18 03:48 .spamassassin
    -rw-r--r--   1 root     root  1144 Nov 19 08:14 .spamassassin.rc
    -rw-r--r--   1 root     root  2433 Nov 19 08:14 .user_prefs
    -rw-r--r--   1 root     root    32 Nov 19 08:14 .vacation.msg
    -rw-------   1 boletins web1   556 Nov 18 16:11 Trash
    drwxrwxr-x   2 boletins web1  4096 Dec 21  2006 web
    
    
    
    localhost:/var/www/web1/user/boletins# invoke-rc.d postfix restart
    Stopping mail transport agent: Postfix.
    Starting mail transport agent: Postfix.
    localhost:/var/www/web1/user/boletins# invoke-rc.d ispconfig_server restart
    Shutting down ISPConfig system...
    /root/ispconfig/httpd/bin/apachectl stop: httpd stopped
    ISPConfig system stopped!
    Starting ISPConfig system...
    /root/ispconfig/httpd/bin/apachectl startssl: httpd started
    ISPConfig system is now up and running!
    
    
    
    
    I hope this helps someone. :)
    You should compare and adapt these permissions and ownership with a fresh new user created at your machine.

    Regards.
    Andre Felipe Machado
    linux blog :cool:
    http://www.techforce.com.br
     
    Last edited: Nov 20, 2007

Share This Page