Present: Bron, Ken, Robert, ellie, Partha, Nicola Ken: * short week last week, was traveling. * continuing to work on mailboxdb keys * need to do SASL release, we have a solution to GSSAPI thing. * sieve-fcc: what needs to be done. - Do we need to force people to do it for notify? - Tricky to implement. - do we need it? - mostly for people to either prove what happened for audit trail, or for debugging, so maybe it doesn't need to be exact. - Ken didn't push latest revision, so will have to redo and push.
Robert: * been working on JMAP-mail mostly * except for Email/parse and maybe some other gaps in the specification.* now working on JSCalendar spec updates in calendar code. * will come back to Email/parse afterwards. * CalConnect Tokyo - goal is to take updated JSCalendar spec in tandem with Last Call, and get any last feedback. - plan to submit updated specification this week (implementation will be done then!) - other idea: get contacts happening more (work with Ribose people). Need to decide best strategy.* Index record updates: - Partha can have a look at it. - Will try to fix current bug (2329/2330) in JMAP separately * JSCalendar - for participant, there are two properties - schedule sequence (SEQ of the last update from the participant), schedule- updated (DTSTAMP of the last update from the participant). - in FastMail this is done with Perl, so we will need to add it there. - right now there's no inbound iMIP handling in Cyrus, so it's up to the client. - should put it in lmtp, sieve extension, etc. - will have to store as an X- parameter on the Attendee. - good discussion point to look at JMAP X-* and see if they should be standardised. - might dovetail with Mike's Participant work. ellie: * have released 3.0.6 * been working more on the imap parsing stuff * got a maybe-fix for this evening's fetch bug (2329) but it's untested * have implemented prot_peek and prot_lookahead, which might be useful for http2 Partha: * mostly been doing FastMail stuff * largely GDPR work Bron: * did some JMAP work with allInThreadHaveKeyword last week. * does IMAP need a "can't be returned for legal reasons" error. - one-way flag - once set, can't be unset by user. ACL to allow override? - per-message ACL? Use-case outside this? - Ken: need per-message ACLs for manage attachments in CalDAV anyway. Nicola: * cyrus probably doesn't have much for GDPR. * maybe Cyrus website needs a privacy policy which says that we keep web logs. -- Bron Gondwana, CEO, FastMail Pty Ltd br...@fastmailteam.com