Viktor Dukhovni via Postfix-users <[email protected]> wrote:
> On Sun, Feb 08, 2026 at 10:25:14AM -0500, Wietse Venema via Postfix-users
> wrote:
>> Michael Grimm via Postfix-users:
>>> (2) additional pcre:virtual_alias_maps to the existing
>>> lmdb:virtual_alias_maps:
>>> /^(.*)@enfer-du-nord\.net$/ ${1}@enfer-du-nord.net
>>> ${1}@dbmail.enfer-du-nord.net
>> 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.
> 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.
One Last Thing ;-)
I will switch from former @enfer-du-nord.net and @dbmail.enfer-du-nord.net to
@ellael.lan and @dbmail.ellael.lan in virtual_alias_maps as advertised above.
Now, would it be possible to come back to my approach (2) above?
But modified like:
/^(.*)@ellael\.lan$/ ${1}@ellael.lan ${1}@dbmail.ellael.lan
Or "hardened" by (I have 5 final mailboxes, only):
/^(user1|user2|user3|user4|user5)@ellael\.lan$/ ${1}@ellael.lan
${1}@dbmail.ellael.lan
Does that bear any risks I fail to imagine?
Thanks and regards,
Michael
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
