Вторник, 15 декабря 2020, 21:21 +03:00 от Andreas Metzler via Exim-users 
<[email protected]>:
 
> Your decoding test was only applied to the =?UTF-8?...?= part but the
> rest of the header contains non-ASCII characters which are not even
> valid UTF8. It could be that exims match function never matches on invalid
> strings.
 
Yes, I see. But my previous searches makes me think that without special 
instructions filter matches only the part of the header before the first "new 
line", which is right after "?=". Is it wrong for decoding Base64 and related 
only to the regex matching, so the part after "new line" breaks decoding from 
Base64? If so, is there a way to workaround this situation?
 
С уважением,
Kirill Sluchanko
[email protected]
 
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to