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
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 wrote:
>
> Hi list,
> any news
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 wrote:
So, let me do a straigth question:
Il 30-11-2015 23:23 Timo Sirainen ha scritto:
On 30 Nov 2015, at 17:48, Gionatan Danti wrote:
Hi Timo,
glad to know it is in your TODO list ;)
It's been for many years.
Any rough ETA on that?
Right now it doesn't seem likely to be developed anytime soon.
Thank you anyway :)
It let me
On 30 Nov 2015, at 17:48, Gionatan Danti wrote:
>
> Hi Timo,
> glad to know it is in your TODO list ;)
It's been for many years.
> Any rough ETA on that?
Right now it doesn't seem likely to be developed anytime soon.
> Thanks.
>
> On 30/11/2015 14:23, Timo Sirainen wrote:
>> On 30 Nov 2015,
Hi Timo,
glad to know it is in your TODO list ;)
Any rough ETA on that?
Thanks.
On 30/11/2015 14:23, Timo Sirainen wrote:
On 30 Nov 2015, at 10:21, Gionatan Danti wrote:
So, let me do a straigth question: is someone using dovecot/LMTP with
hardlinking? To me, this seems a _very_ important f
On 30 Nov 2015, at 10:21, Gionatan Danti 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.
Hard
Hi all,
I have some updates on the hard-link discussion.
First, let me explain that I installed a test machine with CentOS 7.1
and dovecot/pigeonhole version 2.2.10-4 and the results where identical
on what I had on CentOS 6.7 and dovecot 2.0.9-19
The bottom line is that hardlinking works onl
centos 7.x is latest, so if you need help upgrade make a bug report to
centos, not waste your time here since you choiced a precompiled
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
On November 26, 2015 3:28:22 PM Gionatan Danti wrote:
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
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.el
Il 14-07-2015 14:44 Gionatan Danti ha scritto:
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)?
Dear list,
sorry if I
Am Dienstag, den 14.07.2015, 12:26 +0200 schrieb Steffen Kaiser:
> On Tue, 14 Jul 2015, Gionatan Danti wrote:
> > On 14/07/15 08:17, Steffen Kaiser wrote:
> > > On Mon, 13 Jul 2015, Gionatan Danti wrote:
> > >
> > > > On the other hand, private (per-user) sieve file works without
> > > > interferi
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 14 Jul 2015, Gionatan Danti wrote:
On 14/07/15 08:17, Steffen Kaiser wrote:
On Mon, 13 Jul 2015, Gionatan Danti wrote:
On the other hand, private (per-user) sieve file works without
interfering with hardlinks. In a similar manner, disablin
On 14/07/15 08:17, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Jul 2015, Gionatan Danti wrote:
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 multi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Jul 2015, Gionatan Danti wrote:
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.
Doe
/07/15 11:10, Javier Miguel RodrÃguez wrote:
Search about "single instance storage dovecot". This is what you need.
Regards
Javier
On 27/06/2015 18:18, Gionatan Danti wrote:
Hi all,
I have some questions about hardlinks, alternate storage and
compression. I already scanned the list f
that, using Dovecot LMTP server, they
achieved what I want (one messagge, multiple hardlinks), but I am
_already_ using LMTP with no avail...
Regards.
On 27/06/15 18:18, Gionatan Danti wrote:
Hi all,
I have some questions about hardlinks, alternate storage and
compression. I already scanned the
_already_ using LMTP with no avail...
Regards.
On 27/06/15 18:18, Gionatan Danti wrote:
Hi all,
I have some questions about hardlinks, alternate storage and
compression. I already scanned the list for related information and I
have an idea of how things works, but I would like to have a definite
Hi all,
I have some questions about hardlinks, alternate storage and
compression. I already scanned the list for related information and I
have an idea of how things works, but I would like to have a definite
answer.
System spec:
- CentOS 6.6 x64
- dovecot-2.0.9-8.el6_6.4.x86_64 RPM package
21 matches
Mail list logo
