Max Mazurov

IMO Most linters report _potential_ problems, not problems. I believe hard-failing build because of linter warnings is a little bit unnecessary. I think we had this conversation with @emersion in...

As an alternative to throwing nolint all over the place it is probably a good idea to eventually resolve minor 'issues' to reduce noise even if it is just documentation...

Data point: Over time I managed to gradually reduce the amount of warnings reported by linters for maddy code base but that sure was a long way from multiple full...

>The AutoLogout test has a race: `testServer*` functions need "server configuration" callbacks like it is done in go-smtp to set all necessary settings before connecting.

Note that StatusResp is not necessarily an error. Returning OK response as an error would be strange, don't you think? I think we might want to preserve Err() method but...

Also, it might worth considering checking for ErrResp when it is returned by server backend. It can be useful for go-imap-proxy, for example.

Documenting some ideas I have. ## IPC endpoint IPC endpoint is a regular module, just like others. It binds on Unix socket, usually `/run/maddy/ipc.sock`. If somebody wants to run maddy...

Decision: Not needed now, statistics should be collected through analysis of machine-readable logs, IMAP updates passing should be implemented using DB-specific methods (for example, using NOTIFY from PostgreSQL, this will...

It might be a good idea to add some sort of a management API, e.g. for use with some control dashboard or whatever.

Wondering, how a REST-style HTTP API would look like, taking maddy's "modules framework" into account. Probably `/MODULE_INSTANCE/whatever_module_defines` e.g. `/local_mailboxes/accounts`. That is, pass API requests to a particular module instance based...