Hi, I have a problem getting the k9 mail client to work properly with dbmail 2.2.9 (latest marked stable on gentoo AMD64). There was a bug report logged with k9 here http://code.google.com/p/k9mail/issues/detail?id=1159 that the k9 devs seem to have classified as a dbmail server error. If it matters I use mysql 5.0.90.
I have attempted to verify their diagnosis with telnet to my server and seem to come to the same conclusion. I am far from an IMAP expert but my reading of the IMAP RFC http://tools.ietf.org/html/rfc3501#section-6.4.8 seems to me to say that the command UID SEARCH takes a "message sequence number range" as a parameter and then "returns the unique identifiers corresponding to the intersection of two sequence sets". However in my testing my INBOX has a message sequence range of 1-170 yet when I test UID SEARCH 1:170 it doesn't return 170 uid's but when I test SEARCH 1:170 it does return 170 message sequence numbers * OK dbmail imap (protocol version 4r1) server 2.2.9 ready to run a01 login xxx xxxxxxxxxx a01 OK LOGIN completed a02 SELECT "INBOX" * 170 EXISTS * 0 RECENT * FLAGS (\Seen \Answered \Deleted \Flagged \Draft) * OK [PERMANENTFLAGS (\Seen \Answered \Deleted \Flagged \Draft)] * OK [UIDNEXT 280709] Predicted next UID * OK [UIDVALIDITY 1] UID value a02 OK [READ-WRITE] SELECT completed a03 UID SEARCH 1:170 * SEARCH 121562 a03 OK SEARCH completed a04 UID SEARCH 1:* * SEARCH 121562 121565 121567 121574 121575 121580 121581 121582 121584 121585 121587 121588 121589 121590 121591 121592 121593 121594 121596 121598 121599 121600 121601 121602 121604 121606 121609 121610 121611 121612 121613 121614 121615 121616 121617 121618 121619 121620 121621 121624 121625 121626 121627 121628 121629 121630 121635 121636 121637 121638 121639 121641 121642 121643 121644 121646 121647 121648 121649 121650 121651 121652 121653 121654 121655 121656 121657 121658 121659 121660 121661 121662 121663 121664 121665 121666 121667 121668 121670 121673 121674 121675 121676 121679 121685 121690 125657 133202 133703 135257 141061 151579 160586 166147 167140 169244 169807 170035 170915 175437 184850 185053 196563 196678 217979 218048 218256 220843 221891 230721 230988 231112 241129 245185 245700 249266 251269 251538 251620 268760 268895 268897 270048 274424 275833 277540 277949 278377 278449 278677 278739 279382 279508 280130 280144 280212 280236 280240 280242 280254 280284 280300 280304 280324 280326 280382 280419 280431 280451 280479 280497 280517 280547 280551 280561 280567 280575 280583 280589 280592 280594 280600 280602 280604 280610 280646 280648 280684 280706 280708 a04 OK SEARCH completed a05 SEARCH 1:170 * SEARCH 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 a05 OK SEARCH completed I have done a bit of google searching and looking through the dbmail issues log and the version chagelogs and I can't seem to find anything about this. Is this a known bug? Should I log it in the issues log. Thanks, Ken Drummond. _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
