Jump to content

parse problem


Recommended Posts

just for giggles, IE6, FireFox 0.8, didn't resolve it for me either. So yes, it's screwed up, some Quoted-Printable artifacts in there (which again points to needing to see the headers to keep this display in context) ... but if browsers won't resolve it, it's not doing the spammer any good either <g>

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...