Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Character Encoding / Signed msg #28

Open
KAlamurov opened this issue Jun 28, 2021 · 1 comment
Open

Character Encoding / Signed msg #28

KAlamurov opened this issue Jun 28, 2021 · 1 comment

Comments

@KAlamurov
Copy link

KAlamurov commented Jun 28, 2021

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.

@KAlamurov KAlamurov changed the title Character Encoding Character Encoding / Signed msg Jun 30, 2021
@KAlamurov
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant