From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] processing mail bodies
Date: Thu, 5 Feb 2009 10:26:39 -0500 [thread overview]
Message-ID: <27554a6d94230ba1f752fa6009fdd7c2@quanstro.net> (raw)
In-Reply-To: <eda75d8cb509e48c3bf306a4b00a2bad@quintile.net>
> FWIW I have several sources of mail which have large, unnecessary disclaimers,
> adverts, signatures etc on them. I have a serise of test in /mail/box/steve/pipeto
> along the lines of:
>
> if (grep -s 'Forum Subscription New Topic Notification' $D/subject){
> bin/powerboard $D | $BIN/deliver $RECIP $D/from $MBOX
> exit 0
> }
>
> This runs /mail/box/steve/bin/XXX which contains sed scripts to
> remove the rubbish. In this case (powerboard), I only receive a link
> to the relevant bullitin board message, the script uses hget to pull
> down the actual text.
might it be better for ned or Mail to do this?
- erik
prev parent reply other threads:[~2009-02-05 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 15:22 Steve Simon
2009-02-05 15:26 ` erik quanstrom [this message]
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=27554a6d94230ba1f752fa6009fdd7c2@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).