SMTP Error 451

Discussion in 'General' started by mrbronz, Mar 22, 2021.

  1. mrbronz

    mrbronz Member HowtoForge Supporter

    I have just updated my servers to v3.2.3 and the email has stopped working with an error

    SMTP Error (451): Failed to add recipient "[email protected]" (4.3.5 <localhost[:::1] Client host rejected: Server configuration error)

    When I was upgrading I stuck to the default settings and passwords I had previously used when first installed

    the webserver is working fine so I can log in to the RoundCube web email but I am not receiving and not able to send an email.

    From what I have read this is a local issue but cant see why its an error at all
     
  2. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Your post is not related to the HOWTO tutorials, I moved it to an ISPConfig forum.

    Presumably mail was working before updating? See the read before posting items related to problems after updating and to sending email.
     
  3. mrbronz

    mrbronz Member HowtoForge Supporter

    Hi there

    Thank you for the reply

    Yes, I can confirm the email was working before the update.

    I can confirm that
    Code:
    $config['smtp_server'] = 'localhost';
    $config['smtp_port'] = 25;
    I can confirm that the update script reconfigured my services as per default settings I have also ran it with the --force switch

    There are no custom config templates in:
    Code:
    /usr/local/ispconfig/server/conf-custom
    I have also confirmed that email is not being sent from the account I logged into the account with i.e. local mailsystem

    edit:
    So error in the mail.log file
     
    Last edited: Mar 22, 2021
  4. mrbronz

    mrbronz Member HowtoForge Supporter

    I've just checked in the mail.err log and 3 entries

    Code:
    Mar 22 12:10:40 martin amavis[23894]: (23894-07) (!!)AV: ALL VIRUS SCANNERS FAILED
    Mar 22 15:54:14 martin dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF
    Mar 22 15:54:14 martin dovecot: auth: Error: net_connect_unix(anvil-auth-penalty) failed: Connection refused
    I'm guessing this is not good?
     
  5. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    I'm not familiar with that one, try searching for causes of that error.
     
  6. mrbronz

    mrbronz Member HowtoForge Supporter

    I've looked but the results are not making much sense to me.
     
  7. mrbronz

    mrbronz Member HowtoForge Supporter

    All my emails have stopped con anyone point me to a solution please?
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    I have not seen this error yet on an ISPConfig system. Try to re-run the update, use reconfigure services = yes during update and ensure that you are correctly logged in as root user (e.g. use 'su -' and not just 'su' on Debian 10).
     
  9. mrbronz

    mrbronz Member HowtoForge Supporter

    Thanks Till

    But have already tried that with no success
    I am logged in as root as that is how I have always had my servers configured
     
  10. mrbronz

    mrbronz Member HowtoForge Supporter

    So how come it stopped after I ran the ISPC3 update?

    in the /etc/postfix/mysql-virtual_transports.cf

    the host is set to
    Code:
    hosts = 2.0.0.1
    is this correct surly it should be 127.0.0.1 for local host
     
    Last edited: Mar 22, 2021
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    A typo in your /etc/hosts file maybe?
     
  12. mrbronz

    mrbronz Member HowtoForge Supporter

    Yes it was but that is not the problem

    Thank you
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    That's the reason for the wrong IP in the config file (and probably many more config files) you complained about. After fixing the hosts file, re-run the update.
     
  14. mrbronz

    mrbronz Member HowtoForge Supporter

    Outstanding Till,
    I would never have thought such a simple error would course that problem.

    The error was when I updated my hosts file to accommodate my nameservers.
    And obviously, this error never showed up until I updated/upgraded ISPconfig

    Many thanks again...
     

Share This Page