if you are not dealing with the above error you can ignore these additional instructions

Thanks!

hebrew878 wrote:

mangaan wrote:

You must also re-create some directorys

mkdir /var/spool/amavisd/tmp
mkdir /var/spool/amavisd/db

chown amavis:amavis /var/spool/amavisd/tmp
chown amavis:amavis /var/spool/amavisd/db

re enable postfix amavis content filter comment out in postfix main.cf "content-filter = amavis:[127.0.0.1]:10024"

service start amavisd
service restart postfix

check if amavisd is listening:

netstat -tap |grep amavisd

check you maillog

tail -f /var/log/maillog

For me everything is working again!

Thanks!

thank you very much.

Hi,

Unfortunately after further examine the maillog file there where still errors in my mallog :-((

postfix/qmgr[1219]: warning: connect to transport private/smtp-amavis: No such file or directory

postfix/error[1236]: 3C877BACD: to=<root@xxx.domain.xx>, relay=none, delay=77704, delays=77703/1.4/0/0.17, dsn=4.3.0, status=deferred (mail transport unavailable)

So after some googling I found also a solution for this error

Check these files and change them if you're dealing with the above error

Change this additional lines:

etc/postfix/main.cf

content_filter = amavis:[127.0.0.1]:10024

to this:

content_filter = smtp-amavis:[127.0.0.1]:10024

/etc/postfix/master.cf

-o content_filter=smtp-amavis:[127.0.0.1]:10026

to this:

-o content_filter=smtp-amavis:[127.0.0.1]:10024

/etc/amavisd/amavisd.conf

$inet_socket_port = [10024, 9998];

to this:

$inet_socket_port = [10024];

So far no more errors in the maillog

Thanks!

there is no such problem with my configuration..and amavisd working again as i followed your instruction

mangaan wrote:

ZhangHuangbin wrote:

Try:

# amavisd genrsa /var/lib/dkim/domain.com.pem

You must also re-create some directorys

mkdir /var/spool/amavisd/tmp
mkdir /var/spool/amavisd/db

chown amavis:amavis /var/spool/amavisd/tmp
chown amavis:amavis /var/spool/amavisd/db

re enable postfix amavis content filter comment out in postfix main.cf "content-filter = amavis:[127.0.0.1]:10024"

service start amavisd
service restart postfix

check if amavisd is listening:

netstat -tap |grep amavisd

check you maillog

tail -f /var/log/maillog

For me everything is working again!

Thanks!

thank you very much.

Hi,

Unfortunately after further examine the maillog file there where still errors in my mallog :-((

postfix/qmgr[1219]: warning: connect to transport private/smtp-amavis: No such file or directory

postfix/error[1236]: 3C877BACD: to=<root@xxx.domain.xx>, relay=none, delay=77704, delays=77703/1.4/0/0.17, dsn=4.3.0, status=deferred (mail transport unavailable)

So after some googling I found also a solution for this error

Check these files and change them if you're dealing with the above error

Change this additional lines:

etc/postfix/main.cf

content_filter = amavis:[127.0.0.1]:10024

to this:

content_filter = smtp-amavis:[127.0.0.1]:10024

/etc/postfix/master.cf

-o content_filter=smtp-amavis:[127.0.0.1]:10026

to this:

-o content_filter=smtp-amavis:[127.0.0.1]:10024

/etc/amavisd/amavisd.conf

$inet_socket_port = [10024, 9998];

to this:

$inet_socket_port = [10024];

So far no more errors in the maillog

Thanks!

ZhangHuangbin wrote:

Try:

# amavisd genrsa /var/lib/dkim/domain.com.pem

You must also re-create some directorys

mkdir /var/spool/amavisd/tmp
mkdir /var/spool/amavisd/db

chown amavis:amavis /var/spool/amavisd/tmp
chown amavis:amavis /var/spool/amavisd/db

re enable postfix amavis content filter comment out in postfix main.cf "content-filter = amavis:[127.0.0.1]:10024"

service start amavisd
service restart postfix

check if amavisd is listening:

netstat -tap |grep amavisd

check you maillog

tail -f /var/log/maillog

For me everything is working again!

Thanks!

thank you very much.

Try:

# amavisd genrsa /var/lib/dkim/domain.com.pem

You must also re-create some directorys

mkdir /var/spool/amavisd/tmp
mkdir /var/spool/amavisd/db

chown amavis:amavis /var/spool/amavisd/tmp
chown amavis:amavis /var/spool/amavisd/db

re enable postfix amavis content filter comment out in postfix main.cf "content-filter = amavis:[127.0.0.1]:10024"

service start amavisd
service restart postfix

check if amavisd is listening:

netstat -tap |grep amavisd

check you maillog

tail -f /var/log/maillog

For me everything is working again!

Thanks!

hebrew878 wrote:

how can i make amavisd run again?

- Re-generate a DKIM pem file first, then update your DNS record:
http://code.google.com/p/iredmail/wiki/DNS_DKIM

- Disable amavisd cron job.

No DKIM private keys declared in a config file.

how can i make amavisd run again?

- Re-generate a DKIM pem file first, then update your DNS record:
http://code.google.com/p/iredmail/wiki/DNS_DKIM

- Disable amavisd cron job.

mangaan wrote:

none existent directory?

Not exist? Could you show me output of below commands:

# ls /var/
# ls /var/spool/amavisd/

Sure!

[root@nxtmail2 var]# ls /var/
cache  clamav  db  empty  games  lib  local  lock  log  mail  nis  opt  preserve  run  spool  tmp  vmail  www  yp
[root@nxtmail2 var]# ls /var/spool/amavisd
[root@nxtmail2 var]#

none existent directory?

Not exist? Could you show me output of below commands:

# ls /var/
# ls /var/spool/amavisd/

kislik wrote:

The right line for SL6/CENTOS6/RHEL6 probably is:

1   5   *   *   *   find /var/spool/amavisd/quarantine/ -ctime +15 2>/dev/null | xargs rm -rf {}

No, not /var/spool/amavisd/quarantine/.
Does /var/virusmails/ exist? If yes, please use it instead.

So sorry about this issue, it's a bug in iRedMail-0.8.2, i will release a bugfix release soon.

Hi ZhangHuangbin,

none existent directory?? any other quick fix suggestions
our mailserver is unprotected now

Regards,
Mangaan

The right line for SL6/CENTOS6/RHEL6 probably is:

1   5   *   *   *   find /var/spool/amavisd/quarantine/ -ctime +15 2>/dev/null | xargs rm -rf {}

No, not /var/spool/amavisd/quarantine/.
Does /var/virusmails/ exist? If yes, please use it instead.

So sorry about this issue, it's a bug in iRedMail-0.8.2, i will release a bugfix release soon.

Did you test it with the new cron line?
before I change it on our production server
What about the missed key files is there a possibility to generate them again?

Thanks!
Mangaan