Gnus development mailing list
 help / color / mirror / Atom feed
From: Brad Howes <bhowes@cssun3.corp.mot.com>
Subject: Re: [??] delete garbage
Date: 07 Aug 1996 09:56:49 -0700	[thread overview]
Message-ID: <wjy91br2kvi.fsf@cssun3.corp.mot.com> (raw)
In-Reply-To: Richard Pieri's message of 07 Aug 1996 11:29:02 -0400

>>>> Thus spake 'Richard Pieri (ratinox@unilab.dfci.harvard.edu)':

 >>>>>> "KG" == Kai Grossjohann
 >>>>>> <grossjohann@charly.informatik.uni-dortmund.de> writes:

 KG> You could (carefully!) set up an nnmail-split-methods that matches
 KG> all mails *except* the trash ones.  If there is no entry in
 KG> nnmail-split-methods for those mails, they will be quickly routed to
 KG> the bit bucket.  I think.

 RP> A better, though untested, idea is to create a split method that matches
 RP> these messages, and make the directory where they will spool to a
 RP> symbolic link to /dev/null.
[snip]

I'm all for using elisp whenever possible, but for me its just too slow to slug
thru all of the mail I get in a 24 hour period. Situations like mine call for
procmail. With it, one can siphon off the crud from your incoming mail and save
it in a log file (which just may be /dev/null). Much faster than nnmail-split.

Brad
-- 
Brad Howes                          Motorola E-Mail ID: XBH001
EMT Development                     SMTP E-Mail: bhowes@cssun3.corp.mot.com
Motorola Corporate - MD H1780       Voice: 602 441 1522  Fax: 602 441 5455


  reply	other threads:[~1996-08-07 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-07 13:44 Colin Rafferty
1996-08-07 14:08 ` Kai Grossjohann
1996-08-07 15:29   ` Richard Pieri
1996-08-07 16:56     ` Brad Howes [this message]
1996-08-07 15:51   ` Colin Rafferty
1996-08-07 16:21     ` Per Abrahamsen
1996-08-08  9:50       ` Jan Vroonhof
1996-08-09  5:03 ` François Pinard

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=wjy91br2kvi.fsf@cssun3.corp.mot.com \
    --to=bhowes@cssun3.corp.mot.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).