Hallo Stan, * Stan Hoeppner <s...@hardwarefreak.com>: > Stefan Förster put forth on 12/5/2009 5:46 AM: > > * Stan Hoeppner <s...@hardwarefreak.com>: > >> smtpd_helo_required = yes > >> smtpd_helo_restrictions = > >> check_recipient_access hash:/etc/postfix/access > > > > Did you mean "check_helo_access"? > > What does this have to do with the question I asked? How would this > cause the problem I'm inquiring about? Why have two members now > completely missed the problem?
Rejection message: | Dec 4 13:39:15 greer postfix/smtpd[7124]: NOQUEUE: reject: RCPT from | unknown[204.238.179.8]: 450 4.7.1 <mx1.mfn.org>: Helo command rejected: | Host not found; from=<spam-l-boun...@spam-l.com> | to=<s...@hardwarefreak.com> proto=ESMTP helo=<mx1.mfn.org> Obviously triggered by the "reject_unknown_helo_hostname" in: |smtpd_helo_restrictions = | check_recipient_access hash:/etc/postfix/access | reject_non_fqdn_helo_hostname | reject_invalid_helo_hostname | reject_unknown_helo_hostname Whitelist doesn't trigger because you are performing a check for the value of the "RCPT TO" parameter, not the "HELO" or "EHLO". If this isn't what you were looking for I don't have any idea what your question is. Stefan
