550 5.7.1 message content rejected

Discussion in 'ISPConfig 3 Priority Support' started by conductive, Jan 19, 2019.

  1. conductive

    conductive Member HowtoForge Supporter

    When I send an email from gmail to [email protected] the email gets rejected. I have tried 2 different gmail accounts and get the same result.

    The response from the remote server was:
    550 5.7.1 message content rejected​

    Spam and emails from others seem to arrive without a problem. I have over 1000 Regex content filters and do not where to begin looking for the problem.

    Jan 19 13:59:30 mr1 postfix/smtpd[18961]: NOQUEUE: filter: RCPT from mail-wm1-f51.google.com[]: <[email protected]>: Sender address triggers FILTER amavis:[]:10024; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-wm1-f51.google.com>
    Jan 19 13:59:30 mr1 postfix/cleanup[18966]: 87E61486BDF: reject: header From: test gmail <[email protected]> from mail-wm1-f51.google.com[]; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-wm1-f51.google.com>: 5.7.1 message content rejected​

    What is the best way to sort this out?

    Thanks for your help.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    I guess you have 'message content rejected ' in the data field for all filters? In that case, you should change the filters and add a unique code to their reject field, e.g. 'message content rejected. Code 0001' and so on. This will allow you to track which filter triggered the rejection.
  3. conductive

    conductive Member HowtoForge Supporter

    Yes I have been setting all of the global filters to == action = reject
    It seems better than discard since it leaves a bounce for a trail.

    So far I have only used the header and not the body filters. I typically bounce things like viagra, sex. ect. I really do not know what is triggering a vanilla email from gmail. I guess there is something in the gmail header that I am not seeing.

    I am assuming the "unique code" would be entered into the data field of each entry. I was hoping that there was a quicker way as in commenting out lines in /etc/postfix/header_checks. Unfortunately it seems to me that this type of approach does not always update properly in ISPConfig.

    What is the best way to narrow the offending filter?

  4. conductive

    conductive Member HowtoForge Supporter

    I did not find the offending filter but I did fix the problem. I kept deleting lines from header_checks followed by a postfix restart until I fixed the problem. I probably lost 50 or so filters in the process
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    My recommendation is to give the filters individual reject codes in the data field. This will help you in such a case to narrow down which filter caused the rejection.

Share This Page