mail.ru web service

Thank you for reply, i saw and try to use this recommendation, but there is already chosed Russian language.Jeff wrote: ↑Mon Feb 11, 2019 3:14 pm Try changing the following setting in Windows (instructions may be slightly different for your OS):
- Windows Control Panel
- Clock and Region / "change date, time or number formats"
- Click on "administrative" tab
- Press the "change system locale" button in the "language for non-unicode programs" section (bottom)
- Select the most appropriate language from the list
-> This will likely require you to restart your computer or Windows
Yes, other messages displayed correctly.Jeff wrote: ↑Mon Feb 11, 2019 4:05 pm I noticed that other messages are displayed correctly. Do you know if those are using a different encoding format? (you may be able to view the message, then look under menu: "View / Encoding" to see what the message encoding is). Koi8-r should be manually converted by PP, so perhaps they're using that. I saw that there are at least a couple of different "Russian" values in the non-unicode selection, so it's possible that changing to another one would help, but it's also possible that it would break your other messages. Unfortunately, that's about your only recourse at the moment.
I known I've been saying this for a long time, but one of these days, POP Peeper *will* support unicode so this won't be an issue anymore; hopefully sooner than later...
Are there any way to fix it? May be force POP Peeper to encode messages from this sender like utf8?Jeff wrote: ↑Tue Feb 12, 2019 2:53 pm Ah, ok. So in the working samples, the text is explicitly marked as utf-8; whereas in the sample that failed, there's no such indication. I'm not entirely sure that's allowed (I would lean toward it not correct, but it's possible that things have changed [although, I haven't found any such evidence and it doesn't make logical sense anyway]), as any character encoding not indicated is assumed/required to be ascii. The fact that the 'from' and 'reply-to' fields in the same message are properly encoded also suggests that it's a mistake.
Do you get a lot of this type of email? And, in this case, was the email spam?
Thank you, if you can make some workaround i will be very happy!) Potential extra cycles is ok, i think modern CPU wouldn't notice it at all. Of course may be option to switch on and off it in settings will be nice fore those who don't get such kind of problem.
Sorry for my bad English(Jeff wrote: ↑Thu Feb 14, 2019 2:00 pm It's unlikely that something like this would be noticed for individual messages; but it's something that would start racking up a lot of time when someone has to download 10K messages. It's not just the subject field, it would have to apply to the from, to and cc fields, as well.
I was wondering if you could you clarify a couple of your previous statements -- I had asked how many emails you've seen and also if the email was spam. You had answered:
"1 message in 2-3 days, email not in spam"
Does that mean you get 1 such message every 2 or 3 days; or that you have only received 1 email in total?
And I wasn't specifically asking if the email was *evaluated* as spam, but rather if the email itself was actually spam, ie. do *you* believe the email was spam? The reason I ask is that the formatting of the message (that is, some fields are formatted correctly, but the subject was not) is not technically correct, which makes it more likely that it originated as spam; although, newsletters are also not always setup correctly and so I would go 50/50 on it being either spam or a newsletter.