3 ms·
This should be pretty straightforward to do with an IMAP <-> IMAP syncing tool, like mbsync [1]. You'd run it periodically in the background to sync the remote
by abound 11mo ago
This should be pretty straightforward to do with an IMAP <-> IMAP syncing tool, like mbsync [1]. You'd run it periodically in the background to sync the remote IMAP to Stalwart's local IMAP server, and Stalwart can then automatically serve that via JMAP, doing the translation internally.
I was originally thinking you'd need to go remote IMAP <-> maildir <-> Stalwart IMAP, which would be really complicated, but I think the IMAP <-> IMAP should work fine.
[1] https://isync.sourceforge.io/mbsync.html https://isync.sourceforge.io/mbsync.html
- jamespo 11mo agoimapgoose which was recently featured here I think is another option: https://whynothugo.nl/journal/2025/10/15/introducing-imapgoose/ https://whynothugo.nl/journal/2025/10/15/introducing-imapgoo...
- abound 11mo agoImapGoose is on my radar to replace mbsync and imapnotify in my setup, but I think it's IMAP <-> maildir only, which makes sense for the intended use case of local mail
- exprez135 11mo agoStalwart currently does not support the NOTIFY extension to IMAP, needed for ImapGoose, though it is planned: https://github.com/stalwartlabs/stalwart/issues/484 https://github.com/stalwartlabs/stalwart/issues/484
- solarkraft 11mo agoDoes this actually impact the remote IMAP -> Stalwart route? That said, getting timely notifications is definitely an important point!
- ShellackGobln7 11mo agoand it's excellent, I have run it since the HN post. Replaced all the old ways for regular IMAP. Gmail still using lieer.