On Wed, Sep 18, 2013 at 08:54:50AM -0500, Stan Hoeppner wrote:
> >>> This should have blocked the example message, but did not. Why?
> >> He's using Postfix 2.6.6. The parms in his current config that would
> >> have triggered are for 2.2 or older, thus ignored I assume. He should be
> >> using reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
> >> which should trigger on this.
Stan is wrong, both forms work, the older form is deprecated, but
still works.
> I only work with what I can verify. You didn't provide the contents of
> recipient_no_checks. I try not to guess as that gets you into trouble.
> The only thing verifiably wrong was the syntax of those two restrictions.
Those were fine. You did not read my posts upthread.
> > for other users, the old-syntax was working, now updated
>
> That's strange. Usually when new syntax is introduced the old syntax is
> removed and no longer works. 2.3 -> 2.6 seems a rather long grace
> period. Does the pre 2.3 syntax still work today?
With parameter renames, Postfix introduces backwards compatible defaults:
new_name = $old_name
with restriction class names the old form is left in place. Incompatible
changes are avoided whenever possible.
--
Viktor.
