Re: bincdrop - a (courier) maildrop replacment

Hi, Jerry!

On Thu, 21 Jul 2005, [ISO-8859-1] Jerry Lundstr=F6m wrote:
>Hello all,
>I am happy to announce that I am developing bincdrop using the bincimap
>code.
>Bincdrop will use the depot and message/mime backend to deliver mail for
>users and will be able to filter mail using the mail filtering language:
>sieve (http://www.ietf.org/rfc/rfc3028.txt).
>First of all is ofcourse, do bincimap developers want this?
>The reason for this question is that I really want to upload bincdrop to
>bincimap.org when its in a beta/working stage and leave the "rights" to
>the community.

It sounds interesting. But by this, are you saying you would like an open
repository for it, or would you simply announce new versions on the binc
lists and have the files on binc's file areas?

How many LOC are there? Maybe we could merge it in? (just ideas)

>The other question is technically concerning where to put the filter
>files. Since maildrop uses $HOME/.mailfilter and $HOME/.mailfilter.d/*
>that is a very old approach and I was hoping to make the filter
>placments a lite more up-to-date.
>I suggest this when using a single file:
>   Maildir/bincdrop-filter.<ext>
>(ext being .sieve if its a sieve script etc)

That looks perfectly fine to me. It will also be consistent with
bincimap-cache. :-)

>And two suggestions regarding multiple filter files:
>   Maildir/bincdrop-filter.<nameXXX>.<ext>
>   ...
>   Maildir/bincdrop-filter.<nameXXX>.<ext>
>Or:
>   Maildir/bincdrop-filter.d/*
>I know that the last one wont work under IMAPdir depot.

I would prefer the first alternative; but if it's plain SIEVE, could all
=2Esieve files be seen as filters by bincdrop? So for example:

    Maildir/work.sieve
    Maildir/private.sieve

That would look less intrusive, opening up the possibility that other
programs can edit them safely..

>There is also a issue about what to call the files if/when they are
>compiled but that can be a new extension (sieve-bc sievec sbytecode
>whatever).

Here I would just check if there were any (un)written standards, and just
make a choice. So .sieve-bc or .sievec, sure. :-)

>The reason to place the files in the Maildir directory is that I also
>plan to extend the bincimapd with sieve support using this draft:
>http://www.cyrusoft.com/sieve/drafts/managesieve-04.txt .
>Feel free to mail comments about this and about libcyrussieve.

Well firstly thanks for the contribution! I know that SIEVE is a show
stopper for many mail admins. And it fits perfectly into 1.3. I'd like 1.4
to have a couple more punchlines than 1.2 has, as 1.2 is the plain-old
server that worked, works and always will work, and 1.4 would start off as
a server that covers most common requirements.

If you extend bincimapd to support SIEVE, I'll be more than interested in
seeing the sources and perhaps integrating them.

Andy :-)

--
Andreas Aardal Hanssen   | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP      |  "It is better not to do something
http://www.bincimap.org/ |        than to do it poorly."