1 Topic by ninofzh (edited by ninofzh 2017-07-15 03:45:19)

  • ninofzh
  • Member
  • Offline
  • Registered: 2017-07-14
  • Posts: 6

Topic: amavisd faild daemon

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: debian 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): apache2
- Manage mail accounts with iRedAdmin-Pro? no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
My server has 3GB of RAM

Jun 25 06:31:42 servercorreo postfix/qmgr[900]: A0C902817B9: from=<zxcx@external.domain>, size=3735, nrcpt=2 (queue active)
Jun 25 06:31:42 servercorreo postfix/qmgr[900]: 3321B2817C1: from=<zxcx@external.domain>, size=133328, nrcpt=2 (queue active)
Jun 25 06:31:42 servercorreo postfix/qmgr[900]: E1B912817E7: from=<root@my.domain>, size=3182, nrcpt=2 (queue active)
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jun 25 06:31:42 servercorreo postfix/smtp[13131]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: A0C902817B9: to=<adsasd@my.domain>, relay=none, delay=139530, delays=139530/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: 3321B2817C1: to=<asdsad@my.domain>, relay=none, delay=145377, delays=145377/0.04/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: 3321B2817C1: to=<asdad@my.domain>, relay=none, delay=145377, delays=145377/0.07/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: E1B912817E7: to=<asdas@my.domain>, relay=none, delay=400, delays=400/0.09/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jun 25 06:31:42 servercorreo postfix/smtp[13129]: E1B912817E7: to=<root@my.domain>, relay=none, delay=400, delays=400/0.13/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Jun 25 06:31:43 servercorreo postfix/smtp[13131]: A0C902817B9: to=<daas@my.domain>, relay=none, delay=139530, delays=139530/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Jun 25 06:33:27 servercorreo postfix/scache[13135]: statistics: start interval Jun 25 06:31:42
Jun 25 06:33:27 servercorreo postfix/scache[13135]: statistics: domain lookup hits=0 miss=1 success=0%
Jun 25 06:36:29 servercorreo postfix/postscreen[13137]: CONNECT from [155.133.82.77]:57734 to [10.80.80.103]:25
Jun 25 06:36:29 servercorreo postfix/dnsblog[13139]: addr 155.133.82.77 listed by domain zen.spamhaus.org as 127.0.0.4
Jun 25 06:36:29 servercorreo postfix/dnsblog[13139]: addr 155.133.82.77 listed by domain zen.spamhaus.org as 127.0.0.11
Jun 25 06:36:29 servercorreo postfix/dnsblog[13138]: addr 155.133.82.77 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 25 06:36:29 servercorreo postfix/postscreen[13137]: PREGREET 11 after 0.25 from [155.133.82.77]:57734: EHLO User\r\n
Jun 25 06:36:29 servercorreo postfix/postscreen[13137]: DNSBL rank 5 for [155.133.82.77]:57734
Jun 25 06:36:29 servercorreo postfix/postscreen[13137]: DISCONNECT [155.133.82.77]:57734

from this point amavisd does not running and the spamassassin does not find rules

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: amavisd faild daemon

ninofzh wrote:

Jun 25 06:31:42 servercorreo postfix/smtp[13129]: E1B912817E7: to=<asdas@my.domain>, relay=none, delay=400, delays=400/0.09/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

Please start Amavisd service.

3 Reply by ninofzh

  • ninofzh
  • Member
  • Offline
  • Registered: 2017-07-14
  • Posts: 6

Re: amavisd faild daemon

Already probe to restart the amavis but it does not restart and also it does not restart the spamassassin because it does not find the rules

4 Reply by ninofzh

  • ninofzh
  • Member
  • Offline
  • Registered: 2017-07-14
  • Posts: 6

Re: amavisd faild daemon

In the network where the mail server is not connected to the internet, can spamassassin the rules without internet? That is, can you update the spamassassin rules offline?

5 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: amavisd faild daemon

ninofzh wrote:

In the network where the mail server is not connected to the internet, can spamassassin the rules without internet? That is, can you update the spamassassin rules offline?

*) Is it possible to use a proxy to access internet?
*) You can try to download SpamAssassin rules from a computer which has internet access, then copy to mail server.

Also, if your mail server doesn't need to connect to internet at all, disable the spam/virus scanning completely:
http://www.iredmail.org/docs/completely … assin.html

6 Reply by ninofzh

  • ninofzh
  • Member
  • Offline
  • Registered: 2017-07-14
  • Posts: 6

Re: amavisd faild daemon

Thanks to your answers solve the problem in iRedMail with spamassassin