Hey,
it seems you're still offering
250-PIPELINING
Both options work as exspected on my side (Postfix 3.7.6).
best regards
Carsten
On 21.12.23 10:29, Till W. via Postfix-users wrote:
Dear team,
we enabled smtpd_forbid_unauth_pipelining in our Postfix, but
unfortunately it still accepts \
Kai,
both are running simultaneously. So at smtpd_recipient_restriction stat
the milter will also get the recipients. As far as I have seen the
postfix restriction react faster.
So if you reject somebody with an access_map, you won't see any scan
result in rspamd. Only the milter connect, because
have nothing to process. Did i get it correctly? :)
>
> Stefan
>
> Am Fr., 19. Okt. 2018 um 09:17 Uhr schrieb Carsten Rosenberg <mailto:c...@ncxs.de>>:
>
> Have a look here:
>
> https://msg.wikidoc.info/index.php/Milter_operation
>
> Milter
on_fqdn_recipient,
> reject_unknown_sender_domain,
> reject_unknown_recipient_domain,
>
> is checked.
>
> amavis-milter seems dead.
>
>
> Am Fr., 19. Okt. 2018 um 08:33 Uhr schrieb Carsten Rosenberg <mailto:c...@ncxs.de>>:
>
> Hi,
>
> s
Hi,
smtp_milters and restrictions are working at the same time.
smtpd_recipient_restriction will be evaluated at the same as the Milter
RCPT stage.
So a ClamAV Milter should run at EOM milter stage. Anything else is
useless ;)
And in my opinion quarantine is sooo 2010. Reject (pre-queue) or
deli
