--On 14. September 2011 09:36:57 -0400 Adam Tauno Williams
wrote:
Of course, I agree. I saw the date (2006) only after posting. I don't
understand why this distribution of Linux is using a so ancient version
of cyrus, that's very strange.
??? This is not a distribution package; its an Invoca
Quoting Denis BUCHER :
> ear Bron,
> Le 14.09.2011 11:13, Bron Gondwana a écrit :
>> On Wed, Sep 14, 2011 at 10:45:27AM +0200, Denis BUCHER wrote:
I think I've posted already here about this some years ago about this
problem and I'm disappointed that cyrus reconstruct seems to still have
On Wednesday, September 14, 2011 2:24 PM, "Denis BUCHER"
wrote:
> Dear Bron,
>
> Le 14.09.2011 11:13, Bron Gondwana a écrit :
> > On Wed, Sep 14, 2011 at 10:45:27AM +0200, Denis BUCHER wrote:
> >>> I think I've posted already here about this some years ago about this
> >>> problem and I'm disa
Quoting Denis BUCHER
> Dear Bron,
> Le 14.09.2011 11:13, Bron Gondwana a écrit :
>> On Wed, Sep 14, 2011 at 10:45:27AM +0200, Denis BUCHER wrote:
I think I've posted already here about this some years ago about this
problem and I'm disappointed that cyrus reconstruct seems to still have
Dear Bron,
Le 14.09.2011 11:13, Bron Gondwana a écrit :
> On Wed, Sep 14, 2011 at 10:45:27AM +0200, Denis BUCHER wrote:
>>> I think I've posted already here about this some years ago about this
>>> problem and I'm disappointed that cyrus reconstruct seems to still have
>>> the same bug. Although l
On 09/14/2011 11:51 AM, Simon Matter wrote:
>> Dear Jeroen,
>>
>> Le 14.09.2011 10:54, Jeroen van Meeuwen (Kolab Systems) a écrit :
I think I've posted already here about this some years ago about this
problem and I'm disappointed that cyrus reconstruct seems to still
have
the s
> Dear Jeroen,
>
> Le 14.09.2011 10:54, Jeroen van Meeuwen (Kolab Systems) a écrit :
>>> I think I've posted already here about this some years ago about this
>>> problem and I'm disappointed that cyrus reconstruct seems to still
>>> have
>>> the same bug.
>>
>> You wouldn't happen to have a ticket
On 09/14/2011 09:42 AM, Aleksander Machniak wrote:
> A bug or am I doing something wrong?
>
> C: A0005 ENABLE QRESYNC
> S: * ENABLED QRESYNC CONDSTORE
> S: A0005 OK Completed
> C: A0006 SELECT INBOX (QRESYNC (1309794587 944))
> S: * ENABLED QRESYNC CONDSTORE
> S: A0006 BAD Invalid QRESYNC parameter
On Wed, Sep 14, 2011 at 10:45:27AM +0200, Denis BUCHER wrote:
> > I think I've posted already here about this some years ago about this
> > problem and I'm disappointed that cyrus reconstruct seems to still have
> > the same bug. Although last time I was able to circumvent it, this time
> > I am le
Dear Jeroen,
Le 14.09.2011 10:54, Jeroen van Meeuwen (Kolab Systems) a écrit :
>> I think I've posted already here about this some years ago about this
>> problem and I'm disappointed that cyrus reconstruct seems to still
>> have
>> the same bug.
>
> You wouldn't happen to have a ticket in bugzill
On 14.09.2011 09:42, Denis BUCHER wrote:
> Dear all,
>
Hi Denis,
> I think I've posted already here about this some years ago about this
> problem and I'm disappointed that cyrus reconstruct seems to still
> have
> the same bug.
You wouldn't happen to have a ticket in bugzilla.cyrusimap.org abo
On 14.09.2011 10:26, Jeroen van Meeuwen (Kolab Systems) wrote:
> Notice how it is missing the necessary parentheses around the
> parameters when forwarding the QRESYNC command + parameters to the
> backend. I therefore think the issue is in or near
> http://git.cyrusimap.org/cyrus-imapd/tree/im
Le 14.09.2011 10:42, Denis BUCHER a écrit :
> Dear all,
>
> I think I've posted already here about this some years ago about this
> problem and I'm disappointed that cyrus reconstruct seems to still have
> the same bug. Although last time I was able to circumvent it, this time
> I am left out witho
Dear all,
I think I've posted already here about this some years ago about this
problem and I'm disappointed that cyrus reconstruct seems to still have
the same bug. Although last time I was able to circumvent it, this time
I am left out without any solution, and my users are very angry now !!!
On 14.09.2011 08:42, Aleksander Machniak wrote:
> A bug or am I doing something wrong?
>
Not sure ;-)
> C: A0005 ENABLE QRESYNC
> S: * ENABLED QRESYNC CONDSTORE
> S: A0005 OK Completed
> C: A0006 SELECT INBOX (QRESYNC (1309794587 944))
> S: * ENABLED QRESYNC CONDSTORE
> S: A0006 BAD Invalid QRESY
A bug or am I doing something wrong?
C: A0005 ENABLE QRESYNC
S: * ENABLED QRESYNC CONDSTORE
S: A0005 OK Completed
C: A0006 SELECT INBOX (QRESYNC (1309794587 944))
S: * ENABLED QRESYNC CONDSTORE
S: A0006 BAD Invalid QRESYNC parameter list in Select
I've got the same response for
C: A0006 SELECT I
16 matches
Mail list logo