You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I am using the library mainly for exporting eml via Swiftmailer. The problem i am facing is with the encoding.
The language is Bulgarian. The subject is encoded fine so the problem occurs only in the body.
I have tried to change the global default encoding in Swiftmailer from utf-8 to windows1251, 1252 and also the encoding type from raw to quoted-printable but nothing has changed so far.
Also when the email is signed, at the end of the parsed email there is the whole email again in source code format and an attached file mime.txt
The conversation is parsed but the attachments and the signature (with the conversation) are stored in one multipart/signed content type in base64 (full copy of the email without to and from headers). I saw that every attachment and the signature must be in separate content types (tried with another convertor)
Thank you in advance.
The text was updated successfully, but these errors were encountered:
KAlamurov
changed the title
Character Encoding
Character Encoding / Signed msg
Jun 30, 2021
I have forced the character encoding for the body to be windows-1251 in Message.php and it works now but the problem with the signed emails still exists.
Hello. I am using the library mainly for exporting eml via Swiftmailer. The problem i am facing is with the encoding.
The language is Bulgarian. The subject is encoded fine so the problem occurs only in the body.
I have tried to change the global default encoding in Swiftmailer from utf-8 to windows1251, 1252 and also the encoding type from raw to quoted-printable but nothing has changed so far.
Also when the email is signed, at the end of the parsed email there is the whole email again in source code format and an attached file mime.txt
The conversation is parsed but the attachments and the signature (with the conversation) are stored in one multipart/signed content type in base64 (full copy of the email without to and from headers). I saw that every attachment and the signature must be in separate content types (tried with another convertor)
Thank you in advance.
The text was updated successfully, but these errors were encountered: