* email builder :
>
> >> 1. we use a lot of maildrop "features" that are impossible in
>
> >> sieve
> >
> > We're calling deliver from maildropc
>
> Ah, so this is actually sane enough of an idea that someone
> really uses it? Is the performance reasonable? Bounces or
> deferred mail all w
>> 1. we use a lot of maildrop "features" that are impossible in
>> sieve
>
> We're calling deliver from maildropc
Ah, so this is actually sane enough of an idea that someone
really uses it? Is the performance reasonable? Bounces or
deferred mail all work as expected? What syntax did you
* email builder :
> 1. we use a lot of maildrop "features" that are impossible in sieve
We're calling deliver from maildropc
> 2. would love to try dbox
For that you'd need to call deliver from maildropc
> 3. we use IMAP/Maildir++ quotas (looks like with a little finesse
> it's possible to g
> We're considering a move from Courier to Dovecot. So far, looks like
> it's not too bad, but the most challenging obstacle is what to do about
> our local delivery. Factors:
>
> 1. we use a lot of maildrop "features" that are impossible in sieve
>
> without piping to an external program (w
We're considering a move from Courier to Dovecot. So far, looks like
it's not too bad, but the most challenging obstacle is what to do about
our local delivery. Factors:
1. we use a lot of maildrop "features" that are impossible in sieve
without piping to an external program (would rather not
