Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header.

[Garreau\, Alexandre]

Le 23/09/2018 à 09h05, Teemu Likonen a écrit :
> Alexandre Garreau [2018-09-23 02:04:44+02] wrote:
>
>> How to make that readable? why doesn’t nnmail-split-fancy acts on a
>> decoded buffer? I need this to correctly receive and track that mail
>> :/
>
> There is variable nnmail-mail-splitting-decodes which, with a non-nil
> value, should cause the splitting mechanism to decode headers before
> splitting.

Thank you very much! it works excellently!

Why isn’t this behavior the default? is there any advantage to parse the
yet-encoded content (maybe its encoding?) or still big issue by decoding
before rather than after?