Max Mazurov

@kamarya FWIW, maddy has LDAP auth support ( using credentials binding)

IMO that's a weird implementation that loses type safety and makes code much less self-documenting. If I wanted to introduce a lot of optional arguments that should be set early...

>DialWithDialerTLS, DialTLS, DialWithDialer, Dial~~er~~ DialWithDialer can be dropped in favor of Opts.Dialer. Or left as is if we consider the whole Dial family as a "convenience wrappers" and say that...

My current idea of distributed/scalable deployment is putting go-imap-sql on top of CockroachDB with message blobs stored in some block storage (e.g. S3). This all is tracked in https://github.com/foxcpp/maddy/issues/279. Attachment...

Early versions of imapsql backend stored message contents as a blob in the same table as metadata. That turned out to be a performance problem. Now message contents are stored...

What needs to be done for it? From my understanding of linked RFC and go-imap internals, it needs to be supported by go-imap itself. But since UTF8 extension relies on...

Depends on #342 to get ENABLE extension in go-imap itself.

>re-producible by me, what do? Removing $GOPATH/pkg/mod/github.com/libdns/[email protected] directory may help.

>go get: github.com/foxcpp/go-imap-mess@none updating to >github.com/foxcpp/[email protected] requires >github.com/emersion/[email protected]: invalid version: unknown revision 271ea913b422 Another strange error I am failing to reproduce locally. dc11656 should fix it.

I pushed 44dc130 that pins libdns/gandi and libdns/alidns versions via commit. That should prevent overwriting Git tags from causing go.sum check failures. Can anybody confirm this indeed fixes the issue?