Gnus development mailing list
 help / color / mirror / Atom feed
From: Timothy Brown <tim@gwyn.tux.org>
Subject: Another reason for cross-method splitting
Date: Wed, 2 Jun 2004 12:34:44 -0400	[thread overview]
Message-ID: <20040602123444.A24872@gwyn.tux.org> (raw)

One of the main functionalities i'm missing right now in my setup is a hybrid
approach.  We talked a little while ago in some of the spam threads (thanks
again for everyone's help) about cross-server or cross-method splitting.
In my current setup, I don't have control over one of the mail servers
I get mail from, so i'd like to procmail the messages so as to run them
through DSPAM, or similar methods.  Unfortunately, I also need to be able
to have the messages available on the IMAP server.  Normally this would
imply doing something such as an IMAP proxy or synchronizer to keep the
messages equal in state, but wouldn't it be nice if:

	* messages were pulled down via fetchmail/procmail
        * messages were processed accordingly (Spamassassin, DSPAM)
	* messages were thrown into gnus
        * gnus split the messages back into their relevant folders
	  after reading the processed headers, or expired the messages
	  after being read into an IMAP "catchall" mailbox

So there's another argument.

Tim




                 reply	other threads:[~2004-06-02 16:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040602123444.A24872@gwyn.tux.org \
    --to=tim@gwyn.tux.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).