From: Chris Green <cmg@sourcefire.com>
Subject: Re: Spam Management When Using nnimap
Date: Thu, 15 May 2003 17:05:35 -0400 [thread overview]
Message-ID: <m365obhqe8.fsf@radon.sfeng.sourcefire.com> (raw)
In-Reply-To: <76smrgc6of.fsf@newjersey.ppllc.com> (Jake Colman's message of "Thu, 15 May 2003 16:10:24 -0400")
Jake Colman <colman@ppllc.com> writes:
> So what now? Can the techniques discussed in the Info manual be applied to
> an imap situation? If so, how?
>
http://lifelogs.com/spam/spam.html seems to be the best tutorial for
this.
<ramble>
What I've not come to grips with yet is how to handle the concept of
an "incoming split folder" with multiple independent readers.
It used to make more sense to me when /var/spool/mail/cmg was the
incoming data and I wouldn't read it until it was filed away
somewhere. Now gnus+spam.el+nnimap wants that model with IMAP but my
other clients just want to peek at the INBOX.
</ramble>
--
Chris Green <cmg@sourcefire.com>
Chicken's thinkin'
next prev parent reply other threads:[~2003-05-15 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 20:10 Jake Colman
2003-05-15 21:05 ` Chris Green [this message]
2003-05-15 21:19 ` Jake Colman
2003-05-16 16:43 ` David Z Maze
2003-05-16 19:10 ` Jake Colman
2003-05-17 23:38 ` David Abrahams
2003-05-20 18:45 ` Ted Zlatanov
2003-05-20 18:41 ` Ted Zlatanov
2003-05-20 18:39 ` 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=m365obhqe8.fsf@radon.sfeng.sourcefire.com \
--to=cmg@sourcefire.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).