<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; ">Vincent Beffara wrote:<br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; ">-----------------------</div><div style="font-family: 'times new roman', 'new york', times, serif; "><div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; ">Hi,<br><br>cc> 1) I'm getting X-OfflineIMAP headers on a sync between a Dovecot<br>cc> IMAP remote server (don't have version number at hand) and Cyrus<br>cc> IMAP v2.3.16 (very recent). Aren't these servers supposed to<br>cc> support UID's ?? I shouldn't be even getting X-OfflineIMAP headers,<br>cc> right?<br><br>Dovecot (as of version 2.0.x) does support UIDPLUS, which is what's<br>needed here, *but* it
doesn't advertise it by default before login, so<br>we don't know that it does ... Quite easy to patch the source to make it<br>work but I'm not sure if the capability_banner variable can be modified<br>via a config file.<br><br>Cyrus should work, my config is exactly the same as yours with a patched<br>dovecot server.<br><br>HTH,<br><br> /v<br>----------------</div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859">Thanks Vincent. Unfortunately I don't have control of the remote Dovecot IMAP server so I can't patch that source to add UIDPLUS to the pre-login capabilities banner:</div><div class="yui_3_2_0_16_131360253663859"><div class="yui_3_2_0_16_131360253663859">* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.</div></div><div style="font-family: 'times new roman', 'new york',
times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859"><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859">This behavior is exactly what Gmail was doing: not advertising UIDPLUS before login, then admitting it supports UIDPLUS after login.</div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859"><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859">But it's correct according to IMAP protocol. As the client, we're supposed to be able to deal with untagged updates to capabilities - like UIDPLUS - at any time.</div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859"><br></div><div style="font-family: 'times new roman', 'new
york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859">We have to handle this either with a callback or by re-querying the cached value in imaplib2 anytime we're about to make a logical decision that hinges on whether UIDPLUS is supported.<br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859"><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859">Anyone know if this has been fixed ?</div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859"><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; " class="yui_3_2_0_16_131360253663859">Chris</div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "
class="yui_3_2_0_16_131360253663859"><br></div></div></div></body></html>