Max Mazurov

> It would be like `maddyctl` not having `maddyctl imap-acct create` but `maddyctl local_mailboxes create`. There is `--cfg-block` argument with default value of `local_mailboxes`. The problem is that maddy permits...

For client it would involve duplicating `Mail`, `Rcpt`, etc. to add context.Context argument (MailContext, RcptContext). As for relation to timeouts, perhaps we could have context-less functions create such context with...

On a second thought, gluing together net.Conn and context.Context is a tricky task so it is probably better to just implement command timeouts like it is done for the server.

Design considerations: `target.queue` module is able to correctly generate only NOTIFY=DELAY and NOTIFY=FAILURE notifications. Other `target.*` modules are responsible for generating NOTIFY=SUCCESS notifications. This includes target.imapsql, target.smtp and target.remote. Last...

Logout terminates the connection. See https://tools.ietf.org/html/rfc3501#section-3.4. Nevertheless, the error reported by go-imap is not correct.

On point 2: go-smtp terminates the connection after just 3 protocol errors, this is enough to terminate connection if any HTTP request is misdirected to the server.

@lexesv, could you add `io_debug` directive to `imap` block and a global `debug` in maddy.conf, attempt deleting some messages and post logs content here? Like this: ``` debug imap tcp://0.0.0.0:465...

Hmm, the included log does not show any EXPUNGE commands being executed.

In either case, it might be caused by improper IMAP4 implementation. Will need to recheck if it is still happening in 0.6.

go-webdav needs a lot of work before it can be used as a production-ready CalDAV/CardDAV implementation. And we probably need a generic HTTP endpoint implementation in maddy first (some discussion...