From: Steve Allan <stevea@wrq.com>
Subject: Re: someone please help me write a regexp to stop this spam: å ñîïðîâîæäåíèå
Date: Mon, 30 Sep 2002 17:57:24 GMT [thread overview]
Message-ID: <u65wn9xal.fsf@wrq.com> (raw)
In-Reply-To: <ufzvriwpy.fsf@telestoconsulting.com>
Ed <ed@telestoconsulting.com> writes:
>Howdy all!
>
>Spam always sucks, but it particularly suck when I can't even identify
>the letters!
>
>Recently I have been getting a lot of spam from Russian and Korean
>sites which looks like this:
>
>å ñîïðîâîæäåíèå
I've found that filtering on content type catches most of the korean
spam (a trick I learned here some time ago). Here's what I have in my
split-fancy rules:
("Content-Type" "ks_c_5601-1987" "junk-mail")
("Content-Type" "euc-kr" "junk-mail")
--
-- Steve
************************************************************************
* WRQ has 21 years of experience providing integration software and
* services for host-intensive environments. To learn more about our
* Reflection and Verastream products, visit http://www.wrq.com/products/
************************************************************************
parent reply other threads:[~2002-09-30 17:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ufzvriwpy.fsf@telestoconsulting.com>]
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=u65wn9xal.fsf@wrq.com \
--to=stevea@wrq.com \
/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).