OK, I see. Let me attack the problem from another side: there is any
method to use some sort of message filtering (not necessarily Sieve)
without destroying hardlinking capability? Or are you all running
dovecot without hardlinking?
Thanks.
Il 08-06-2016 02:13 Timo Sirainen ha scritto:
It's a rather difficult change and also pretty low priority right now.
I'd be happy to explain the details to whoever wants to develop this,
but I wouldn't be surprised if it was still unimplemented a few years
from now.
On 07 Jun 2016, at 15:59, Gionatan Danti <g.da...@assyoma.it> wrote:
Hi list,
any news regarding hardlinks + sieve/pigeonhole setup?
Hardlinking seems a very important feature to me, and I would really
like to get it working.
Thanks.
On 30/11/2015 14:23, Timo Sirainen wrote:
On 30 Nov 2015, at 10:21, Gionatan Danti <g.da...@assyoma.it> wrote:
So, let me do a straigth question: is someone using dovecot/LMTP
with hardlinking? To me, this seems a _very_ important feature, and
I wonder if I am doing something wrong or if the feature
(hardlink+sieve) simply does not exists.
Hardlink+Sieve has never worked. The fix is a bit complicated. Here's
my TODO entry about it:
- remove mail_deliver_session after all, do all the stuff
transparently
by hooking into mailbox_copy().
- use this hook also to do the mail deduplication: 1) sort all
destination
users, 2) create mail_user only once for each user, 3)
remember in
src_mail the previously copied mail, 4) use that for
mailbox_copy()ing
to following recipients
- make sure this removes duplicate dbox mails when sieve saves
mail to
multiple mailboxes
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.da...@assyoma.it - i...@assyoma.it
GPG public key ID: FF5F32A8
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.da...@assyoma.it - i...@assyoma.it
GPG public key ID: FF5F32A8