[SpamCop-List] Re: URL fails to parse.

[Glenn Daniels]

"Redstone" wrote:
...
> Funny thing is that it seems to happen on this single type of spam.

This is going on now for months, and, yes, it seems
always to be this vendor's spamitems that seem to
yank the parser's chain. I have a suspicion that the
items are contaminated, as by having embedded
"smileys" that throw an error flag when the parser
decodes the b64, or some other contaminant such
as "fuzzfuzzfuzzfuzz" tacked onto the end of the
b64 segments.

Whatever the "trick" is, no-one seems to care that
the spamvending URLs don't get reported, and
that is of concern for those of us who are receiving
several hundred of these items or more monthly.
I don't care that there are no reports to the
unresponsive ISPs for these sites. I do care that
these items don't contribute to spamvending
blocklists as there are inordinate numbers
involved. Since February, these items have
comprised nearly half of my spam, and there
is no sign of any letting up.

Although I "see" a fair bit of spam, at least 90%
is "tagged" by SpamPal and ignored. I do SpamCop
report the untagged items, and it flusters that there
is no option for simply reporting the spamvending
URL without regard to whether it happens to
resolve in the particular instant that it goes through
parser. With some spamitems, it is very typical
to find URLs that resolve one day and don't
the next, then pop up resolving somewhere else
the next day.

Personally, I would just as soon the parser
resolved none of the URLs as I don't happen
to think the spamvending ISPs have a right to
know just how many millions of spamitems
are being reported for their pet spamvendors.
I would prefer that they be taken by surprise
when they are denied the advantage of their
resources for their abuses of them. But it grates
when these spamitems, allegedly sent by/for
"World RX Direct" seem not to register as
unwelcome.

</rant>
Cheers,
Glenn