[Crash] error parsing email objects #40
Labels
No labels
bug
enhancement
good first issue
halted
help wanted
security
wait for upstream
wait to be tested
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: b3yond/ticketfrei#40
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Author: @b3yond Posted at: 25.09.2018 09:38
Expected Behavior
when an email is received, it searches for patterns in the body to check if it is appropriate.
Actual Behavior
it crashes, because the email body is not passed correctly - report.text needs to be a string.
Traceback:
Author: @d24phant Posted at: 07.10.2018 07:07
report.text is fed by the email.message.get_payload() function:
The case of a simple string or bytes object is well covered, the problem here is that it was the only test case ;)
We need to decide how we treat the EmailMessage objects in this list; do we want to put all of them in report.text?
Author: @b3yond Posted at: 07.10.2018 16:51
untreated MIMEtypes which are multipart are logged - we should revisit this once in a while.
Author: @b3yond Posted at: 07.10.2018 21:18
doesn't work yet, not even text works anymore.
test case:
Author: @b3yond Posted at: 07.10.2018 21:27
During the test, there were some shutdowns:
quickfix on master
Author: @b3yond Posted at: 07.10.2018 21:46
pgp signed mails don't get posted yet, but the other mails went through.
another test run would be nice, but I'm too fucking tired.
Author: @b3yond Posted at: 08.10.2018 13:17
pgp signed mails don't throw errors anymore. They are still not posted. Nasty, but I would not consider it a release blocker.
Author: @d24phant Posted at: 08.10.2018 18:00
Me neither ;) Not perfect, but shouldn't prevent from releasing!