Hello!
The documentation patch seems to suggest that there are potential futures in which the parameter also restricts non-SMTP message ingres, or even delivery after alias expansion for addresses not listed in the table.
Well, based on previous messages on this thread, I thought this was indeed a possibility. I’m not saying I think it should be done, but Wietse did say:
There is nothing that prevents local_recipient_maps from being used elsewhere. The need to do so just hasn't come up.
which opens the possibility.So I chose a wording that should make clear to users that they cannot rely on local_recipient_maps to be ignored by non-SMTP inputs, and therefore that they should make sure the lookups specified in this setting include all locally deliverable recipients. Essentially, I said:
Whether this setting applies to non-SMTP inputs is unspecified, don’t rely on either way.
Of course, it can be decided that local_recipient_maps not applying to anything else than smtpd is now a documented feature. This would mean a configuration where some local users cannot receive mails from the Internet is now supported (although I guess this can already be done with filters) but also that changing this behavior would now be a breaking change, requiring a major version bump and proper warning.
I’m totally fine with that, and can even provide a new patch to document this. It’s just in my opinion, such a decision must be carefully weighted before it is taken.
Regards, -- Étienne Miret https://etienne.miret.io/
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
