On Wed, Nov 30, 2022 at 05:10:26AM +0000, Sean Hennessey wrote:
> I've been poking at this a bit tonight. I am by no means a postfix expert. In
> the hopes that someone can see an obvious configuration issue, I'm going to
> post what I'm seeing:
>
> In my main.cf;
> smtpd_recipient_restrictions = check_recipient_access
> inline:{
> { gmail.com = class-gmail }
> { yahoo.com = class-yahoo }
> } permit_mynetworks permit_sasl_authenticated defer_unauth_destination
>
> restriction_classes = class-gmail, class-yahoo
s/restriction_classes/smtpd_restriction_classes/
For every parameter you configure, you should check the postconf(5)
documentation to try to understand whether you've at least typed the
name correctly, and whether the setting makes plausible sense.
> class-gmail = check_recipient_access randmap:{filter smtp1:, filter smtp2:}
> class-yahoo = check_recipient_access randmap:{filter smtp1:, filter smtp2:}
>
> postconf complains about this:
> postconf: warning: /etc/postfix/main.cf: unused parameter:
> class-yahoo=check_recipient_access randmap:{filter smtp1:, filter smtp2:}
> postconf: warning: /etc/postfix/main.cf: unused parameter:
> class-gmail=check_recipient_access randmap:{filter smtp1:, filter smtp2:}
> postconf: warning: /etc/postfix/main.cf: unused parameter:
> restriction_classes=class-gmail, class-yahoo
This is a clear sign that the parameter name is not correct.
FWIW, my advice remains to consider the Postgres approach, it is more
correct and scales to more domains. Yes, it requires some effort to set
up a minimal Postgres database.
--
Viktor.
[ My SQL "INSERT" statement incorrectly used double-quotes instead of
single-quotes for string values in the "VALUES" clause. In Postgres
double-quotes as for schema names, and single-quotes are for string
data. Other than that, the recipe seems correct. ]
