Please - make so that in a window of sending spam report (email body in second box) - there was coding UTF-8 and that then was not recoded in another at sending to providers

Russian spam it is simple not to know after your recoding:
=====================
-это самый красивый город ->>
-&# 1101;&# 1090;&# 1086; &# 1089;&# 1072;&# 1084;&# 1099;&# 1081; &# 1082;&# 1088;&# 1072;&# 1089;&# 1080;&# 1074;&# 1099;&# 1081; &# 1075;&# 1086;&# 1088;&# 1086;&# 1076;
=====================

Ah, so which is the most beautiful city? FWIW, I agree, it is obviously next to impossible to follow the sequence as a reporter when the spam is so transformed and worse for the abuse desks receiving the SC reports. The cases I have seen personally did not actually originate in Russia/Cyrillic netspace but how can the abuse desks relate what was sent to what is reported? I guess they concentrate on the headers and timestamps.

This matter has been raised before, maybe in the newsgoups, but in a different context, and which I can't get to just now. And I don't think it was sympathetically received. Anyway, processing "alters the evidence", at least for a human trying match evidence and source, even trying to determine whether the material is actually UCE/UBE. There is indeed a problem, I think.