I'm seeing the same thing that others are seeing. Sometimes, the spamvertised URL is flagged ("LART"d ?): Resolving link obfuscation http://www.ch00s3.com/gone.asp host www.ch00s3.com (checking ip) = 220.127.116.11 host 18.104.22.168 (getting name) no name http://www.ch00s3.com/sign.asp Tracking link: http://www.ch00s3.com/gone.asp [report history] Resolves to 22.214.171.124 Routing details for 126.96.36.199 [refresh/show] Cached whois for 188.8.131.52 : ipanm[at]heinfo.net abuse[at]cnc-noc.net ... Please make sure this email IS spam: But moments later, the same URL is ignored (from separate spam with same spamvertised URL, which has the exact same message Body with a different person's name in the message Body): Resolving link obfuscation http://www.ch00s3.com/gone.asp http://www.ch00s3.com/sign.asp Please make sure this email IS spam: As you can see from the first example, the system correctly identified the first URL, but ignored the second URL. In the second example, both URLs are ignored. Also, as with the others, 10-20 refreshes eventually triggers the processing of the spamvertised URLs. I've read through this thread and the other suggested threads, but I'm not sure if this is a parsing issue (the BODY is plain text), a load balancing issue, a bonus-but-not-supported SC feature, or another issue suggested in these threads. I do know that I started seeing this several months ago, about the time this thread was started. This is less a requrest for help than a datapoint to help resolve the unreported URL issue. This is a particularly aggressive spammer (6-10 identical spams per day always relayed through different accounts) that I would really like to have out of my inbox.