Re: URI decoding problems?

posted to spamcop.spam and spamcop.help;  f/ups to spamcop.help

Sir Sorcerer wrote:
> This came from your URI page:
>
>
http://r.lycos.com/r/nk>_lhxplcvg_dllvnteriu/http:\/zajmpzbxypnn.net.svxwszd
> fhnzcxmjm0ogm5ywi0mdvmyzu3nwyz.closetoperffect.com

[posted url wrapped by my newsagent]

spamcop.spam is not a discussion group.

I don't see a good way to discuss your issue in a normal discussion
group like spamcop or spamcop.help, either.

In the future, if you want to discuss how spamcop deobfuscates a URL
found in a spam, IMO the best way to do it would be to submit the spam
in question into the parser, copy the tracking URL, and paste that URL
into a normal discussion group such as spamcop or spamcop.help.  You
could also paste the URL itself, as you did here, but that will subject
it to the adverse effects of your newsagent or the newsagent of
others -- which is sometimes not avoidable.  The tracker represents a
link to the entire spam, header and body, including the link, without
any adverse newsreader effects.

spamcop.spam was originally intended as a newsgroup for posting spams,
before the days in which a tracking url was able to contain the entire
spam.  The original or earlier tracking url/s only contained access to
the spam headers, so entire spams were posted into spamcop.spam to be
able to discuss a spambody issue.

spamcop.spam is no longer a good place to post a spam because of what
'contamination' and bending of the original spam takes place by the
newsagent, unless you have a compatible way to submit the spam into
spamcop.spam newsgroup by attaching it to your news message rather than
pasting it inline into the body where wrapping effects take over.

The other problem with spamcop.spam usage is that no spam is allowed in
the discussion groups and no discussion in the spam group.

-- 
Mike Easter
kibitzer, not SC admin