Max Mazurov

Looks like you need to create a pgloader.load file to define a custom CAST rule to get rid of LONGTEXT type: Something like this: ``` CAST type LONGTEXT to TEXT...

Uh, apparently, many automated systems generate malformed MIME messages and so we need to handle them somehow instead of rejecting.

I accidentally increased required Go version to 1.14 in 0.3.0 release. This made certain things such as easily reproducible builds problematic as latest stable Alpine Linux release ships Go 1.13.

How to determine public hostname to expose in auto-config? I think we should just let the user specify all details: ``` http http://0.0.0.0:8888 { autoconfig { display_name "ur.gs Email Service"...

Something like that could work as a generic base for HTTP-related static stuff: ``` http https://0.0.0.0 { # can use TLS in the same way as other endpoint modules tls...

Regarding auto-auto-config: This is kinda tricky IMO and on the edge of being "too clever to be useful". Unless the user explicitly defines endpoint information to use - pick first...

Side note: JMAP requires an HTTP endpoint too. So we need dynamic content support.

Different approach to HTTP endpoint module interfaces. It doesn't require keeping a separate "registry" for HTTP-related modules. Instead of HTTP endpoint module calling "attached" modules, modules that need HTTP call...

What I think about automatic configuration: it helps only in exotic setups because in more simple cases MUA can just probe standard ports. So guessing of parameters for auto-config is...

What's up with https://github.com/emersion/go-imap-disk? Can we use it? (of course, we need to finish it first)