-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error parsing detail rules with content preview header #34
Comments
I will check how to avoid the parsing the content preview part of the X-Spam-Report header. Otherwise, it will always be possible to send a mail with content falsely recognised as a spam rule. |
Another example.
|
Another example for better problem analysis. In this case, retrieved two values from Content preview.
|
Problem not solved? |
Sorry that I haven't had the time to close the open issues yet. The problem will be fixed in the next update, which will definitely be released until the end of next week. |
Should be fixed as a part of the merge request c1ca2a9. It will be uploaded as a new version in the official Thunderbird add-on store this week. |
I tested the new add-on version 1.3.1. Unfortunately, it isn't quite good yet.
The error repeats, when the number 30 appears in Content Preview. Maybe, here's the problem?
Example 1:
![obraz](https://user-images.githubusercontent.com/90441957/135804807-70dab926-72bb-46dd-996b-446a39b01dc9.png)
Source 1:
Example 2:
![obraz](https://user-images.githubusercontent.com/90441957/135805621-dae02525-e876-43c6-813e-7b9be874dc5d.png)
Source 2:
Originally posted by @MXEH in #33 (comment)
The text was updated successfully, but these errors were encountered: