-
Notifications
You must be signed in to change notification settings - Fork 0
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
Move to go-imap-mess #1
Comments
Hi there! I was wondering if there's something I could do to help remove this blocker to using a maildir backend with maddy. I notice this has been open for a while, and if you have no interest in spending time/effort in this project of course I understand! I've been looking at this code a bit. My understanding is that this project needs to be "rebased" on top of the helpers in foxcpp/go-imap-mess, is that accurate? Quick bit on my motivation for using a maildir backend over the go-imap-sql one: I'd like to run maddy on a little server I have and write my email in a command line clients on my laptop and desktop. I already have a solution I'm happy with for syncing files around my machines and would love to stick a maildir directory into that and have clients interact with it, rather than set up additional imap based syncing for emails. Thank you for your work on maddy! Maddy dragged me over the line of putting some effort into hosting my own email, something I wanted to do for a while but always seemed to much maintenance/effort up till now. |
Yes. |
go-imap-maildir was used to prototype go-imap-mess helpers but go-imap-mess
eventually moved forward (while porting go-imap-sql) leaving go-imap-maildir in
its own mess (completely intentional pun).
The text was updated successfully, but these errors were encountered: