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

Message charset: mb_convert_encoding + aliases #196

Merged
merged 9 commits into from
Sep 27, 2017

Conversation

Slamdunk
Copy link
Collaborator

@Slamdunk Slamdunk commented Sep 27, 2017

@Slamdunk Slamdunk added the bug label Sep 27, 2017
@Slamdunk Slamdunk added this to the 1.0 milestone Sep 27, 2017
@Slamdunk Slamdunk changed the title Message charset bugfixes Message charset: mb_convert_encoding + aliases Sep 27, 2017
@Lewiscowles1986
Copy link

Damn... Good work 👍 🥇

@Slamdunk
Copy link
Collaborator Author

@Lewiscowles1986 thank you. Stay tuned for the 1.0 milestone.

You seem to have faced a lot of edge cases in the email universe: I would love to have your help in gathering them so we can stress test the library.

@Lewiscowles1986
Copy link

Lewiscowles1986 commented Sep 28, 2017

The problem is that without decoding the emails I can't tell if they contain private or confidential information. It's like being on the edge of an edge...

I am digging through a branch backup in spare time to see if there is anything I can share.

The app itself dumps to a sqlite DB, so I can get information like unique headers, content type. I see I have a couple of changes to the lib that need tests. I'll create issues as needed.

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

Successfully merging this pull request may close these issues.

2 participants