Op 14-4-2016 om 12:08 schreef Matthias Lay:> On Thu, 7 Apr 2016 15:44:04 +0200 > Stephan Bosch <stephan at rename-it.nl> wrote: > > >> - Recently, I implemented support for the "imapsieve" extension in >> Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785). >> This is now in the Pigeonhole master branch. This allows running >> Sieve scripts at IMAP activity, rather than at delivery. There are >> also facilities for the familiar sieve_before/sieve_after >> administrator scripts. The documentation is currently only in th > > this sounds great! > I guess this will work with dovecot hardlinks on sieve copying in > contrast to lda sieve?I am not sure what you mean exactly. Can you clarify? Regards, Stephan.
On Thu, 14 Apr 2016 12:22:22 +0200 Stephan Bosch <stephan at rename-it.nl> wrote:> > I am not sure what you mean exactly. Can you clarify? >sure, at the moment, if I am using a script like this fileinto :copy "myspecialplace" in lda sieve, the hardlinking is not working the mail gets duplicated on the FS, as far as I can see. So if the sieve is acting on an already saved mail, I guess it would be hard linked? Regards Matze
Op 14-4-2016 om 12:46 schreef Matthias Lay:> On Thu, 14 Apr 2016 12:22:22 +0200 > Stephan Bosch <stephan at rename-it.nl> wrote: > > >> I am not sure what you mean exactly. Can you clarify? >> > > sure, > > at the moment, if I am using a script like this > > fileinto :copy "myspecialplace" > > in lda sieve, the hardlinking is not working the mail gets duplicated on > the FS, as far as I can see. > > So if the sieve is acting on an already saved mail, I guess it would be > hard linked?Not sure. I should test that. As far as I know, Dovecot does that implicitly if possible. Regards, Stephan.