Re:Show HN: IMAP API – Self-hosted access to IMAP over REST
by andris9 on Sunday March 01, 2020 @04:28PM
(#22459488)
It mostly means I haven’t yet figured out which kind of license/terms to use for this project. TBD.
[ Parent
| on HN ]
Re:Show HN: IMAP API – Self-hosted access to IMAP over REST
by grizzles on Sunday March 01, 2020 @07:23PM
(#22460436)
Thanks for your work in this area. A couple questions.
How is this different to the wilduck webmail api?
Would it be hard to abstract away the wildduck storage code to use a datastore other than mongodb?
Re:Show HN: IMAP API – Self-hosted access to IMAP over REST
by andris9 on Monday March 02, 2020 @12:17AM
(#22461845)
WildDuck API exposes database structures from MongoDB, IMAP API is more like a proxy in front of any IMAP server.
WildDuck is pretty much coupled with MongoDB. IMAP is not very easily abstractable and keeping the result scalable at the same time. Largest WildDuck cluster in production manages 20TB (~20k accounts) of email by now with no special config or modifications - making it scalable was the main goal from the start and supporting arbitrary storage would not have helped.