Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el and Procmail splitting strategy?
Date: Sat, 05 Apr 2003 08:42:38 -0500	[thread overview]
Message-ID: <m3fzox2h81.fsf@heechee.beld.net> (raw)
In-Reply-To: <uy92syf32.fsf@coas.oregonstate.edu> (Jody Klymak's message of "Wed, 02 Apr 2003 09:38:41 -0800")

On Wed, 02 Apr 2003, jklymak@coas.oregonstate.edu wrote:
> I split on my IMAP server using procmail.  But I get spam in both my
> Inbox and on of the mailboxes I procmail into, lets call one of them
> "bbdb."  What is the best strategy for cleaning this up using
> spam.el?

Hmm, spam.el assumes a single incoming point (with spam-split).  Have
you tried making nnimap-split-inbox a list of strings?  That would
defeat your procmail splitting, of course.

> The following works great for my Inbox.  But, of course, doesn't do
> anything for "bbdb".  
> (require 'spam)
> (setq
>   nnimap-split-rule 'nnimap-split-fancy
>   nnimap-split-inbox "INBOX"
>   nnimap-split-fancy '(|
> 		      (: spam-split)
> 		      ;; default mailbox
> 		      "mail/Inbox.spam"))
> 
> I'd prefer to be able to split using procmail on the server, but I
> guess I'd like gnus to check for spam when it enters a group?
> 
> If its not doable, thats fine.  I'll split in gnus.

Well, I was thinking of a 'respool spam/ham process destination, as
suggested before, which would resubmit the spam/ham mail to the spool
process from any mailbox.  Would that work for you?

I think it would be easier in the end to keep splitting on the client
side with spam.el.

Ted




  reply	other threads:[~2003-04-05 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 17:38 Jody Klymak
2003-04-05 13:42 ` Ted Zlatanov [this message]
2003-04-14 19:49   ` Jody Klymak
2003-04-15 17:48     ` Ted Zlatanov

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=m3fzox2h81.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).