The following issue has been CLOSED ====================================================================== http://www.dbmail.org/mantis/view.php?id=914 ====================================================================== Reported By: vampyre Assigned To: ====================================================================== Project: DBMail Issue ID: 914 Category: Authentication layer Reproducibility: always Severity: minor Priority: normal Status: closed target: Resolution: no change required Fixed in Version: ====================================================================== Date Submitted: 09-Aug-11 16:32 CEST Last Modified: 06-Sep-12 09:28 CEST ====================================================================== Summary: CAPABILITY for AUTHENTICATE LOGIN Description: Hello paul,
That is me again. And now I am trying to migrate information from one dbmail instance to another one via imapsync. However dbmail return incorrect capability as a result I don't succeed: .... Host xxx.xx.xx.xx says it has CAPABILITY for AUTHENTICATE LOGIN .... Read: * OK [CAPABILITY IMAP4rev1 AUTH=LOGIN STARTTLS ID] dbmail 2.3.7 ready. Banner: * OK [CAPABILITY IMAP4rev1 AUTH=LOGIN STARTTLS ID] dbmail 2.3.7 ready. ..... Host1 capability: ID AUTH=LOGIN STARTTLS IMAP4REV1 Host2 capability: ID AUTH=LOGIN STARTTLS IMAP4REV1 While if I am doing the same stuff using cyrus I am getting: ==== Host1 capability: ID QUOTA ANNOTATEMORE NAMESPACE STARTTLS MULTIAPPEND RIGHTS=KXTE IDLE URLAUTH CONDSTORE UNSELECT SORT BINARY NO_ATOMIC_RENAME CATENATE UIDPLUS THREAD=REFERENCES IMAP4 IMAP4REV1 MAILBOX-REFERRALS THREAD=ORDEREDSUBJECT ACL LITERAL+ SORT=MODSEQ CHILDREN Host2 capability: ID AUTH=LOGIN STARTTLS IMAP4REV1 ==== As I can see it can be connected with following commit: 63b0acdc0625d0d6ee4076edd0e5f7b1176fb211 Am I right? If yes, could you please point me to the reason of removing capability ? ====================================================================== ---------------------------------------------------------------------- (0003226) paul (administrator) - 10-Aug-11 10:30 http://www.dbmail.org/mantis/view.php?id=914#c3226 ---------------------------------------------------------------------- vampyre, the commit you mention fixes the capability response. Current behaviour is modelled on dovecot: * OK [CAPABILITY IMAP4rev1 AUTH=LOGIN STARTTLS ID] dbmail 3.0.0-rc2 ready. x capability * CAPABILITY IMAP4rev1 AUTH=LOGIN ACL RIGHTS=texk NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE ID x OK CAPABILITY completed x login testuser1 test x OK [CAPABILITY IMAP4rev1 ACL RIGHTS=texk NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE ID] User testuser1 authenticated x logout * BYE x OK LOGOUT completed ---------------------------------------------------------------------- (0003227) vampyre (reporter) - 10-Aug-11 19:03 http://www.dbmail.org/mantis/view.php?id=914#c3227 ---------------------------------------------------------------------- I don't sure if I understand you correctly, I will recheck the model. However currently I am interested in that "fixed" capability, if I remove the "Capa_remove" line for namespace it seems to be working. Btw, I can see that there is a capability configuration in dbmail.conf, however it doesn't help either due to the same reason. Is there a way to make this configurable? Issue History Date Modified Username Field Change ====================================================================== 09-Aug-11 16:32 vampyre New Issue 10-Aug-11 10:30 paul Note Added: 0003226 10-Aug-11 19:03 vampyre Note Added: 0003227 06-Sep-12 09:28 paul Status new => closed 06-Sep-12 09:28 paul Resolution open => no change required ====================================================================== _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
