> I'll set the
>
> smtpd_delay_reject=yes
>
> and watch that for awhile to see what happens.
Okay, I remembered what I was *trying* to make sure happened by setting
smtpd_delay_reject=no
For now I'm trying to do everything stepwise and more-or-less separated in
Postfix config, until I get a good handle on flow. Later on I'll clean it up
and streamline it.
Right now, after postscreen, I pass email to a prequeue isntance of amavis
SMTPd-only SPF + DKIM checks are done here.
Amavis passes back to a postfix smtpd instance which I set up with
-o smtpd_milters=inet:127.0.0.1:8893
-o non_smtpd_milters=inet:127.0.0.1:8893
-o content_filter=amavis:[127.0.0.1]:13003
where my goal is to first pass through an OpenDMARC milter (port 8893), and
THEN to a 2nd amavis instance, postqueue, to do content (A/V, A/S) scanning.
I think I set
smtpd_delay_reject=no
to make sure that that order was preserved.
But TBH I can't convince myself from reading if smtpd_delay_reject has any
effect.
So my question is -- does it?
If I set the recommended
smtpd_delay_reject=yes
in order to 'fix' the original issue here of the "double reject", will the mail
still flow through the OpenDMARC milter
-o smtpd_milters=inet:127.0.0.1:8893
-o non_smtpd_milters=inet:127.0.0.1:8893
first, and only them if passed, on to the postqueue Amavis?
-o content_filter=amavis:[127.0.0.1]:13003
Thanks
Jason
