Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam-stat and base64 encoded messages
Date: Thu, 05 Jun 2003 16:05:44 -0400	[thread overview]
Message-ID: <4nof1cguhz.fsf@holmes.bwh.harvard.edu> (raw)
In-Reply-To: <03of1dyplo.fsf@msgid.viggen.net> (Oystein Viggen's message of "Thu, 05 Jun 2003 09:01:55 +0200")

On Thu, 05 Jun 2003, oysteivi@tihlde.org wrote:
> Lately, I've been getting a lot of spam where the message is hidden
> as a base64 encoded text/plain or text/html part.  Since spam-stat
> works on the raw message it doesn't see any spammy words, so it
> won't classify the message as spam.
> 
> Would it be possible to add some hack to spam-stat for decoding
> these text parts?

Maybe the backend or Gnus should optionally decode it before spam-stat
ever sees the message in the splitting?  Right now it's not done for
performance.  I don't think spam-stat.el or spam.el should do what
logically is not their task.

Ted



  reply	other threads:[~2003-06-05 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  7:01 Oystein Viggen
2003-06-05 20:05 ` Ted Zlatanov [this message]
2003-06-06  2:02   ` Jesper Harder
2003-06-06  3:22     ` Ted Zlatanov
2003-06-06 15:30       ` Jesper Harder
2003-06-06 23:21         ` Oystein Viggen
2003-06-09  1:21           ` Jesper Harder
2003-06-09 20:06             ` Ted Zlatanov
2003-06-11 19:42               ` Jesper Harder
2003-08-02 21:17                 ` Alex Schroeder
2003-08-04  7:36                   ` Adam Sjøgren
2003-08-08  0:02                     ` Alex Schroeder
2003-06-06  1:59 ` Jesper Harder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4nof1cguhz.fsf@holmes.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).