accept incoming DMARC and TLS reports with reporting addresses containing catchall separator(s)

Such as "-" when addresses are dmarc-reports@ and tls-reports@.

Existing configuration files can have these combinations. We don't allow them
to be created through the webadmin interface, as this is a likely source of
confusion about how addresses will be matched. We already didn't allow regular
addresses containing catchall separators.
This commit is contained in:
Mechiel Lukkien
2025-04-18 12:34:07 +02:00
parent 4eddf5885d
commit 794ef75d17
11 changed files with 175 additions and 27 deletions

View File

@ -1,11 +1,19 @@
Domains:
mox.example:
DMARC:
Account: mjl
Localpart: mjl
Account: dmarc
# Localpart contains a catchall separator
Localpart: dmarc-reports
Mailbox: DMARC
LocalpartCatchallSeparators:
- +
- -
Accounts:
mjl:
Domain: mox.example
Destinations:
mjl@mox.example: nil
dmarc:
Domain: mox.example
Destinations:
dmarc@mox.example: nil

View File

@ -2,10 +2,18 @@ Domains:
mox.example:
TLSRPT:
Account: mjl
Localpart: mjl
# Localpart contains a catchall separator
Localpart: tls-reports
Mailbox: TLSRPT
LocalpartCatchallSeparators:
- +
- -
Accounts:
mjl:
Domain: mox.example
Destinations:
mjl@mox.example: nil
tls:
Domain: mox.example
Destinations:
tls@mox.example: nil

View File

@ -10,4 +10,4 @@ Listeners:
HostTLSRPT:
Account: mjl
Mailbox: TLSRPT
Localpart: mjl
Localpart: tls-reports