Don't see any reason why X-REFERENCES2 should not be advertised in the CAPABILITY string - the wiki indicates this is a new addition for 1.2, and RFC 5256 explicitly states that the THREAD= is to be used for upwards-compatible extensions. # HG changeset patch # User root@bigworm.curecanti.org # Date 1225057043 21600 # Branch HEAD # Node ID 1f082281f8d4e3d364b85c08ec329cf1be7ba61f # Parent 88a6a193e2884ac882ecc75e9ae9a242acc6188f Add X-REFERENCES2 to CAPABILITY string. diff -r 88a6a193e288 -r 1f082281f8d4 configure.in --- a/configure.in Sun Oct 26 16:30:50 2008 +0200 +++ b/configure.in Sun Oct 26 15:37:23 2008 -0600 @@ -2390,7 +2390,7 @@ dnl ** capability_banner="IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE" -capability="$capability_banner SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH SEARCHRES WITHIN CONTEXT=SEARCH" +capability="$capability_banner SORT THREAD=REFERENCES THREAD=X-REFERENCES2 MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH SEARCHRES WITHIN CONTEXT=SEARCH" AC_DEFINE_UNQUOTED(CAPABILITY_STRING, "$capability", IMAP capabilities) AC_DEFINE_UNQUOTED(CAPABILITY_BANNER_STRING, "$capability_banner", IMAP capabilities advertised in banner) michael