Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
On Fri, Oct 23, 2015 at 07:38:56PM -0400, Matt Elson wrote: > > So the exact text after the OK response doesn't matter, but it MUST > > be SP followed by at least 1 TEXT-CHAR. > > > > This is pretty easy to patch in 2.3.x if you're forced to remain > > there for reasons. It is, of course, fixed in later versions. > > > > Bron. > > > > > > I'm seeing this issue in my environment.. I think. I'm only *fairly* > sure - I see clients that are identifying themselves as 10.11 causing > lots of entries showing up in the sync log and a whole lot of index > churning on.. usually smaller folders, luckily. I've been trying to > track down a test machine to validate, but resources are quite limited > where I am. > > But I'm a bit confused about the current working theory as to what's > causing Mail.app to go into its strange loop. > > My Cyrus (RedHat provided 2.3.16-13.el6_6 with a very minor local patch) > responds to EXPUNGE with " OK COMPLETED" as near as I can tell.. > which seems spec compliant if I understand the above. > > * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID > MUPDATE=mupdate://redacted.example.com/ AUTH=GSSAPI AUTH=PLAIN > AUTH=LOGIN SASL-IR COMPRESS=DEFLATE] redacted.example.com Cyrus IMAP > Murder v2.3.16-Fedora-RPM-2.3.16-13.el6_6 server ready > A0001 login REDACTED PASSWORD > A0001 OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID > MUPDATE=mupdate://redacted.example.com/ LOGINDISABLED AUTH=GSSAPI > AUTH=PLAIN AUTH=LOGIN COMPRESS=DEFLATE ACL RIGHTS=kxte QUOTA > MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN > MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT > THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE LISTEXT > LIST-SUBSCRIBED X-NETSCAPE URLAUTH] User logged in > A0002 SELECT Trash > * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) > * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] > * 4560 EXISTS > * 0 RECENT > * OK [UNSEEN 1] > * OK [UIDVALIDITY 1347582296] > * OK [UIDNEXT 6437] > * OK [NOMODSEQ] Sorry, modsequences have not been enabled on this mailbox > * OK [URLMECH INTERNAL] > A0002 OK [READ-WRITE] Completed > A0003 idle > + idling > done > A0003 OK Completed > A0004 EXPUNGE > * 4560 EXISTS > * 0 RECENT > A0004 OK Completed > > > In fact a 2.4.18 install I'm building (I'm using this issue as an excuse > to prioritize a long time coming upgrade) seems to respond to expunge in > the same way. > > > * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE > MUPDATE=mupdate://redacted.example.com/ STARTTLS AUTH=LOGIN AUTH=PLAIN > AUTH=DIGEST-MD5 SASL-IR] redacted.example.com Cyrus IMAP Murder > v2.4.18-Invoca-RPM-2.4.18-1.el7.centos server ready > A0001 login redacted redacted > A0001 OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxte QUOTA > MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN > MULTIAPPEND BINARY CATENATE CONDSTORE SORT SORT=MODSEQ SORT=DISPLAY > THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE WITHIN SCAN XLIST > URLAUTH X-NETSCAPE MUPDATE=mupdate://redacted.example.com/ LOGINDISABLED > COMPRESS=DEFLATE IDLE] User logged in > SESSIONID= > A0002 SELECT Trash > * 0 EXISTS > * 0 RECENT > * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) > * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok > * OK [UIDVALIDITY 144503] Ok > * OK [UIDNEXT 1] Ok > * OK [HIGHESTMODSEQ 1] Ok > * OK [URLMECH INTERNAL] Ok > A0002 OK [READ-WRITE] Completed > A0003 idle > + idling > done > A0003 OK Completed > A0004 EXPUNGE > A0004 OK Completed > > (And fastmail's IMAP responds with a OK Completed, and I assume it > represents the most up to date Cyrus :P) > > Am I misunderstanding the theoretical issue? My IMAP-fu is a little > rusty these days and I'm a bit bleary eyed so apologies in advance if > I'm missing something obvious - I'm just testing by typing the commands > in raw since imaptest is panicking on me and I've not had time to sort > that out (though my Thunderbird debug log also shows an OK Completed as > a repsonse). > > It does seem from one of the trace logs from the Apple discussion that > there is a version of Cyrus that responds with just OK, but.. it's not > all 2.3.x 's at the very least :P. > > Sorry again if this noise and thanks in advance for any clarification > someone can give. > > Matt > Hi Matt, I just confirmed your result. It looks like Redhat had patched that in there release. I will try and get some El Capitan telemetry on Monday and see what it is doing. Regards, Ken Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
On Fri, Oct 23, 2015 at 09:37:28AM +1100, Bron Gondwana wrote:
> >
> > If they are thinking that the example in the RFC is the specification, they
> > are
> > not correct. The IMAP server responses to determine completion of the
> > EXPUNGE
> > command are "OK" for a completed EXPUNGE, "NO" for a failure, and "BAD for
> > unknown
> > command or invalid arguments. Everything after those words are not germane
> > to
> > whether or not the command completed. The tag is what links the OK to the
> > EXPUNGE
> > command and not the "EXPUNGE completed". Sigh, they had it right and now it
> > is
> > broken.
>
> Actually, the ImapTest command complained about this too:
>
> http://imapwiki.org/ImapTest
>
> >From RFC3501:
>
> response-tagged = tag SP resp-cond-state CRLF
>
>
> resp-cond-state = ("OK" / "NO" / "BAD") SP resp-text
> ; Status condition
>
> resp-text = ["[" resp-text-code "]" SP] text
>
> text= 1*TEXT-CHAR
>
> So the exact text after the OK response doesn't matter, but it MUST be SP
> followed by at least 1 TEXT-CHAR.
>
> This is pretty easy to patch in 2.3.x if you're forced to remain there for
> reasons. It is, of course, fixed in later versions.
>
> Bron.
>
Hi Bron,
I don't suppose you have a patch? If not, I will work one up.
Regards,
Ken
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
Sorry, in phone so not able to look at code today. So from this it appears that calling expunge frequently will still happen. Recent 2.4 and later will be the same, but expunge with no changes to make is cheap on more recent Cyrus and won't even cause a sync log. On Sat, Oct 24, 2015, at 10:38, Matt Elson wrote: > > So the exact text after the OK response doesn't matter, but it MUST > > be SP followed by at least 1 TEXT-CHAR. > > > > This is pretty easy to patch in 2.3.x if you're forced to remain > > there for reasons. It is, of course, fixed in later versions. > > > > Bron. > > > > > > I'm seeing this issue in my environment.. I think. I'm only *fairly* > sure - I see clients that are identifying themselves as 10.11 causing > lots of entries showing up in the sync log and a whole lot of index > churning on.. usually smaller folders, luckily. I've been trying to > track down a test machine to validate, but resources are quite limited > where I am. > > But I'm a bit confused about the current working theory as to what's > causing Mail.app to go into its strange loop. > > My Cyrus (RedHat provided 2.3.16-13.el6_6 with a very minor local patch) > responds to EXPUNGE with " OK COMPLETED" as near as I can tell.. > which seems spec compliant if I understand the above. > > * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID > MUPDATE=mupdate://redacted.example.com/ AUTH=GSSAPI AUTH=PLAIN > AUTH=LOGIN SASL-IR COMPRESS=DEFLATE] redacted.example.com Cyrus IMAP > Murder v2.3.16-Fedora-RPM-2.3.16-13.el6_6 server ready > A0001 login REDACTED PASSWORD > A0001 OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID > MUPDATE=mupdate://redacted.example.com/ LOGINDISABLED AUTH=GSSAPI > AUTH=PLAIN AUTH=LOGIN COMPRESS=DEFLATE ACL RIGHTS=kxte QUOTA > MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN > MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT > THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE LISTEXT > LIST-SUBSCRIBED X-NETSCAPE URLAUTH] User logged in > A0002 SELECT Trash > * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) > * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] > * 4560 EXISTS > * 0 RECENT > * OK [UNSEEN 1] > * OK [UIDVALIDITY 1347582296] > * OK [UIDNEXT 6437] > * OK [NOMODSEQ] Sorry, modsequences have not been enabled on this mailbox > * OK [URLMECH INTERNAL] > A0002 OK [READ-WRITE] Completed > A0003 idle > + idling > done > A0003 OK Completed > A0004 EXPUNGE > * 4560 EXISTS > * 0 RECENT > A0004 OK Completed > > > In fact a 2.4.18 install I'm building (I'm using this issue as an excuse > to prioritize a long time coming upgrade) seems to respond to expunge in > the same way. > > > * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE > MUPDATE=mupdate://redacted.example.com/ STARTTLS AUTH=LOGIN AUTH=PLAIN > AUTH=DIGEST-MD5 SASL-IR] redacted.example.com Cyrus IMAP Murder > v2.4.18-Invoca-RPM-2.4.18-1.el7.centos server ready > A0001 login redacted redacted > A0001 OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxte QUOTA > MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN > MULTIAPPEND BINARY CATENATE CONDSTORE SORT SORT=MODSEQ SORT=DISPLAY > THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE WITHIN SCAN XLIST > URLAUTH X-NETSCAPE MUPDATE=mupdate://redacted.example.com/ LOGINDISABLED > COMPRESS=DEFLATE IDLE] User logged in > SESSIONID= > A0002 SELECT Trash > * 0 EXISTS > * 0 RECENT > * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) > * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok > * OK [UIDVALIDITY 144503] Ok > * OK [UIDNEXT 1] Ok > * OK [HIGHESTMODSEQ 1] Ok > * OK [URLMECH INTERNAL] Ok > A0002 OK [READ-WRITE] Completed > A0003 idle > + idling > done > A0003 OK Completed > A0004 EXPUNGE > A0004 OK Completed > > (And fastmail's IMAP responds with a OK Completed, and I assume it > represents the most up to date Cyrus :P) > > Am I misunderstanding the theoretical issue? My IMAP-fu is a little > rusty these days and I'm a bit bleary eyed so apologies in advance if > I'm missing something obvious - I'm just testing by typing the commands > in raw since imaptest is panicking on me and I've not had time to sort > that out (though my Thunderbird debug log also shows an OK Completed as > a repsonse). > > It does seem from one of the trace logs from the Apple discussion that > there is a version of Cyrus that responds with just OK, but.. it's not > all 2.3.x 's at the very least :P. > > Sorry again if this noise and thanks in advance for any clarification > someone can give. > > Matt > > > > > > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Bron Gondwana br...@fastmail.fm Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
> So the exact text after the OK response doesn't matter, but it MUST > be SP followed by at least 1 TEXT-CHAR. > > This is pretty easy to patch in 2.3.x if you're forced to remain > there for reasons. It is, of course, fixed in later versions. > > Bron. > > I'm seeing this issue in my environment.. I think. I'm only *fairly* sure - I see clients that are identifying themselves as 10.11 causing lots of entries showing up in the sync log and a whole lot of index churning on.. usually smaller folders, luckily. I've been trying to track down a test machine to validate, but resources are quite limited where I am. But I'm a bit confused about the current working theory as to what's causing Mail.app to go into its strange loop. My Cyrus (RedHat provided 2.3.16-13.el6_6 with a very minor local patch) responds to EXPUNGE with " OK COMPLETED" as near as I can tell.. which seems spec compliant if I understand the above. * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID MUPDATE=mupdate://redacted.example.com/ AUTH=GSSAPI AUTH=PLAIN AUTH=LOGIN SASL-IR COMPRESS=DEFLATE] redacted.example.com Cyrus IMAP Murder v2.3.16-Fedora-RPM-2.3.16-13.el6_6 server ready A0001 login REDACTED PASSWORD A0001 OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID MUPDATE=mupdate://redacted.example.com/ LOGINDISABLED AUTH=GSSAPI AUTH=PLAIN AUTH=LOGIN COMPRESS=DEFLATE ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE LISTEXT LIST-SUBSCRIBED X-NETSCAPE URLAUTH] User logged in A0002 SELECT Trash * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] * 4560 EXISTS * 0 RECENT * OK [UNSEEN 1] * OK [UIDVALIDITY 1347582296] * OK [UIDNEXT 6437] * OK [NOMODSEQ] Sorry, modsequences have not been enabled on this mailbox * OK [URLMECH INTERNAL] A0002 OK [READ-WRITE] Completed A0003 idle + idling done A0003 OK Completed A0004 EXPUNGE * 4560 EXISTS * 0 RECENT A0004 OK Completed In fact a 2.4.18 install I'm building (I'm using this issue as an excuse to prioritize a long time coming upgrade) seems to respond to expunge in the same way. * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE MUPDATE=mupdate://redacted.example.com/ STARTTLS AUTH=LOGIN AUTH=PLAIN AUTH=DIGEST-MD5 SASL-IR] redacted.example.com Cyrus IMAP Murder v2.4.18-Invoca-RPM-2.4.18-1.el7.centos server ready A0001 login redacted redacted A0001 OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY CATENATE CONDSTORE SORT SORT=MODSEQ SORT=DISPLAY THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE WITHIN SCAN XLIST URLAUTH X-NETSCAPE MUPDATE=mupdate://redacted.example.com/ LOGINDISABLED COMPRESS=DEFLATE IDLE] User logged in SESSIONID= A0002 SELECT Trash * 0 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UIDVALIDITY 144503] Ok * OK [UIDNEXT 1] Ok * OK [HIGHESTMODSEQ 1] Ok * OK [URLMECH INTERNAL] Ok A0002 OK [READ-WRITE] Completed A0003 idle + idling done A0003 OK Completed A0004 EXPUNGE A0004 OK Completed (And fastmail's IMAP responds with a OK Completed, and I assume it represents the most up to date Cyrus :P) Am I misunderstanding the theoretical issue? My IMAP-fu is a little rusty these days and I'm a bit bleary eyed so apologies in advance if I'm missing something obvious - I'm just testing by typing the commands in raw since imaptest is panicking on me and I've not had time to sort that out (though my Thunderbird debug log also shows an OK Completed as a repsonse). It does seem from one of the trace logs from the Apple discussion that there is a version of Cyrus that responds with just OK, but.. it's not all 2.3.x 's at the very least :P. Sorry again if this noise and thanks in advance for any clarification someone can give. Matt Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
On Thu, Oct 22, 2015 at 10:54:28PM +0200, Eric Luyten wrote: > On Thu, October 22, 2015 10:39 pm, k...@rice.edu wrote: > > On Thu, Oct 22, 2015 at 10:32:40AM -0400, bacon wrote: > > > >> Apple released OS 10.11.1 update yesterday. It shows that it includes, > >> > >> > >> - Fixes an issue where outgoing server information may be missing from > >> Mail > >> - Resolves an issue that prevented display of messages and mailboxes in > >> Mail > >> > >> > >> Does anyone know if this fixed the problem. I've asked my users not to > >> use Mail on El Capitan until this bug is fixed. > >> > >> Meanwhile, I'm working in my spare time to upgrade my cyrus-imapd on > >> RedHat Enterprise Linux 6 from the 2.3 series distributed by RedHat to > >> the 2.5 series which I'll have to build and maintain myself. That's an > >> ugly > >> job and one that I don't really want to do. > >> > >> Fred > >> > >> > > > > Hi Fred, > > > > > > It does not appear to have addressed the problem. We are trying to gather > > more information. > > > In > >https://discussions.apple.com/thread/7267399 > > someone states older Cyrus servers are returning a syntactically not quite > correct response to the EXPUNGE command but I'm having a hard time buying > this for an explanation. > > Oh, and someone in there asks for help to get the Apple bug report (22996765) > escalated. > > I think at our site we have reached the count of 100 (one hundred) El Capitan > Mail.app users. > > > Eric. > Hi Eric, If they are thinking that the example in the RFC is the specification, they are not correct. The IMAP server responses to determine completion of the EXPUNGE command are "OK" for a completed EXPUNGE, "NO" for a failure, and "BAD for unknown command or invalid arguments. Everything after those words are not germane to whether or not the command completed. The tag is what links the OK to the EXPUNGE command and not the "EXPUNGE completed". Sigh, they had it right and now it is broken. Regards, Ken > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
On Thu, October 22, 2015 10:39 pm, k...@rice.edu wrote: > On Thu, Oct 22, 2015 at 10:32:40AM -0400, bacon wrote: > >> Apple released OS 10.11.1 update yesterday. It shows that it includes, >> >> >> - Fixes an issue where outgoing server information may be missing from >> Mail >> - Resolves an issue that prevented display of messages and mailboxes in >> Mail >> >> >> Does anyone know if this fixed the problem. I've asked my users not to >> use Mail on El Capitan until this bug is fixed. >> >> Meanwhile, I'm working in my spare time to upgrade my cyrus-imapd on >> RedHat Enterprise Linux 6 from the 2.3 series distributed by RedHat to >> the 2.5 series which I'll have to build and maintain myself. That's an ugly >> job and one that I don't really want to do. >> >> Fred >> >> > > Hi Fred, > > > It does not appear to have addressed the problem. We are trying to gather > more information. In https://discussions.apple.com/thread/7267399 someone states older Cyrus servers are returning a syntactically not quite correct response to the EXPUNGE command but I'm having a hard time buying this for an explanation. Oh, and someone in there asks for help to get the Apple bug report (22996765) escalated. I think at our site we have reached the count of 100 (one hundred) El Capitan Mail.app users. Eric. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
On Thu, Oct 22, 2015 at 10:32:40AM -0400, bacon wrote: > Apple released OS 10.11.1 update yesterday. It shows that it includes, > > - Fixes an issue where outgoing server information may be missing from > Mail > - Resolves an issue that prevented display of messages and mailboxes in > Mail > > Does anyone know if this fixed the problem. I've asked my users not to > use Mail on El Capitan until this bug is fixed. > > Meanwhile, I'm working in my spare time to upgrade my cyrus-imapd on > RedHat Enterprise Linux 6 from the 2.3 series distributed by RedHat to > the 2.5 series which I'll have to build and maintain myself. That's an > ugly job and one that I don't really want to do. > > Fred > Hi Fred, It does not appear to have addressed the problem. We are trying to gather more information. Regards, Ken Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
On Fri, Oct 23, 2015, at 08:39, k...@rice.edu wrote:
> On Thu, Oct 22, 2015 at 10:54:28PM +0200, Eric Luyten wrote:
> > On Thu, October 22, 2015 10:39 pm, k...@rice.edu wrote:
> > > On Thu, Oct 22, 2015 at 10:32:40AM -0400, bacon wrote:
> > >
> > >> Apple released OS 10.11.1 update yesterday. It shows that it includes,
> > >>
> > >>
> > >> - Fixes an issue where outgoing server information may be missing from
> > >> Mail
> > >> - Resolves an issue that prevented display of messages and mailboxes in
> > >> Mail
> > >>
> > >>
> > >> Does anyone know if this fixed the problem. I've asked my users not to
> > >> use Mail on El Capitan until this bug is fixed.
> > >>
> > >> Meanwhile, I'm working in my spare time to upgrade my cyrus-imapd on
> > >> RedHat Enterprise Linux 6 from the 2.3 series distributed by RedHat to
> > >> the 2.5 series which I'll have to build and maintain myself. That's an
> > >> ugly
> > >> job and one that I don't really want to do.
> > >>
> > >> Fred
> > >>
> > >>
> > >
> > > Hi Fred,
> > >
> > >
> > > It does not appear to have addressed the problem. We are trying to gather
> > > more information.
> >
> >
> > In
> >
> >https://discussions.apple.com/thread/7267399
> >
> > someone states older Cyrus servers are returning a syntactically not quite
> > correct response to the EXPUNGE command but I'm having a hard time buying
> > this for an explanation.
> >
> > Oh, and someone in there asks for help to get the Apple bug report
> > (22996765)
> > escalated.
> >
> > I think at our site we have reached the count of 100 (one hundred) El
> > Capitan
> > Mail.app users.
> >
> >
> > Eric.
> >
>
> Hi Eric,
>
> If they are thinking that the example in the RFC is the specification, they
> are
> not correct. The IMAP server responses to determine completion of the EXPUNGE
> command are "OK" for a completed EXPUNGE, "NO" for a failure, and "BAD for
> unknown
> command or invalid arguments. Everything after those words are not germane to
> whether or not the command completed. The tag is what links the OK to the
> EXPUNGE
> command and not the "EXPUNGE completed". Sigh, they had it right and now it is
> broken.
Actually, the ImapTest command complained about this too:
http://imapwiki.org/ImapTest
>From RFC3501:
response-tagged = tag SP resp-cond-state CRLF
resp-cond-state = ("OK" / "NO" / "BAD") SP resp-text
; Status condition
resp-text = ["[" resp-text-code "]" SP] text
text= 1*TEXT-CHAR
So the exact text after the OK response doesn't matter, but it MUST be SP
followed by at least 1 TEXT-CHAR.
This is pretty easy to patch in 2.3.x if you're forced to remain there for
reasons. It is, of course, fixed in later versions.
Bron.
--
Bron Gondwana
br...@fastmail.fm
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server. [WARNING: DKIM validation failed]
Apple released OS 10.11.1 update yesterday. It shows that it includes, - Fixes an issue where outgoing server information may be missing from Mail - Resolves an issue that prevented display of messages and mailboxes in Mail Does anyone know if this fixed the problem. I've asked my users not to use Mail on El Capitan until this bug is fixed. Meanwhile, I'm working in my spare time to upgrade my cyrus-imapd on RedHat Enterprise Linux 6 from the 2.3 series distributed by RedHat to the 2.5 series which I'll have to build and maintain myself. That's an ugly job and one that I don't really want to do. Fred On 2015-10-18 06:14 AM, Bron Gondwana wrote: > On Sat, Oct 17, 2015, at 00:22, Eric Luyten wrote: >> On Thu, October 15, 2015 1:34 am, Bron Gondwana wrote: >> >> > Absolutely no idea. I think we have an upgraded test mac here in the >> > office. I'll set it up and see what it does. >> >> >> https://discussions.apple.com/thread/7267399 > > Yep, I managed to get a repeat test case. Of course on Cyrus 2.4+ the > cost of an errant EXPUNGE command isn't very high, because it doesn't > trigger a repack unless it actually makes a change which sets the > MAILBOX_NEEDS_REPACK flag on the index header, so it's only going to > affect people on ancient Cyrus. > > I have no idea why they're doing an EXPUNGE every time though. > > Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
