When an embedded MIME image does not contain a file name, fuzzyocr uses the Content-ID to generate a file name. If the Content-ID contains a ".", fuzzyocr mistakenly considers the characters after the "." to be the filename suffix, resulting in false positives of the FUZZY_OCR_WRONG_EXTENSION rule. The patch I will attach after opening the bug should fix the problem, by adding "." to the list of characters fuzzyocr replaces with an "_" when generating a file name from the Content-ID. This will result in the suffix not being defined, and remove the false positives. Reproducible: Always Steps to Reproduce:
Created attachment 116571 [details, diff] patch to fix the problem
Any thoughts about adding this patch to the ebuild? It's been almost a year...
Thanks for the report! And sorry for the delay I've just added 3.6.0 in tree, with this patch included