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
Creating filters - extracting headers can fail if msg > 16kByte #206
Labels
Comments
quick fix versions: ESR 102: quickFilters-wx-5.9.4pre3.zip ESR 115: quickFilters-wx-6.2pre61.zip To one of the versions above download the correct zip file and drag it into Add-ons Manager (do not extract contents or it won't install). |
RealRaven2000
changed the title
When creating new filters - Reading headers can fail if msg > 16kByte
When creating new filters - extracting headers can fail if msg > 16kByte
Aug 13, 2023
RealRaven2000
changed the title
When creating new filters - extracting headers can fail if msg > 16kByte
Creating filters - extracting headers can fail if msg > 16kByte
Aug 13, 2023
RealRaven2000
added a commit
that referenced
this issue
Aug 13, 2023
RealRaven2000
added a commit
that referenced
this issue
Aug 13, 2023
fixed in 6.2 - Published 13/08/2023, also backported to 5.9.4, same day |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Important problem - when reading the headers (especially custom headers such as "
delivered-to
") from an email, adding the search term may fail if the email > 16kb. This may both happen when using the "mailing list" template and when using a custom template.When this error condition happens, the filter assistant is not able to extract data from the headers of the original email
This is due to the following bug in
quickFilters.clsGetHeaders.read()
this should not be
return null
but simplybreak
- because otherwise the whole structureCurrentHeader.headers
is not initialized.The text was updated successfully, but these errors were encountered: