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

Fix default_charset and _process_message() to accept emojis in utf-8 encode #199

Closed
lologf opened this issue Jan 18, 2019 · 7 comments
Closed

Comments

@lologf
Copy link

lologf commented Jan 18, 2019

This fix works in python 2.7, django 1.11 and database with charset utf8 and collation ut8_general_ci. I can't changing charset and collation of production database for an emoji in email subject.

#198

@sanderroosendaal
Copy link

Is this issue going to be fixed soon? I am getting errors because of emoji's in email subject.

@coddingtonbear
Copy link
Owner

As far as i’m aware, this isn’t an issue for users using a properly configured database, @sanderroosendaal — you may want to look into that first.

Relatedly, the associated PR above isn’t one that is mergeable for a variety of reasons; so the answer is not likely to be one you want to hear.

@sanderroosendaal
Copy link

@coddingtonbear Understood, but what is a proper database setting? djang-mailbox set my mysql database to utf8mb4_unicode_ci for the subject field. This generates an error on fetching the email.

@coddingtonbear
Copy link
Owner

It’s very difficult to say without having at least a traceback; do you happen to have one?

@coddingtonbear
Copy link
Owner

Just to be clear — this module is not involved in selecting your collation, so the proper fix is outside in your django/db settings. Without knowing more, I might suggest the following resources:

@sanderroosendaal
Copy link

thanks for replying. I do have a traceback but don't want to clutter your issues list. I will check the links you kindly provided.

@pfouque
Copy link
Collaborator

pfouque commented Dec 17, 2023

The setting has ben fixed on main (but there is no release date yet)

@pfouque pfouque closed this as completed Dec 17, 2023
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

4 participants