1

Topic: Logwatch Clamav Begin Unmatched Entries

==== Required information ====
- iRedMail version: 0.8.1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):MySQL
- Linux/BSD distribution name and version: CentOS6.3
- Related log if you're reporting an issue:
====

what is the meaning of this message?

lstat() failed on: /var/spool/amavisd/tmp/amavis-20130409T234421-01059/parts
lstat() failed on: /var/spool/amavisd/tmp/amavis-20130409T224645-31556/parts
lstat() failed on: /var/spool/amavisd/tmp/amavis-20130409T234421-01059/parts
lstat() failed on: /var/spool/amavisd/tmp/amavis-20130409T224645-31556/parts
lstat() failed on: /var/spool/amavisd/tmp/amavis-20130409T234421-01059/parts


How do you do I do?

2

Re: Logwatch Clamav Begin Unmatched Entries

It should be ok to ignore it.

Amavisd will extract all parts of email file, then invoke SpamAssassin/ClamAV for spam/virus scanning. Looks like something wrong while getting info of some parts.

3

Re: Logwatch Clamav Begin Unmatched Entries

ZhangHuangbin wrote:

It should be ok to ignore it.

Amavisd will extract all parts of email file, then invoke SpamAssassin/ClamAV for spam/virus scanning. Looks like something wrong while getting info of some parts.

Hi, Zhang

Thank you for the advice.
That permission is related to this problem?

/var/spool/amavisd/
/var/spool/amavisd/tmp/

Correct these permissions wonder what?

It has become a appear in Logwatch after the other day, it was also updated clamav relationship in conjunction with the update of php relationship with mysql.