Bron: welcome people from CalConnect who stayed on from JMAP, you're welcome to stay and participate
Regular IETF NoteWell applies
There was no Agenda bash.


fetch-preview
---

fetch preview: should we make it just text and nothing else
Barry: would be happy with that
Neil: was it dovecot who wanted something else?   IMAGE as well?

ACTION: Bron to initiate discussion on the list about reverting to a simpler version

imap4rev2
---

Alexey: tweaked wording on earlier reported issues.  Finally took out mailbox pattern.

Open Issues:
* use of CLOSED response code to force client to unselect mailbox.
* canonical mailbox name.

CLOSED response code:
  Bron: suggest gate it behind IMAP4REV2
  Timo: worried that clients will forget to implement it
  Barry: if it's enabled, then CLOSED should always be used.  It's reasonable to expect anybody who does ENABLED IMAP4REV2 to read the spec.
  Timo: the problem is that this is so rare that clients won't ever have this happen during testing.  It should never happen.  Alternative is to just disconnect the client.
  Alexey: so just reserve closed for "if you select when already opened".

RESOLVED: if mailbox can't be kept open, the server must drop the connection (same as existing IMAP4rev1 behaviour of some servers)

Canonical name:
  Alexey: Initial proposal was response code, but there's too many restrictions on what's allowed.
  SUGGESTION: update response-code text in imap4rev2 to allow non-ASCII text (if enabled!)
  Barry: seems fine.
  Option - LIST extension or a new CREATED response.

RESOLVED: Alexey will propose a list response extension for IMAP4rev2 handling of canonical created name.

REMAINING ISSUES:

Bron: when do you think we'll be done?
Alexey: better is enemy of good.  Maybe future revision can deal with some of them!  We need to discuss search.  Will do in Madrid.
Murray: have been reading the whole document.  Haven't done IMAP before!  Collecting issues.
Alexey: please give issues as you find them so I can incorporate them.

ACTION: Alexey to review notes and publish another draft of IMAP4rev2 before Madrid.


Quota
---

Alexey: suggest people read the document and decide whether the OVERQUOTA with tag is useful, or whether we should drop it.
Alexey: Bron please review the ANNOTATION-STORAGE item. - Bron, will do.

Open Issues:
* OVERQUOTA SP tag syntax issue
* "If you know STORAGE is supported"... should it be dropped?  Does anybody think it's needed?

Future Directions:
* Interations with IMAP ACL extension.

Please let Alexey know if any opinions!

Timo: Is it useful to have SETQUOTA?  It feels more like a server command rather than something via IMAP.

Alexey: yes, you're probably right - but some tools are using it.  Should we split it up?  Maybe put in a separate section and maybe a different capability.

ACTION: Alexey to make SETQUOTA a separate capability in the quota draft.

ACTION: All please review the draft


sieve-mailboxid
---

Recent discussion on the list - need to make sure it works.

ACTION: Bron will make changes from Alexey and upload into group.


Other business
---

Ken: there's a "snooze action" for Sieve at Fastmail - do we want to document that?
Alexey: what does it do?
Ken: Set up a rule so emails get stored for later delivery.  Backend could be server specific.  Put into SMTP queue, put into IMAP mailbox and move automatically, etc.
Ken: Document just specifies the expected behaviour, not the underlying mechanics.
Alexey: I am curious and support seeing it.

ACTION: Ken will put together a -00 draft for sieve-snooze.


Milestones
---

ACTION: Bron, follow up with Stephan about EAI Sieve document.

Jul 2020 - Adopt a sieve-snooze document
Jul 2020 - Sieve MailboxId
Sep 2020 - IMAP4rev2
Dec 2020 - QUOTA