-
Notifications
You must be signed in to change notification settings - Fork 303
Open
Labels
authRelated to authentication providersRelated to authentication providersgo-imapIssue that is caused by a problem in go-imap.Issue that is caused by a problem in go-imap.go-imap-sqlIssue that is caused by a problem in go-imap-sql.Issue that is caused by a problem in go-imap-sql.imapRelated to IMAP server implementationRelated to IMAP server implementation
Description
In the light of #277 and Project Hexanet's internal needs. Here is the list of things to do:
Refactoring:
- Refactor imapsql blob storage interface to use modules framework #303
- Replace updatepipe package written for go-imap v1 with a better update dispatcher.
- Implement support for some distributed broker - to be used with IMAP updates distribution.
- Create abstraction for SMTP queue storage #262.
- S3 blob storage #304
Several queries should be optimized/reworked in go-imap-sql in order to behave well in a distributed environment:
- Get rid of "marking" logic in message removal go-imap-sql#28
- Expunge does two (!) full table scans go-imap-sql#33
Officially support CockroachDB:
- CockroachDB support go-imap-sql#5
- Officially support CockroachDB use with auth.sql_table/auth.sql_query.
In other words, we have a long way to go. :)
radriaanse, dzervas, franchb and aviallon
Metadata
Metadata
Assignees
Labels
authRelated to authentication providersRelated to authentication providersgo-imapIssue that is caused by a problem in go-imap.Issue that is caused by a problem in go-imap.go-imap-sqlIssue that is caused by a problem in go-imap-sql.Issue that is caused by a problem in go-imap-sql.imapRelated to IMAP server implementationRelated to IMAP server implementation