Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta: Make distributed deployments possible #279

Open
5 of 10 tasks
foxcpp opened this issue Oct 3, 2020 · 5 comments
Open
5 of 10 tasks

Meta: Make distributed deployments possible #279

foxcpp opened this issue Oct 3, 2020 · 5 comments
Labels
auth Related to authentication providers go-imap Issue that is caused by a problem in go-imap. go-imap-sql Issue that is caused by a problem in go-imap-sql. imap Related to IMAP server implementation

Comments

@foxcpp
Copy link
Owner

foxcpp commented Oct 3, 2020

In the light of #277 and Project Hexanet's internal needs. Here is the list of things to do:

Refactoring:

Several queries should be optimized/reworked in go-imap-sql in order to behave well in a distributed environment:

Officially support CockroachDB:

In other words, we have a long way to go. :)

@foxcpp foxcpp added auth Related to authentication providers go-imap-sql Issue that is caused by a problem in go-imap-sql. go-imap Issue that is caused by a problem in go-imap. imap Related to IMAP server implementation labels Oct 3, 2020
@foxcpp foxcpp pinned this issue Oct 3, 2020
@savchenko
Copy link

Is this relevant to #473 by any chance?..

@foxcpp
Copy link
Owner Author

foxcpp commented Mar 31, 2022

Yes, it is directly related. Currently, maddy does but support any deployment setup using active replication. For MX redundancy, your best solution is to configure second MX to buffer incoming messages and attempt resending them to the main server infinitely.

@aviallon
Copy link

aviallon commented Aug 8, 2024

Yes, it is directly related. Currently, maddy does but support any deployment setup using active replication. For MX redundancy, your best solution is to configure second MX to buffer incoming messages and attempt resending them to the main server infinitely.

Is there any hidden documentation on how to configure go-imap-sql with maddy?

I plan to setup a test server, which I'll migrate to when I feel the project is mature enough (I'm tired of dovecot).

@foxcpp
Copy link
Owner Author

foxcpp commented Aug 23, 2024

go-imap-sql is storage.imapsql module in maddy. All relevant documentation is available here: https://maddy.email/reference/storage/imapsql/
Some additional (mostly technical) information is available here: https://github.com/foxcpp/go-imap-sql

@foxcpp
Copy link
Owner Author

foxcpp commented Aug 23, 2024

I'll migrate to when I feel the project is mature enough

As of that, go-imap-sql will be eventually replaced by https://github.com/foxcpp/maddy-storage that is is in early development stage currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth Related to authentication providers go-imap Issue that is caused by a problem in go-imap. go-imap-sql Issue that is caused by a problem in go-imap-sql. imap Related to IMAP server implementation
Projects
None yet
Development

No branches or pull requests

3 participants