Debian 9 new install problem with Postfix

Discussion in 'General' started by tal56, Dec 4, 2017.

  1. tal56

    tal56 Member

    Hi, I just setup a new VPS on Debian 9 and had issues with Postfix connecting to Amavis. I kept getting
    Code:
    Dec  4 01:08:38 server1 postfix/qmgr[8565]: warning: connect to transport private/amavis: Connection refused
    Both Amavis and Postfix seemed to be running fine, so I started comparing my config files to my other servers and notice something strange. On the bottom of /etc/postfix/master.cf on the working server I had a lot of extra config info, but it was not on the new server. Not sure why it was missing at all, however it was not there on the new install, can someone confirm if this code is supposed to be on the bottom of the master.cf file? I copied and pasted it to the new server's master.cf file and it seems to be working fine now, but not sure why it got cut out or if it was supposed to be there to begin with. Here's the missing config stuff I copied :

    Code:
    dovecot   unix  -       n       n       -       -       pipe
      flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop}
    amavis unix - - - - 2 smtp
            -o smtp_data_done_timeout=1200
            -o smtp_send_xforward_command=yes
    
    127.0.0.1:10025 inet 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
    
    
    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
    It was copied at the bottom of master.cf where on the new server mine just ended at :
    Code:
    mailman   unix  -       n       n       -       -       pipe
      flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
      ${nexthop} ${user}
     
    Last edited: Dec 4, 2017
  2. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    the blocks in the master.cf will be added, when the installer detects, that amavis is installed on your server.
     
  3. tal56

    tal56 Member

    hm ok. Should I remove the block I copied over and rerun the installer now that amavis is running properly? Or would running the latest update again and reconfigure services take care of this?

    Or should I just leave the block I copied over? This would be easiest, but I don't want it to be duplicated or cause problems when I do an update. Thanks
     
  4. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    the update will not result in duplicate entries in the master.cf. if you have installed amavis and amavis is running, you should not see anymore warnings in the mail.log and no mails in the queue-
     
  5. tal56

    tal56 Member

    HI Florian, I stopped getting the warnings after i copied that block of config over from my old server, but I was just curious as to why the old server had that block of code and not the new one, and if I'm reading you clearly, it's from the ispconfig install when/if it detects amavis is available. I guess my amavis was not running correctly when I installed Ispconfig.

    I'm just not sure what I should do now to keep the server running correctly, should I just leave the code that I copied in the master.cf file? Or should I remove that block of code and rerun the ispconfig install now that amavis is working. Thanks
     

Share This Page