postfix not listening on any port

Discussion in 'ISPConfig 3 Priority Support' started by Taleman, Apr 29, 2019.

  1. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I noticed mailq is filling up since Friday, when Debian Jessie got apt-get upgrade and reboot. ISPConfig 3.1.13p1

    I found https://www.howtoforge.com/postfix-amavisd-connect-to-127.0.0.1-10024-connection-refused searching with the error I get in mail.log
    Code:
    dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
    Using that tutorial, I checked with netstat -tap that amavis is running:
    Code:
    # netstat -tap | grep amavis
    tcp6       0      0 localhost:10024         [::]:*                  LISTEN      1206/amavisd-new (m
    tcp6       0      0 localhost:10026         [::]:*                  LISTEN      1206/amavisd-new (m
    But it is running only TCP6, not plain TCP. Don't know why.
    Postfix is not visible in netstat -tap, but is running:
    Code:
    # systemctl status postfix
    ● postfix.service - LSB: Postfix Mail Transport Agent
       Loaded: loaded (/etc/init.d/postfix)
      Drop-In: /run/systemd/generator/postfix.service.d
               └─50-postfix-$mail-transport-agent.conf
       Active: active (running) since ma 2019-04-29 13:34:08 EEST; 18min ago
      Process: 10035 ExecStop=/etc/init.d/postfix stop (code=exited, status=0/SUCCESS)
      Process: 1392 ExecReload=/etc/init.d/postfix reload (code=exited, status=0/SUCCESS)
      Process: 10062 ExecStart=/etc/init.d/postfix start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/postfix.service
               ├─10172 /usr/lib/postfix/master
               ├─10173 pickup -l -t unix -u -c
               ├─10174 qmgr -l -t unix -u
               ├─10176 tlsmgr -l -t unix -u -c
               ├─10505 anvil -l -t unix -u -c
               ├─11226 smtpd -n smtp -t inet -u -c -o stress= -s 2
               └─11233 smtpd -n smtp -t inet -u -c -o stress= -s 2
    
    huhti 29 13:51:00 ispcjessie postfix/smtpd[11233]: disconnect from unknown[103.231.139.146]
    huhti 29 13:51:23 ispcjessie postfix/smtpd[11226]: connect from unknown[103.231.139.146]
    huhti 29 13:51:35 ispcjessie postfix/smtpd[11226]: warning: unknown[103.231.139.146]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
    huhti 29 13:51:35 ispcjessie postfix/smtpd[11226]: disconnect from unknown[103.231.139.146]
    huhti 29 13:52:06 ispcjessie postfix/smtpd[11233]: connect from unknown[103.231.139.127]
    huhti 29 13:52:13 ispcjessie postfix/smtpd[11233]: warning: unknown[103.231.139.127]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
    huhti 29 13:52:13 ispcjessie postfix/smtpd[11233]: disconnect from unknown[103.231.139.127]
    huhti 29 13:52:42 ispcjessie postfix/smtpd[11226]: connect from unknown[103.231.139.127]
    huhti 29 13:52:48 ispcjessie postfix/smtpd[11226]: warning: unknown[103.231.139.127]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
    huhti 29 13:52:49 ispcjessie postfix/smtpd[11226]: disconnect from unknown[103.231.139.127]
    
    What is wrong and how to fix?
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I'm pretty sure I did choose reconfigure services on Friday when updateing ISPConfig. But now I forced reconfigure services, and
    Code:
    # netstat -tap | grep -i amavis
    tcp        0      0 localhost:10024         *:*                     LISTEN      13005/amavisd-new (
    tcp        0      0 localhost:10026         *:*                     LISTEN      13005/amavisd-new (
    tcp6       0      0 localhost:10024         [::]:*                  LISTEN      13005/amavisd-new (
    tcp6       0      0 localhost:10026         [::]:*                  LISTEN      13005/amavisd-new (
    
    Now mailq empties, after postqueue -f. I don't know why it stopped of friday.
     
    Last edited: Apr 29, 2019
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    That should be ok.

    Good that it works again now. Was 10024 connection refused the only error? This would indicate an amavis problem, but netstat showed it was listening, so it's a bit strange why it did not accept the messages.
     
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I could not see any other errors in mail.log. The mails arrived at the host, but were put in deferred queue.
     

Share This Page