Vsevolod Stakhov

https://github.com/rspamd/maps/commit/cc52a0a25515a1d7ad72b7e595ebd2e2c2b34926 R_EMPTY_IMAGE is expected to be there.

Please check output of https://github.com/rspamd/rspamd/actions/runs/9755846790/job/26933504019?pr=5036 There are some issues introduced: * Incompatible pointers passed * Warnings in dkim.c (maybe somewhere else as well) Could you please address those and make...

I don't see why does it matter at all. Yes, there are broken DKIM signers in the world (surprise) but it is usually better to support them then to break....

If gmail does not encode 8bit characters in the headers it is their problem.

I don't understand how is MIME encoding (meaning message based) related to SMTPUTF (meaning the concrete message transaction based).

All message headers must be 7bit. Apparently rfc2047 allows to encode any header, including `From`, `To` and even `Received`.

The only thing that actually allows utf8 in the headers is SMTPUTF rfc. Rspamd does not support it and I have no intention to add such a support (unless it...

You are right @TaaviE and that's really a bit problematic. It seems we need to support SMTPUTF8 at some point. I don't have much desire to implement that though, however...

Tracking PR: https://github.com/rspamd/rspamd/pull/5056

Do you have any .eml samples with UTF8 text inside?