Any chance to get a config for MILTER_CHUNK_SIZE? It would be great so=20
have an easy and fast switch. I may have different settings on different=20
mail systems (because of 3rd party milters), its hard to manage=20
different customized postfix versions in my distribution repositories.


Thanks,

Matthias Schneider

Am 16.08.19 um 15:32 schrieb Matthias Schneider:
> Any chance to get a config for MILTER_CHUNK_SIZE? It would be great so=20
> have an easy and fast switch. I may have different settings on=20
> different mail systems (because of 3rd party milters), its hard to=20
> manage different customized postfix versions in my distribution=20
> repositories.
>
>
> Thanks,
>
> Matthias Schneider
>
>
>
> Am 16.08.19 um 14:49 schrieb Viktor Dukhovni:
>>> On Aug 16, 2019, at 10:33 PM, Matthias Schneider=20
>>> <matthias.schneider@rmail.de> wrote:
>>>
>>> I was wondering why the transfer of a 100mb mail to my milter=20
>>> application was slow, i found the bottleneck in the body chunk=20
>>> transfer.
>>>
>>> The maximum packet length seems to be fixed to 64k, it would be=20
>>> great if we could make that configurable in postfix (uint32 is=20
>>> possible).
>> * milter communication fails if a single header is larger than 64K.
>>
>> =C2=A0=C2=A0 If a single header is larger than 64KB (which is not poss=
ible in the
>> =C2=A0=C2=A0 default configuration) then it cannot be transferred in o=
ne block to
>> =C2=A0=C2=A0 libmilter and hence the communication fails.=C2=A0 This c=
an be avoided by
>> =C2=A0=C2=A0 increasing the constant MILTER_CHUNK_SIZE in
>> =C2=A0=C2=A0 include/libmilter/mfdef.h and recompiling sendmail, libmi=
lter, and
>> =C2=A0=C2=A0 all (statically linked) milters (or by using undocumented=
 compile
>> =C2=A0=C2=A0 time options: _FFR_MAXDATASIZE/_FFR_MDS_NEGOTIATE; you ha=
ve to
>> =C2=A0=C2=A0 read the source code in order to use these properly).
>>