IMAP IDLE capability missing (Push support) #446
Labels
bug
Something isn't working.
go-imap
Issue that is caused by a problem in go-imap.
ready-for-release
Feature is implemented and available for testing in dev branch. It will be included in the next rele
Describe the bug
Latest maddy doesn't report the IMAP IDLE capability, rendering message pushing unavailable.
Steps to reproduce
export MOZ_LOG=IMAP:4
in this case)Log files
[Parent 11216: IMAP]: I/IMAP 7f63b185f800:redacted:NA:CreateNewLineFromSocket: 45 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR CHILDREN UNSELECT MOVE APPENDLIMIT APPENDLIMIT CHILDREN I18NLEVEL=1 SORT THREAD=ORDEREDSUBJECT COMPRESS NAMESPACE] AUTHENTICATE completed
Other examples for reference:
generic provider A
[Parent 11216: IMAP]: I/IMAP 7f63bdbea000:redacted:NA:CreateNewLineFromSocket: 93 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SPECIAL-USE QUOTA] Logged in
generic provider B
[Parent 11216: IMAP]: I/IMAP 7f63b1877000:redacted:A:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 CHILDREN ENABLE ID IDLE LIST-EXTENDED LIST-STATUS LITERAL- MOVE NAMESPACE SASL-IR SORT SPECIAL-USE THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN APPENDLIMIT=29360128
generic provider C
[Parent 11216: IMAP]: I/IMAP 7f63b1869800:redacted:NA:CreateNewLineFromSocket: 61 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY XLIST LITERAL+ NOTIFY SPECIAL-USE] Logged in
Configuration file
Default configuration except
$(hostname)
and$(primary_domain)
maddy/maddy.conf
Line 1 in 5972749
Environment information
The text was updated successfully, but these errors were encountered: