> >> question is: > >> > >> X-IMAP: 1213219525 0000000002 > >> > >> Although if the data is not stored in a placeholder message, the header > >> is named X-IMAPbase. > > > > By "placeholder message" do you mean what is described here? > > > > http://www.washington.edu/imap/IMAP-FAQs/index.html#6.14 > > > > If so, then it is correct that this change over time. > > > Yes, that is the "placeholder" message I was referring to. In mailboxes that > have never been empty when the POP client > connected, the X-IMAP info is stored in the first message in the mailbox, whi > ch seems to be moved to the next message > when that first message is deleted.
http://www.washington.edu/imap/IMAP-FAQs/index.html#6.15 > Why is that correct to change over time? Do you mean the second field of the > X-IMAP header to change? It was my > understanding that the second field is a strict counter of the last assigned > X-UID number, and the first field was a > time stamp of when the "DO NOT DELETE" message was created. The POP server i > s using the two to create a single UIDL > (hex representations of both field concacted). Wouldnt changing the first fi > eld (which is what we are experiencing) > cause the same message to have two different UIDLs and thus confuse the clien > t? That sounds like what is happening. I did, indeed, only mean that it is normal for the second field to change. So, is something (other than UW ipop3d) deleting this first message that should not be deleted, or are you saying the message is not being deleted, but is having its X-IMAP header regenerated anyway? Perhaps Oscar's suggestion of bogus headers on incoming messages is correct? Cheers, - Joel _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
