> Postfix with default milter body chunk size 65535:
>
> mail processing time 1m30.154298259s
>
> Postfix with milter body chunk size 1048576:
>
> mail processing time 17.52360866s
it looks to me like postfix is able to feed a milter very quickly
i just did a couple of quick tests here, an ~83
On Fri, Aug 16, 2019 at 04:53:23PM +1000, Viktor Dukhovni wrote:
> Bottom line, only trust local resolvers you deploy, configure
> *correctly* and test.
Well, it doesn't _have_ to be local. You could, for instance, be
connected to a resolver that you know you can trust (FSVO "know" and
"trust")
Matthias Schneider:
> Any chance to get a config for MILTER_CHUNK_SIZE? It would be great so
> have an easy and fast switch. I may have different settings on different
> mail systems (because of 3rd party milters), its hard to manage
> different customized postfix versions in my distribution
Matthias Schneider:
> my tests are little bit frustrating:
>
>
> Postfix with default milter body chunk size 65535:
>
> mail processing time 1m30.154298259s
>
> Postfix with milter body chunk size 1048576:
16x larger packet size.
> mail processing time 17.52360866s
5x faster processing. You
Am 16.08.19 um 16:03 schrieb Viktor Dukhovni:
You could raise the limit, but it may be more productive to figure
out why your milter application is "slow" with the default chunk
size. AFAIK, other milter applications are doing fine with the
default size.
I am using the golang implementation:
my tests are little bit frustrating:
Postfix with default milter body chunk size 65535:
mail processing time 1m30.154298259s
Postfix with milter body chunk size 1048576:
mail processing time 17.52360866s
(same mail of 107421kb size / some time is added in body() but it should
be
On Fri, Aug 16, 2019 at 03:51:05PM +0200, Matthias Schneider wrote:
> Any chance to get a config for MILTER_CHUNK_SIZE? It would be great so
> have an easy and fast switch. I may have different settings on different
> mail systems (because of 3rd party milters), its hard to manage
> different
Any chance to get a config for MILTER_CHUNK_SIZE? It would be great so
have an easy and fast switch. I may have different settings on different
mail systems (because of 3rd party milters), its hard to manage
different customized postfix versions in my distribution repositories.
Thanks,
Viktor Dukhovni:
> > On Aug 16, 2019, at 10:33 PM, Matthias Schneider
> > wrote:
> >
> > I was wondering why the transfer of a 100mb mail to my milter application
> > was slow, i found the bottleneck in the body chunk transfer.
> >
> > The maximum packet length seems to be fixed to 64k, it
> On Aug 16, 2019, at 10:33 PM, Matthias Schneider
> wrote:
>
> I was wondering why the transfer of a 100mb mail to my milter application was
> slow, i found the bottleneck in the body chunk transfer.
>
> The maximum packet length seems to be fixed to 64k, it would be great if we
> could
Hi,
I was wondering why the transfer of a 100mb mail to my milter
application was slow, i found the bottleneck in the body chunk transfer.
The maximum packet length seems to be fixed to 64k, it would be great if
we could make that configurable in postfix (uint32 is possible).
best
> On Aug 16, 2019, at 1:29 AM, Viktor Dukhovni
> wrote:
>
> enable DANE outbound:
>
> http://www.postfix.org/TLS_README.html#client_tls_dane
>
> main.cf:
> smtp_dns_support_level = dnssec
> smtp_tls_security_level = dane
>
> /etc/resolv.conf
> # A validating *local*
12 matches
Mail list logo
