Re: bincdrop - a (courier) maildrop replacment

Jeremy Kitchen <[email protected]> Fri, 22 Jul 2005 10:22:14 -0700
Newsgroups gmane.mail.imap.binc.devel
Organization GreyStar Solutions
Message-ID <[email protected]>
--nextPart1861646.Bi6UXPiTPt
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 22 July 2005 09:30 am, Peter Stuge wrote:
> On Fri, Jul 22, 2005 at 01:15:49PM +0200, Jerry Lundstr=F6m wrote:
> > >    Maildir/work.sieve
> > >    Maildir/private.sieve
> > >
> > >That would look less intrusive, opening up the possibility that
> > >other programs can edit them safely..
> >
> > That sounds like a good plan, I'll make it so.
>
> [..]
>
> > Well there isnt really any (un)written standard that says .sieve
> > either so.
>
> [..]
>
> > The only fear I have about extending sieve into bincimap is that the
> > draft managesieve-04.txt is OLD.
>
> Forgive my ignorance here guys, but how well is the IMAP client able
> to control this filtering-on-delivery?

clients that support sieve would connect to a sieve daemon and talk a proto=
col=20
to change their filter settings.

kmail is the only client I am aware of that supports sieve.. and I've never=
=20
used cyrus, so I'm not sure how WELL it supports it :)

> From the name I guess that's what said draft describes?

sieve is server-side filtering.... which .. with imap... is where all of yo=
ur=20
filtering should go :)

> Hmm, how would the filters be used? To automatically sort incoming=20
> mail into different folders?=20

yes, based on rules you can configure with a sieve-speaking MUA or a specia=
l=20
configuration utility.

> Again, sorry I don't know more about this. I'd appreciate a pointer
> somewhere or just a few lines describing how it fits into IMAP.

http://www.cyrusoft.com/sieve/ (google is your friend! :)

=2DJeremy

--nextPart1861646.Bi6UXPiTPt
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBC4StTyBTJv0gb9+IRAssKAJ9sU1z8tsAUgcfmMl9HvAIAPybCoACfTdfb
6UD8/CnUCo1JUyxaxk2GevQ=
=5oOG
-----END PGP SIGNATURE-----

--nextPart1861646.Bi6UXPiTPt--