You can look at the headers and reject Mails with Headers["auto-submitted"]. Sieve should add them.
Am 28. Februar 2025 um 00:25 schrieb "doobry via dovecot" <dovecot@dovecot.org mailto:dovecot@dovecot.org?to=%22doobry%20via%20dovecot%22%20%3Cdovecot%40dovecot.org%3E >:
Dear Dovecot community,
we changed
sieve_redirect_envelope_fromtoorig_recipientrecently to fix sieve redirects in case the forwarded mail comes from a DMARC-enabled domain.While this works well, it creates a new problem: if the receiving mail server (the one in charge of the redirect destination) reacts with a bounce mail, the bounce now will go to
orig_recipient- the mail address that has the redirect in place, which means no less than creating a mail bomb (endless mail loop).See the following example:
- alice@sender.org sends mail to jane@our-domain.org
- jane@our-domain.org has a sieve redirect to jane@redirect-target.org
- jane@redirect-target.org replies with a bounce because their mailbox is full.
- The bounce mail gets sent to jane@our-domain.org.
- The loop starts again at step 2.
Is it possible to configure dovecot/pigeonhole to *not* forward the bounce mails from step 4 again?
Probably it would work to add manual extra checks to the sieve redirect rules, but that would need to be followed by any user who configures a redirect. So I'm more looking for a server-wide configuration change that fixes this problem.
Looking forward to hear about your thoughts on the problem.
Kind regards doobry
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org