We seem to be using dovecot, which seems to have NOTIFY support via an option (that might be incompatible with some other plugins). We don't have it enabled: 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 COMPRESS=DEFLATE There is at least IDLE support, but that only works for the active folder. So if doing server-side filtering to subfolders with sieve, there is no push notification support other than to the folder active in the client. My client (evolution) also has NOTIFY support, which would be able to notify about all folders, not just one like IDLE. Without NOTIFY, I'm forced to either do a slow full send/receive process or switch folders to get IDLE to tell about the new e-mails in the folder switched to (plus likely a separate request happening from the client about that folder), with NOTIFY, this should be more lightweight on the server and solve the issues. <grknight> leio: according to http://wiki2.dovecot.org/IMAPServer, a single function must be set to enable it. dunno if that's a good thing to change without discussion (and it excludes a certain plugin from use.. mailbox_alias)
I've enabled it by editing the file locally on woodpecker for testing.
I see it in CAPABILITIES now and do get STATUS notifications now in IMAP conversation debug output for the stuff my mail client has subscribed to be notified for. Some regression or configuration combination involved bug in client is not showing the updates in the GUI, but it seems to work server-side. I should get the client bug fixed myself or via upstream help within a week or so.
What's left to do here?
Moving the configuration changes to puppet, I think.
leio, is all good here? This seems to be live on woodpecker and config in puppet looks good to me
