Download raw body.
smtpd: be more relaxed in table usage
February 7, 2024 1:42 PM, "Philipp" <philipp@bureaucracy.de> wrote:
> Helo
>
> Currently you can't use a map on some places in smtpd.conf. Therefor
> you need sometimes hold the content in a list and a map. For example
> you want some recipients handle by a different action then others:
>
> table specialvirt { a@example.com=alice@example.com, b@example.com=bob@example.com }
> table specialrcpt { a@example.com, b@example.com }
>
> action specialaction forward-only virtual <specialvirt>
> action default mbox virtual <virtual>
>
> match for rcpt-to <specialrcpt> for domain "example.com" action specialaction
> match for domain "example.com" action default
>
> It would be simpler when you could use the specialvirt table also for
> the rcpt-to rule. There are a few places where such double uses of
> tables are not posible because the config parser restrict this:
>
> * src and helo-src
> * match auth and userbase or auth table
> * match mail-from and virtual (you might want to reject local recipients)
> * match rcpt-to and virtual
>
> Following patch would fix this.
>
I agree that we may have been a bit too strict with these checks, I see
a benefit in relaxing them even for my own configuration.
If others don't voice objections, I think this can go in.
smtpd: be more relaxed in table usage