search for: before_siev

Displaying 6 results from an estimated 6 matches for "before_siev".

Did you mean: before_sieve
2020 Jul 10
1
Per-user sieve_before settings?
...com context, with a corresponding single email on aaa at newdomain.com). However, I would avoid manipulating the already present per-user file (roundcube.sieve), as I need to add my custom rules on top of that file. Moreover, users would be able to disable the redirect filter. Using a per-user before_sieve filter file seems the right solution, *if* it works using multiple files rather than a single global one. If not, do you have any other suggestion/approach to share? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti at assyoma.it - info at assyoma.i...
2015 Nov 27
2
[g.danti@assyoma.it: Re: Questions about hardlinks, alternate storage and compression]
...recompiled > problem, 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 / C...
2015 Jul 14
1
Questions about hardlinks, alternate storage and compression
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
2015 Nov 30
0
Questions about hardlinks, alternate storage and compression]
...eporting 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 s...
2015 Nov 26
2
[g.danti@assyoma.it: Re: Questions about hardlinks, alternate storage and compression]
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
2015 Jul 13
2
Questions about hardlinks, alternate storage and compression
...backup 2) only the 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 me...