> On 29 Dec 2018, at 02:56, Wietse Venema <wie...@porcupine.org> wrote:
>
> Maybe you can figure out why rspamd is slow. Are you sending huge
> messages, or is rspamd slow because of DNS lookups?
>
> Maybe you can use /usr/sbin/sendmail for local submissions? This
> requires configuring non_smtpd_milters in main.cf.
>
> Otherwise, you can run milters post-queue, with a null SMTP-based
> content filter (Postfix SMTP client sending directly into Postfix
> SMTP server).
>
> /etc/postfix/master.cf
> # The default before-queue SMTP port, configured
> # to send mail through a null SMTP filter.
> smtp inet .. .. .. .. .. .. smtpd
> -o content-filter=smtp:127.0.0.1:10025
>
> # New post-queue SMTP port. Set 'no content filter'
> # to avoid mailer loops (belts and suspenders).
> 127.0.0.1:10025 inet .. .. .. .. .. .. smtpd
> -o smtpd_milters=inet:127.0.0.1:12345
> -o content_filter=
>
> # Optional, to use rspamd for /usr/sbin/sendmail submissions.
> pickup unix .. .. .. .. .. .. pickup
> -o content-filter=smtp:127.0.0.1:10025
>
> Untested, but it should be very close.
>
> Wietse
Maybe the issue was related to this message:
"got IO timeout with server fuzzy2.rspamd.com(212.24.145.107:11335), after 1
retransmits"
At the moment I block in my firewall UDP port 11335. In the relays the port is
open.
I will try tomorrow to see if it's related to this timeout (I think it timeouts
in 4 seconds).
