From: Colin Rafferty <craffert@spspme.ml.com>
Cc: (ding) GNUS Mailing List <ding@ifi.uio.no>
Subject: Re: [??] delete garbage
Date: 07 Aug 1996 11:51:00 -0400 [thread overview]
Message-ID: <ocrbugnura3.fsf@spssunp.spspme.ml.com> (raw)
In-Reply-To: Kai Grossjohann's message of 07 Aug 1996 16:08:09 +0200
"Kai" == Kai Grossjohann writes:
"Colin" == Colin Rafferty writes:
Colin> I am constantly getting mail that I consider garbage, but my
Colin> management thinks is necessary. I want to delete it
Colin> automatically. [...]
Colin> Does anyone know a way to trash these messages directly?
Colin> Would I have a faster time if I used an nnfolder on that
Colin> group?
Kai> I think there's a way, but it's DANGEROUS!
Kai> You could (carefully!) set up an nnmail-split-methods that matches all
Kai> mails *except* the trash ones. If there is no entry in
Kai> nnmail-split-methods for those mails, they will be quickly routed to
Kai> the bit bucket. I think.
I have done this. In fact, I realized that I could do this pretty
easily by switching to `nnmail-split-fancy' (which seems faster than
nnmail-split-methods). However, the function nnmail-split-methods
does not allow null lists.
For fancy splitting, it will post to the group list ("bogus"), and for
non-fancy splitting, it will just post to the last method (whether the
test matches or not).
By nature, I am a dangerous person. If I want to shoot myself in the
foot, I want Gnus to help me do it (or at least let me set a variable
to allow me to do it).
I am cross-mailing this to gnus-bug.
Gnus v5.2.25; nntp 4.0; nnml 1.0; nnfolder 1.0
XEmacs 19.14 [Lucid] (sparc-sun-solaris2.4) of Sun Jun 23 1996 on xemacs
--
Colin
next prev parent reply other threads:[~1996-08-07 15:51 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
1996-08-07 15:51 ` Colin Rafferty [this message]
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=ocrbugnura3.fsf@spssunp.spspme.ml.com \
--to=craffert@spspme.ml.com \
--cc=craffert@ml.com \
--cc=ding@ifi.uio.no \
/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).