I am happy to announce that I am developing bincdrop using the bincimap
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:
The sieve support comes from libcyrussieve
(http://people.su.se/~jelun/libcyrussieve/) which is a library I
developed to move out the sieve routins from cyrus-imapd source into a
standalone library. It also includes a C++ interface and that is what
bincdrop will use. I also plan of adding support for other sieve
libraries when I get the time.
I will also make a filter class resembling the broker class so that you
can add multiple filtering backends.
To prevent spending unneeded amount of time on things I wanted to
discuss some issues here on this list.
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 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:
(ext being .sieve if its a sieve script etc)
And two suggestions regarding multiple filter files: