On 9 May 2022, at 7:58, Sam Birch wrote:
And as Randy said, the reason why MailMate can’t “strictly
block” 1-pixel images is that, in many cases, _MailMate has no way
to know the size of the image until it fetches it from the remote
server._
For example, here’s an <IMG> tag from spam message I recently
received (re-wrapped for clarity, and domain changed to avoid being
tagged as spam):
```
<img src="http://www.not-the-original-dom.ain/cljo8bq86/Cw4ear2u
2QPT6WIi5q6Mr2gNDEIIpk_24HKoK0Q7ulY/fSlEIVCxnTqw7304Z8k5-7DeoB8B
TUDm4NmMX28zpyXKVfWsVIjfNzFFKOiXLw399vfpzvuSHfoXwZGLWvq6TfyuQPAJ
OvdL7LOQ_tKLpSvPVXO1xJtHDimWEa5bpThzzWOgItSd6XMoWJdv7yKnLtzwcx3m
-zrp7icAZ_1CAcg”>
```
Can you tell that this is a 1-pixel image?
Neither can MailMate.
The difference between "Blocked" and "Strictly Blocked" is that the
latter uses a list of known-undesirable sources? Given this, I assume
the purpose of the warning that a 1-pixel image has been downloaded is
to let the user know that the message whose embedded images were
downloaded contains obvious trackers? Yet, the message may very likely
be from a "good" source but sent using a commercial mail distribution
service which adds its own trackers. It would be more helpful if the
warning would add the source of each just-downloaded 1-pixel image to
the "Strictly Blocked" list. Sort of a "Fool me once, shame on you; fool
me twice, shame on me" thing._______________________________________________
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
