Mail error after cron job

Discussion in 'General' started by BenM, Jan 4, 2021.

Tags:
  1. BenM

    BenM Member

    Hi,
    Having problems recieving quota warnings for mail en websites. After checking on hard errors i find this.
    Its from the ispconfig cron log. Its a bug in a script that's mailing info.

    Any tips were i can look to drill this down?

    Its just ones a day

    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: fatal: usage: sendmail [options]
    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: fatal: usage: sendmail [options]
    Mon Jan 4 00:14:02 CET 2021 finished server.php.

    Greetings, Ben
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Which version of ISPConfig are you running?
     
  3. BenM

    BenM Member

    ISPConfig 3.2.1
     
  4. BenM

    BenM Member

    seems al my servers have the same problem. must be an update problem
     
  5. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Do you have a conf-custom template in use? It probably needs updated if so, eg to include a From header.
     
  6. BenM

    BenM Member

    No, i dont use custom templates.
    if you are talking about /usr/local/ispconfig/server/conf-custom

    How can i run manaly the nigtly cron job? or just the mail function for this?
     
  7. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    They would be in /usr/local/ispconfig/server/conf-custom/mail/

    Checking all the default templates, the only value used is "{admin_email}" or "{admin_name} <{admin_email}>" - what do you have set in System > Main Config > Mail > Administrator's email?
     
  8. BenM

    BenM Member

    Okay, i dont use any conf-custom files.
    my admin mail is [email protected] name admin. This always worked.

    How can i check if there is someting wrong? i can send mail from the commandline, so it has to be in a script.
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Not necessarily, it can be in your php.ini as well. ISPConfig uses the PHP mail() function by default and not the sendmail command, but it might be that you reconfigured php by using the php.ini in a way that this sendmail error happens.
     
  10. BenM

    BenM Member

    That's strange. Could it be that the error message is generic bij postfix?
    Jan 4 00:13:31 server4 postfix / sendmail [27461]: fatal: usage: sendmail [options]
    Jan 4 00:13:31 server4 postfix / sendmail [27464]: fatal: usage: sendmail [options]
     
  11. BenM

    BenM Member

    test the function of php mail with a script and the results are fine.
    X-Mailer: PHP/7.0.33-0+deb9u10
     
  12. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    How did you run that script? The cli has a different php.ini, and your web could be using a different PHP version
     
  13. BenM

    BenM Member

    i selected a webdomain with fast-cgi and the default php version.
    uploaded a script a run it. tel me how to use the php setting for ispconfig
     
  14. BenM

    BenM Member

    as far as i can tell ispconfig use the same php.ini
     
  15. BenM

    BenM Member

    well i am stuc.
    this report comes from the ispconfig cron.log ....

    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: fatal: usage: sendmail [options]
    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: option requires an argument -- 'f'
    Mon Jan 4 00:13:31 CET 2021 sendmail: fatal: usage: sendmail [options]
     
  16. BenM

    BenM Member

    problem solved, after upgrading to ispconfig version 3.2.2
     
    Th0m likes this.

Share This Page