Encoding problem

[Suncatcher]

I set up forwarder on AWS and now it forwards messages to Yahoo mail. All is fine except that sometimes I receive such abracadabra messages with messed encoding

пїЅoпїЅпїЅпїЅпїЅпїЅ пїЅpпїЅпїЅпїЅпїЅ! 
пїЅoпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ пїЅ пїЅпїЅcпїЅпїЅпїЅaпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ пїЅoпїЅпїЅпїЅпїЅ! 
9 пїЅaпїЅ пїЅ пїЅпїЅпїЅпїЅuпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅeпїЅпїЅпїЅпїЅпїЅ "пїЅпїЅпїЅпїЅпїЅпїЅpпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ". пїЅпїЅпїЅпїЅoпїЅпїЅпїЅпїЅ пїЅoпїЅпїЅпїЅпїЅпїЅ пїЅaпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅ. 
пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ, пїЅcпїЅпїЅ пїЅoпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ/пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ пїЅaпїЅ пїЅпїЅпїЅпїЅa - пїЅaпїЅпїЅпїЅ пїЅпїЅ пїЅпїЅpпїЅ, пїЅaпїЅпїЅoпїЅaпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅoпїЅпїЅпїЅпїЅпїЅeпїЅпїЅпїЅпїЅ пїЅпїЅeпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ пїЅпїЅ пїЅпїЅпїЅпїЅ. 
пїЅпїЅпїЅпїЅ пїЅ пїЅaпїЅ пїЅпїЅ пїЅпїЅoпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅcпїЅпїЅпїЅпїЅ, пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅeпїЅпїЅ пїЅ пїЅaпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ-oпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ. 
пїЅпїЅпїЅaпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅeпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅpпїЅпїЅпїЅ, пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ, пїЅaпїЅпїЅ пїЅпїЅпїЅ c пїЅпїЅпїЅпїЅ. 
пїЅпїЅпїЅoпїЅпїЅпїЅпїЅ! пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅo пїЅaпїЅпїЅ пїЅaпїЅпїЅпїЅпїЅ cпїЅпїЅпїЅaпїЅ - пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅaпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅ. 

пїЅпїЅпїЅoпїЅпїЅaпїЅпїЅпїЅ oпїЅ пїЅпїЅпїЅпїЅпїЅ "пїЅeпїЅcпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅoпїЅпїЅ пїЅпїЅpauпїЅпїЅ": polkua.com

Previously they were getting to my mailbox from the single sender and I thought it's a matter of this concrete sender, but now I received similar message from couple of other senders. I suspect that messages are messed during AWS Lambda forwarding. How can I check this hypothesis?
Do original messages are saved anywhere on AWS so I can check if they break before or after?
Or maybe it's a problem of Yahoo?

[Suncatcher]

Also I observe such kind of encoding mess:

I strongly suspect that it is a forwarder issue, 'cause I never received such things to those forwarded email directly.

[Suncatcher]

Does forwarder fully support Unicode?

[jakubboucek]

Does forwarder fully support Unicode?

It should be, because Node.js is support Unicode and forwarder is not touch the content of message body.

[jakubboucek]

Please check the message saved in S3, open it and found all lines begins with Content-Type: and Content-Transfer-Encoding:. And next do same thing in message delivered to your inbox.

[Suncatcher]

It shows:

Content-Type: multipart/alternative;
	boundary="b1_f9f245e8bd726478e0c11a2992ef21ff"
Content-Transfer-Encoding: 8bit

--b1_f9f245e8bd726478e0c11a2992ef21ff
Content-Type: text/plain; charset=cp1251
Content-Transfer-Encoding: 8bit

However, as you see in message file in S3 text is showed properly

[Suncatcher]

And in Yahoo web-mail it also showed incorrectly. I assume it's messed in Forwarder

[Suncatcher]

It's definitely forwarder problem. I observe this in messages from different senders.

[amertak]

@Suncatcher I think I have a fix for this.

#131

[Suncatcher]

@amertak thank you!