mailing list archives

Is anyone else seeing particularly bad IMAP behaviour from the new Mac OS?  Here's a lovely one from a user who keeps copying messages into the Junk Mail folder over and over:

<1382743710<4<1382743710<4.18 SELECT "INBOX.Junk Mail" (CONDSTORE)
>1382743711>* OK [CLOSED] Ok
* 79 EXISTS
* 0 RECENT
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen $X-ME-Annot-2 $IsMailingList $IsNotification $HasAttachment $HasTD $Junk $NotJunk $X
-ME-Annot-1 JunkRecorded hasatt Junk $MailFlagBit1 $MailFlagBit2 NotJunk hasnoatt hasnotd Forwarded $Forwarded)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen $X-ME-Annot-2 $IsMailingList $IsNotification $HasAttachment $HasTD $Jun
k $NotJunk $X-ME-Annot-1 JunkRecorded hasatt Junk $MailFlagBit1 $MailFlagBit2 NotJunk hasnoatt hasnotd Forwarded $Forwarded \*)] Ok
* OK [UNSEEN 1] Ok
* OK [UIDVALIDITY 1318456612] Ok
* OK [UIDNEXT 3361070] Ok
* OK [HIGHESTMODSEQ 213636] Ok
* OK [URLMECH INTERNAL] Ok
* OK [ANNOTATIONS 65536] Ok
44.18 OK [READ-WRITE] Completed
<1382743711<4<1382743711<5.18 FETCH 1:* (FLAGS UID MODSEQ) (CHANGEDSINCE 213634)
>1382743711>45.18 OK Completed (0.000 sec)
<1382743713<4<1382743713<6.18 IDLE
>1382743713>+ idling
<1382743713<D<1382743713<ONE
>1382743713>46.18 OK Completed
<1382743713<4<1382743713<7.18 CHECK
>1382743713>47.18 OK Completed
<1382743713<4<1382743713<8.18 UID COPY 3360991:3361069 "INBOX.Junk Mail"
>1382743714>* 158 EXISTS
* 79 RECENT
48.18 OK [COPYUID 1318456612 3360991:3361069 3361070:3361148] Completed

They've had 2 million messages in that mailbox over the past couple of week, using pre-release and then released 10.9.

(there's another interesting pattern, it appears to send the 'D' of 'DONE' in a separate packet when finishing IDLE... no idea why.  I've never seen DONE split over two reads before)

We've also had users reporting regular bugs in the interface, like turning off "store sent items on server" not working, and the "\Archive" folder not appearing in the GUI, but that's not IMAP protocol territory.

...

I've also seen this lovely pattern on Mail.app sessions while debugging today:

<1382690260<229.12 UID STORE 588201 +FLAGS.SILENT ($Junk Junk JunkRecorded)
>1382690260>229.12 OK Completed
<1382690260<230.12 UID STORE 588201 -FLAGS.SILENT ($NotJunk NotJunk)
>1382690260>230.12 OK Completed
<1382690260<231.12 UID EXPUNGE 588201
>1382690260>231.12 OK Completed
<1382690260<232.12 UID STORE 588201 +FLAGS.SILENT (\Deleted)
>1382690260>232.12 OK Completed

Unsurprisingly, this doesn't actually lead to the message being expunged.

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm

On Sat, Oct 26, 2013 at 12:10:18PM +1100, Bron Gondwana wrote:
> (there's another interesting pattern, it appears to send the 'D' of
> 'DONE' in a separate packet when finishing IDLE... no idea why.  I've
> never seen DONE split over two reads before)

Two possibilities:

1. It's a neat hack to learn whether a middlebox has killed the
   connection.

2. They're sending the D, O and N separately to extend NAT timeouts.

Arnt

Have you seen the 2-million-message-copy behavior on multiple users? That
seems like a bug that might be related to some weird rules, or perhaps a
buggy migration of rules from 10.8 to 10.9.

From talking to people at Apple, literally the *best* way to get stuff like
this fixed is to file bug reports on BugReporter<http://bugreporter.apple.com>.
After that, please post the issue to
OpenRadar<http://www.openradar.me/page/1> so
others can see it. For your users that actively report problems, you can
send them some boilerplate to also submit a bug, and include the original
bug number so it can be marked as a dupe.








On Mon, Oct 28, 2013 at 6:25 AM, Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no>wrote:

> On Sat, Oct 26, 2013 at 12:10:18PM +1100, Bron Gondwana wrote:
> > (there's another interesting pattern, it appears to send the 'D' of
> > 'DONE' in a separate packet when finishing IDLE... no idea why.  I've
> > never seen DONE split over two reads before)
>
> Two possibilities:
>
> 1. It's a neat hack to learn whether a middlebox has killed the
>    connection.
>
> 2. They're sending the D, O and N separately to extend NAT timeouts.
>
> Arnt
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20131028/51fa2d41/attachment.html>

On Tue, Oct 29, 2013, at 06:00 AM, Michael Grinich wrote:

Have you seen the 2-million-message-copy behavior on multiple users?
That seems like a bug that might be related to some weird rules, or
perhaps a buggy migration of rules from 10.8 to 10.9.


No, just one - but the latest appears that he deleted a bunch of
folders with names like "Junk" and "Junk Mail" - I'm guessing that
something got corrupted inside his mail database.

From talking to people at Apple, literally the *best* way to get stuff
like this fixed is to file bug reports on [1]BugReporter. After that,
please post the issue to [2]OpenRadar so others can see it. For your
users that actively report problems, you can send them some boilerplate
to also submit a bug, and include the original bug number so it can be
marked as a dupe.


Luckily we actually have a developer account, or it would be a "pay
money so you can report bugs to us".  Of course, my bug hasn't actually
be LOOKED AT yet.

Anyway:
[3]http://www.openradar.me/radar?id=5268346471710720

Bron.
--
Bron Gondwana
brong@fastmail.fm

References

1. http://bugreporter.apple.com/
2. http://www.openradar.me/page/1
3. http://www.openradar.me/radar?id=5268346471710720
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20131029/83a660f1/attachment.html>