From: John Buttery <john@io.com>
To: zsh-users@sunsite.dk
Subject: Re: Please remove this spamming asshole <moonjh1@hanmail.net>
Date: Wed, 19 Feb 2003 05:49:11 -0600 [thread overview]
Message-ID: <20030219114911.GF21085@io.com> (raw)
In-Reply-To: <3E53487C.1010508@uk.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
* Cosmo <cosmo@uk.ibm.com> [2003-02-19 09:03:56 +0000]:
> There are plenty of XXXX->html converters for all sorts of doc types
> but I'm not aware of a html->text converter - everyone seems hellbent
> on producing html even if just to be able to print the heading in
> *boldface*.
I'm not sure how resource-intensive this is -- I know it works fine
for my mail and I get over 100 messages a day, most of them spam -- but
I use lynx via procmail to convert text/html emails to text/plain (I
leave multipart ones intact).
If you want my personal opinion (and as the saying goes, everybody's
got one :p), any email with a content-type of text/html should be
stopped cold. If Hotmail is using it, well, their users might finally
have to feel 1/100th of the pain that their usage of that service
inflicts on the rest of the net. Note that text/html is not the same as
multipart, where at least normal mail clients can get at a plain text
version to display (even if we still have to deal with the overall
sluggishness of the Net that results from SMTP-ing around all that extra
HTML crap), although as you can probably guess I have no love lost with
that format either.
:0
* ^Content-type: text/html
{
:0 c
${MAILDIR}/inc/html-safetynet
:0 fb
|lynx -nopause -force_html -dump /dev/stdin
:0 afwh
|formail -i "Content-type: text/plain" -I "X-HTML-Strip: 1.0"
}
As a list maintainer, you'll probably want to remove that little
clause that writes a copy to the "html-safetynet" file. For everyone's
information, I have never once recovered a legitimate email from that
folder in the year I've been using this recipe, so I'm not sure why I
keep it around myself... Anyway, after running this recipe you'll wind
up with these three headers:
Old-Content-type: text/html
Content-type: text/plain
X-HTML-Strip: 1.0
The first is added by formail when it replaces the "Content-type"
header...it "backs up" the old one. The second, well duh. :p The
third one is just something I arbitrarily added so I could see at a
glance whether an email had been "filtered"...just in case a legit one
ever came in and I for some reason needed to recover the original HTML
version.
--
------------------------------------------------------------------------
John Buttery
(Web page temporarily unavailable)
------------------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-19 11:49 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 [this message]
2003-02-19 9:09 ` Zefram
2003-02-19 9:32 ` Seth Kurtzberg
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=20030219114911.GF21085@io.com \
--to=john@io.com \
--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).