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

How to set encoder(8bit,base64 or quoted-printable) in symfony mailer #16812

Closed
adnan-rasheed opened this issue May 19, 2022 · 7 comments
Closed
Labels

Comments

@adnan-rasheed
Copy link

No description provided.

@xabbuh xabbuh added the Mailer label May 26, 2022
@xabbuh
Copy link
Member

xabbuh commented May 26, 2022

Can you please elaborate a bit more what piece of information you are missing?

@adnan-rasheed
Copy link
Author

adnan-rasheed commented May 31, 2022

@xabbuh there is an option in php mailer for setting content transfer encoding to one of these methods 8bit,base64, 7bit & quoted-printable. Also there is way to set encoding method in swiftmailer but in symfony I did not see any documentation to set one of the value from above methods

@xabbuh
Copy link
Member

xabbuh commented Jul 4, 2022

I think we need an easy way to configure that in the code itself first (see symfony/symfony#44557).

@fritzmg
Copy link
Contributor

fritzmg commented Aug 14, 2023

In SwiftMailer 5.x we had setEncoder + get8BitEncoding etc. so you could do

$message->setEncoder(\Swift_Encoding::get8BitEncoding());

However, this was removed in 6.x: swiftmailer/swiftmailer@d210d67

@mpichot
Copy link

mpichot commented Aug 31, 2023

I'm wondering why this was removed? 🤔
I can't find a good solution to encode emails other than quoted-printable.
Anyone?

@javiereguiluz
Copy link
Member

I'm closing this one because the related code issue was closed after "expiring" (symfony/symfony#44557).

Please, try to ask about this in the GitHub Discussions or Slack chat shown in https://symfony.com/support If there's enough interest, the next step would be to create an issue in the code repository and try to gather some support for it. Finally, there could be a PR in the code repository and then we would document it here.

Thanks for understanding.

@fritzmg
Copy link
Contributor

fritzmg commented Sep 4, 2023

No need to create a new issue. The last comment in the original issue states:

Feel free to comment if this is still relevant, I can always reopen!

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

No branches or pull requests

5 participants