On Wed, 17 Oct 2018, Rupert Gallagher wrote:
IC is an effort to dig a hole in the water, because the problem of image spam
with obfuscated text cannot be solved by ocr.
My approach is a "better safe than sorry" best practice that anyone can
implement with existing software:
1. do not display inline the content of attachments and linked resources;
2. give high spam score (>=5) to any email with very low text to image ratio.
Your system, your rules, but it won't work for everybody.
We routinely receive messages from users needing help which contain 1~2 lines of
text describing the issue (like: 'my computer crashed' ) and then a screen-shot
taken with a cellphone camera (10~20 megapixel) which is 4~8 MB in size.
Sometimes the text is only in the subject and the screen-shot is the only thing
in the body.
I agree about not displaying inline attachments by default but that is a client
configuration issue and we cannot control our users' clients.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
