amavis 10026: Connection refused

Discussion in 'Installation/Configuration' started by SamTzu, Jun 15, 2019.

Tags:
Thread Status:
Not open for further replies.
  1. SamTzu

    SamTzu Active Member

    I did a modified installation of ISPconfig on top of Debian9/Odoo 11 and run in to a problem with Amavis.
    For some reason Postfix thinks that Amavis runs only on port 10026 (and not on 10024) and runs in to a problem.
    Code:
    postfix/smtp[13008]: F259B35F7C: to=<[email protected]>, relay=none, delay=3002, delays=3002/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10026: Connection refused)
    How do I get the port to 10026 up and running?
     
    Last edited: Jun 15, 2019
  2. SamTzu

    SamTzu Active Member

    Code:
    amavis unix - - - - 2 smtp
            -o smtp_data_done_timeout=1200
            -o smtp_send_xforward_command=yes
                    -o smtp_bind_address=
    
    
    127.0.0.1:10025 inet n - n - - smtpd
            -o content_filter=
            -o local_recipient_maps=
            -o relay_recipient_maps=
            -o smtpd_restriction_classes=
            -o smtpd_client_restrictions=
            -o smtpd_helo_restrictions=
            -o smtpd_sender_restrictions=
            -o smtpd_recipient_restrictions=permit_mynetworks,reject
            -o mynetworks=127.0.0.0/8
            -o strict_rfc821_envelopes=yes
            -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
            -o smtp_send_xforward_command=yes
            -o disable_dns_lookups=yes
    
    
    127.0.0.1:10027 inet n - n - - smtpd
            -o content_filter=
            -o local_recipient_maps=
            -o relay_recipient_maps=
            -o smtpd_restriction_classes=
            -o smtpd_client_restrictions=
            -o smtpd_helo_restrictions=
            -o smtpd_sender_restrictions=
            -o smtpd_recipient_restrictions=permit_mynetworks,reject
            -o mynetworks=127.0.0.0/8
            -o strict_rfc821_envelopes=yes
            -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
            -o smtp_send_xforward_command=yes
                -o milter_default_action=accept
            -o milter_macro_daemon_name=ORIGINATING
            -o disable_dns_lookups=yes
    
     
  3. SamTzu

    SamTzu Active Member

    Nothing seems to run on port 10026

    Code:
    tcp        0      0 127.0.0.1:10023         0.0.0.0:*               LISTEN      8459/postgrey --pid
    tcp        0      0 127.0.0.1:10024         0.0.0.0:*               LISTEN      12346/amavisd-new (
    tcp        0      0 127.0.0.1:10025         0.0.0.0:*               LISTEN      11800/master
    tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      527/mysqld
    tcp        0      0 127.0.0.1:10027         0.0.0.0:*               LISTEN      11800/master
     
    Last edited: Jun 15, 2019
  4. SamTzu

    SamTzu Active Member

    Code:
    content_filter = amavis:[127.0.0.1]:10024
     
  5. SamTzu

    SamTzu Active Member

    Running ISPconfig update.php again fixed the problem. Now all Amavis ports are up.
     
    Th0m, ahrasis and zenny like this.
  6. zenny

    zenny Member

    @SamTzu Thanks for an important pointer which helped me the email send/receive issue whining me for days!
     
  7. SamTzu

    SamTzu Active Member

    Ur welcome.
     
  8. grafik

    grafik New Member

    Hi,

    The solution to this problem is the following on Debian systems.
    Code:
     vi  /etc/amavis/conf.d/20-debian_defualts
    and change line
    Code:
    $inet_socket_port = [10024];   to -->  $inet_socket_port = [10024, 10026];
    After that restart Amavis
    Code:
    systemctl restart amavis.service
    Now Amavis should listen on port 10026.
    I run into this problem when I updated Debian 10 to Debian 11 - Bullseye.
    If there is a better, or more healthy solution, please mention it here.

    I hope it helps.
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    @grafik Your issue is not related to the old thread that you re-opened, even if it might sound similar or related on the first look. The issue that Amavis stops working on Debian 11 is a Debian 11 specific issue that does not occur on other distributions or older Debian versions. The reason for the issue on Debioan 11 is that amavis is unable to read its own config files even if owned by the right user and group. The correct solution for your problem can be found in the Debian 11 thread here: https://www.howtoforge.com/community/threads/bullseye-for-ispconfig.87450/page-2#post-427169

    To anyone who reads this thread: do not follow the suggestions posted here on Debian 11. What @grafik posted disables per domain and per mailbox antivirus and anti-spam configurations, so do not use that on an ISPConfig system. Instead, follow the instructions in the post that I posted the link for above.
     
    grafik likes this.
Thread Status:
Not open for further replies.

Share This Page