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
Ensure parsed e-mail message is not discarded #67
Ensure parsed e-mail message is not discarded #67
Conversation
8ff1be4
to
36d2f7f
Compare
tests/tests/test_models.py
Outdated
b"\x00\x00\x00\rIDAT\x18Wc\xf8\xff\xef\xdf\x7f\x00\t\xf6\x03\xfbW\xfe{\x1b" | ||
b"\x00\x00\x00\x00IEND\xaeB`\x82" | ||
) | ||
image.add_header("Content-ID", f"<123456789>") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit nit, but flake8 is complaining about the f-string: f-string is missing placeholdersflake8(F541)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no worries, I aim to comply to flake8! It used to be an interpolated thing but I updated it afterwards.
As for flake8 and the likes - have you considered adding the check to CI? I checked but couldn't find anything for isort/black either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we have considered adding at least flake8 and we will probably do it in the future. Not 100% sure about adding black and reformat all the code.
BCC addresses are not included in e-mail headers, as this would disclose the other recipients, breaking the 'blind' aspect. As such, there is no point in trying to read this from the parsed email, it will never yield valid addresses. Removing the line removes confusion and prevents wrong impressions.
Message reconstruction from string dropped custom headers and particular attachment content disposition/relations.
47198d0
to
c535118
Compare
Closes #66 |
Related to #66
The custom header treatment feels a bit fragile, though I do believe that: