On Wed, 2007-03-14 at 13:26 -0700, Alex Boster wrote:
X-IMAPbase: 1173814340 4280058374 $NotJunk JunkRecorded X-UID: 4280058361
This is your problem. Your UID has gotten higher than 2^31 which confuses many clients, even though it's still valid from IMAP protocol's point of view.
As for why it has gotten this high.. Well, recent Dovecot RCs could break them sometimes, but at least with 1.0.rc27 everything should be working.
If you remove the X-IMAPbase, X-IMAP and X-UID headers and delete Dovecot's index files the messages will be given new UIDs beginning from 1.
If this just keeps happening, then I think it's because the incoming mails contains invalid X-UID headers. Normally those shouldn't break anything as long as you haven't deleted Dovecot's index files or the mbox file isn't empty. If they do and you can figure out how to reproduce it, please let me know.
Anyway, the problems would most likely go away if you just filter out all the X-UID headers from incoming mails. See the bottom of http://wiki.dovecot.org/MboxProblems