zsh-users
 help / color / mirror / code / Atom feed
From: Seth Kurtzberg <seth@cql.com>
To: Zefram <zefram@fysh.org>, Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-users@sunsite.dk
Subject: Re: Please remove this spamming asshole <moonjh1@hanmail.net>
Date: Wed, 19 Feb 2003 02:32:34 -0700	[thread overview]
Message-ID: <200302190232.34815.seth@cql.com> (raw)
In-Reply-To: <20030219090918.GA585@fysh.org>

A quick check in my spam directory shows that some spam messages are also 
multipart.  The majority (in my sample which may or may not be 
representative) have only text/html, but a significant number also have plain 
text.

If it is practical, it would be a good idea to automatically extract plain 
text only for senders who are part of the list.  If that can't be done, then 
send a bounce message to the sender.  If it isn't a spam message, the sender 
can resend in plain text.

On Wednesday 19 February 2003 02:09 am, Zefram wrote:
> Oliver Kiddle wrote:
> >The spams getting through seem to be mostly just those with charsets of
> >euc-kr, ks_c_5601-1987 and GB2312 and content-types of text/html.
>
> I can only think of one occasion when I've received a non-spam email
> with content type text/html -- that alone is a good spam indicator.
> There's also a huge number of people that have the poor taste to send
> a multipart of text/plain and text/html, which also deserves to be
> discouraged but isn't a good spam indicator.
>
> -zefram

-- 
Seth Kurtzberg
M. I. S. Corp.
480-661-1849
seth@cql.com


  reply	other threads:[~2003-02-19  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030215183407.55965.qmail@web13707.mail.yahoo.com>
2003-02-19  8:21 ` Oliver Kiddle
2003-02-19  9:03   ` Cosmo
2003-02-19 11:49     ` John Buttery
2003-02-19  9:09   ` Zefram
2003-02-19  9:32     ` Seth Kurtzberg [this message]
2003-02-19 20:56   ` William Park

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=200302190232.34815.seth@cql.com \
    --to=seth@cql.com \
    --cc=okiddle@yahoo.co.uk \
    --cc=zefram@fysh.org \
    --cc=zsh-users@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).