Max Mazurov

go-imap v2 Backend interface work

6

See messages for individual commits. Closes #323.

IMAP4rev2

4

I think it might be an interesting idea for go-imap v2 to track IMAP4rev2 development if we manage to implement all merged extensions. https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/

Merge support for COMPRESS extension

20

First round of changes for #322. - [x] APPENDLIMIT - [x] COMPRESS - [x] ENABLE - [ ] ~~ID~~ - [x] SPECIAL-USE - [x] UNSELECT - [x] [CHILDREN](https://github.com/foxcpp/go-imap-sql/tree/master/children) - [...

Backend extensions

1

This is a proof-of-concept to start some work on #322. See last 2 commits. To demonstrate how it works I implemented server support for UIDPLUS extension and also add it...

Avoid creating unnecessary backend.Mailbox objects

2

Ref https://github.com/emersion/go-imap/issues/337#issuecomment-594458545

Specification: https://tools.ietf.org/html/rfc5032 I believe it should be possible to implement it without backend changes.

Add Mailbox.Close

2

I am working on the maildir-based backend that uses BoltDB for caches and metadata. BoltDB DB is created per mailbox. backend.Mailbox implementation opens it on demand, but it also needs...

Merge extensions into the main code base

2

Comments in #260 outline a number of issues caused by an attempt to keep extensions independent of the main go-imap code. This includes two extensions being unable to extend the...

Delegate updates dispatching to the backend

2

## Problem - It is unsafe to send updates to clients literally "at any time". This causes major problems with synchronization and sequence numbers. - RFC 3501 prohibits sending EXPUNGE...

```go type Feature int const ( FeatureSMTPUTF8 = 1