Viktor Dukhovni via Postfix-users <[email protected]> wrote:
> On Sun, Feb 08, 2026 at 10:25:14AM -0500, Wietse Venema via Postfix-users 
> wrote:

>> PROBLEM: your server will accept spam for recipients that do not
>> exist in enfer-du-nord.net. Later it discovers that the recipient
>> does not exist, and returns that spam to someone who did not send
>> the spam. Your server may end up being denylisted for beong a
>> backscatter source.
>> 
>> Insteead, use recipient_bcc_maps.
> 
> Well, actually, I am impressed that the OP considered virtual
> alias_maps, that would also be my approach.  However, not as a PCRE
> wildcard rewrite, but rather as a per-recipient rewrite for each user.
> 
>    [email protected]   [email protected], [email protected]
>    [email protected]   [email protected], [email protected]
>    ...

Your "…" end up to be 200+ accepted addresses, and thus I came up with that 
wildcard rewrite. I am using virtual_alias_maps ever since running my first 
postfix server.

I guess I have add those @db.foo.example to my existing, accepting addresses in 
virtual_alias_maps.
awk will do this job.

> Or if the input domain is already a virtual alias domain, different
> from the underlying mailbox domain (which the server might not
> accept from external clients):
> 
>    [email protected]   [email protected], [email protected]
>    [email protected]   [email protected], [email protected]
>    ...
> 
> With transport mappints for "virtual.invalid" and "db.virtual.invalid".
> Of course with an existing mailstore the above would need additional
> aliases of the "@virtual.invalid" form for each underlying mailbox.
> I always start with that, but it should be possible as a retrofit.

And, I will substitute my @enfer-du-nord.net addresses by something like 
@ellael.lan

Thanks. That will be my way if I will fail with the recipient_bcc_maps approach.

Regards,
Michael

_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to