[SC-Help] Re: Embedded images in spam not parsing

[Mike Easter]

Posted to .spam and .help, f/ups to .help

nighthawke wrote:
> Been getting spam that has no text in body, just a image.
> Ideas on how to deal with it?

That is a stock spam which has no links in the body anyway, even in the
graphic -- all that is reported or reportable is the spamsource, which
SC offers to do.


Posting a spam in spamcop.spam is no longer a good way to talk about it.
The proper way is to submit the spamitem to the parser and copy the
tracker and paste it into the message like this...

http://www.spamcop.net/sc?id=z886176374zc7aaf7af28290083688330b31690d8baz

Finding links in message body
Recurse multipart:
   Recurse multipart:
      Parsing text part
      Parsing HTML part
      No html links found, trying text parse
   Ignored image/gif part
no links found

Report Spam to:
Re: 83.19.92.210 (Administrator of network where email originates)
   To: abuse at tpnet.pl (Notes)
   To: abuse at telekomunikacja.pl (Notes)
   To: webmaster at telekomunikacja.pl (Notes)
   To: postmaster at telekomunikacja.pl (Notes)

<open proxy source, report cancelled>


... which is a tracker for your spamitem and demonstrates perfectly
exactly what the parser does with the item, and it also provides access
to the complete spam in the 'view entire message' section.  After
parsing, the report can be submitted or cancelled depending on whether
it has been reported or not.

When you put a spam into this newsgroup -- first of all it is the wrong
group to be discussing a spam.  .spam is not a discussion group, it is a
'junk' group which used to be used to post spam, since raw spam is not
allowed in the discussion groups spamcop or .help.

Second of all it bends or breaks the spam formatting.  So then if we
want to see what the result of the parser is on the spamitem, it has to
be reconfigured or formatted by hand -- which is tedious and
unnecessary.  It didn't use to be bent or broken until you put it into
your news message and then your newsreader started wrapping its lines
and ruining its header and body by spurious returns for the EOLs.  No
good.

Don't post spams in .spam.  Don't post spams in the discussion groups.
Don't discuss spam in .spam.  Discuss spam in the discussion groups and
give access to the spam with a tracker as above.


-- 
Mike Easter
kibitzer, not SC admin