search for: after_siev

...roblem, reporting here 7s helpfull if you use dovecot compiled with > the latest version here, this migth be a unknown bug you then have > found, but not if you use precompiled problems, then report to the > maintainers of such software Hi, does it means that when you use before_sieve and after_sieve in your dovecot configuration the hard-linking part works? I don't need help to upgrade to CentOS 7.x, but before going this route I would understand if this is how dovecot/pigenhole are expected to work (don't use hardlinks) or if I misconfigured something. RedHat / CentOS are a very...

On 14/07/15 12:26, Steffen Kaiser wrote: > > You asked about "newer dovecot versions", v2.2 does so. > Fair enough :) So, with v2.2+ the hardlink approach is irremediably gone, at least with LMTP (and without relying to SiS)? -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti at assyoma.it - info at assyoma.it GPG public key ID: FF5F32A8

...helpfull if you use dovecot compiled with >> the latest version here, this migth be a unknown bug you then have >> found, but not if you use precompiled problems, then report to the >> maintainers of such software > > Hi, > does it means that when you use before_sieve and after_sieve in your > dovecot configuration the hard-linking part works? > > I don't need help to upgrade to CentOS 7.x, but before going this route > I would understand if this is how dovecot/pigenhole are expected to work > (don't use hardlinks) or if I misconfigured something. > &...

Il 26-11-2015 15:15 John R. Dennison ha scritto: > You are strongly encouraged to update that CentOS system. Current is > 6.7 (released some 3 months ago) and dovecot-2.0.9-19. Ouch! I copied outdated information from my old post. My current system _is_ CentOS 6.7 with dovecot dovecot-2.0.9-19.el6_7.2.x86_64 Sorry for the confusion. Still, the problems remain > If you find you need a

...he attachments, and not the entire messages, are deduped. Message-based hardlinks really exists for a reason. The good news is that I found _why_ they are not working: it depends from how dovecot and its sieve plugin (pigenhole) interact. Basically, if I define anything for the before_sieve and after_sieve variables, dovecot stops creating hardlinks for multiple copies of the same message. On the other hand, private (per-user) sieve file works without interfering with hardlinks. In a similar manner, disabling sieve also permits dovecot to create multiple hardlinks for a single message. Does som...

...I could figure it out, in that 1) I could then send to something more simple like <senderlocalpart>+saveoutgoing and use the "date" extension of sieve to generate the split. 2) Users could ultimately decide what to do them selves with this tag (and I could define a global "after_sieve" to throw it away. Unfortunately my reading of the fileinto extension is that the destination can only be a literal string and not a "computed" value based on the date. UNLESS anyone knows different? I would welcome any advice anyone could give me Thanks Alan Chandler