David W. Tamkin writes:
Has anyone yet seen what kinds of HTML are stuck into mail by
didtheyreadit.com, so that we can catch it and prevent it from phoning
home (either by marking it with a warning to display it as flat text, or
by stripping out the code that checks in with the mother ship)?
They're using a web bug.
<img src="http://didtheyreadit.com/index.php/worker?code=xxxxxxxxxxxxxxxx"
width="1" height="1" />
at the end of the html part.
There was a lengthy discussion of didtheyreadit on spam-l, but you need to
be a subscriber to get access to the archive.
I think their product (which does not deserve to be called a service) is
sneaky and vicious. It's nobody else's business whether, much less
WHEN, I read a message.
Fully agreed. And while we're at it, I'm also filtering out DSN and
return-receipt headers here. The initial reason for that, though, was
that we received email from luser sites where the address in the DSN/
return-receipt headers wasn't masqueraded, and therefore not deliverable.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail