On Aug 24, 2012, at 11:56 PM, Bron Gondwana wrote:
> On Sat, Aug 25, 2012, at 07:28 AM, Geoff Adams wrote:
>> On Aug 24, 2012, at 3:22 PM, Geoff Adams wrote:
>>
>>> * 3743 EXISTS
>>
>> I think I may have solved the problem. I created a new mailbox for the user,
>> used an IMAP client to copy th
On Sat, Aug 25, 2012, at 07:28 AM, Geoff Adams wrote:
> On Aug 24, 2012, at 3:22 PM, Geoff Adams wrote:
>
> > * 3743 EXISTS
>
> I think I may have solved the problem. I created a new mailbox for the user,
> used an IMAP client to copy the original 3743 messages into that mailbox, and
> then use
On Aug 24, 2012, at 3:22 PM, Geoff Adams wrote:
> * 3743 EXISTS
I think I may have solved the problem. I created a new mailbox for the user,
used an IMAP client to copy the original 3743 messages into that mailbox, and
then used a one-line shell script to convert the newer messages into mbox
f
On Aug 24, 2012, at 3:22 PM, Geoff Adams wrote:
> * 3743 EXISTS
I think I may have solved the problem. I created a new mailbox for the user,
used an IMAP client to copy the original 3743 messages into that mailbox, and
then used a one-line shell script to convert the newer messages into mbox
f
So, based on your expert investigation, I'm now going on the theory that most
of the "missing" messages are, in fact, expunged, and only the newer messages
since the upgrade are missing. I can correct that…
I've killed the master, copied the cyrus.* files for that mailbox from the
pre-upgrade s
On Aug 24, 2012, at 1:36 PM, Bron Gondwana wrote:
> And you didn't realise that in 2.4.x, the EXPUNGED records are
> retained in cyrus.index with a magic flag rather than copied to
> a separate cyrus.expunge file. This means that even though there
> are lots of files on the disk, what you're actu
On Aug 24, 2012, at 1:26 PM, Geoff Adams wrote:
> On Aug 24, 2012, at 1:17 PM, Bron Gondwana wrote:
>
>> Can I please have a copy of your imapd.conf as well.
>>
>> I _suspect_ at this stage that it's locking problems.
>
> That does seem likely. Attached is my imapd.conf.
I forgot to mention th
On Fri, Aug 24, 2012, at 10:26 PM, Geoff Adams wrote:
> On Aug 24, 2012, at 1:17 PM, Bron Gondwana wrote:
>
> > Can I please have a copy of your imapd.conf as well.
> >
> > I _suspect_ at this stage that it's locking problems.
>
> That does seem likely. Attached is my imapd.conf.
See my other
On Aug 24, 2012, at 1:17 PM, Bron Gondwana wrote:
> Can I please have a copy of your imapd.conf as well.
>
> I _suspect_ at this stage that it's locking problems.
That does seem likely. Attached is my imapd.conf.
- Geoff
imapd.conf
Description: Binary data
Cyrus Home Page: http://www.cy
On Fri, Aug 24, 2012, at 10:06 PM, Geoff Adams wrote:
> On Aug 24, 2012, at 5:40 AM, Bron Gondwana wrote:
>
> > Do you have a cyrus.index which has this issue which you're willing to
> > share with me? I can have a look at the actual data structures that way :)
>
> Thanks for the help. Sent sep
On Aug 24, 2012, at 5:40 AM, Bron Gondwana wrote:
> Do you have a cyrus.index which has this issue which you're willing to share
> with me? I can have a look at the actual data structures that way :)
Thanks for the help. Sent separately.
> Also - what does syslog say?
Syslog just shows this,
On Fri, Aug 24, 2012, at 12:16 PM, Geoff Adams wrote:
> I have recently upgraded from Cyrus imapd 2.3.16 to 2.4.16, and it would seem
> I have a subtle problem. One user noticed that he didn't receive any new mail
> since the upgrade. Sure enough, I found that, while he had 16322 message
> files
I have recently upgraded from Cyrus imapd 2.3.16 to 2.4.16, and it would seem I
have a subtle problem. One user noticed that he didn't receive any new mail
since the upgrade. Sure enough, I found that, while he had 16322 message files
in his inbox (*. files) and growing as new mail came in, sele
13 matches
Mail list logo
