We are excited to announce the release of Stalwart Mail Server v0.5.0. As we approach the end of the year, this significant update marks a major advancement in our journey to provide a robust, efficient, and versatile mail server solution. This latest version incorporates a range of performance enha...
Elevating Performance and Flexibility
We are excited to announce the release of Stalwart Mail Server v0.5.0. As we approach the end of the year, this significant update marks a major advancement in our journey to provide a robust, efficient, and versatile mail server solution. This latest version incorporates a range of performance enhancements, storage layer improvements, and new features, designed to elevate your email server experience.
Very interested in this as Gmail is one of my last Google cords to cut. But it doesn't solve the issue of trying to host it from a non-commercial Internet connection. Last I remember most ISPs won't let you open the ports required to run an email service on a home connection. Anyone have modern experience with that?
I moved from Gmail to ProtonMail, then to Mailbox.org. Ypu can set up a mailserver on your home server, but you would need a VPS that would forward the traffic to and from your home server without you needing to open any ports. This guide can help you with TLS passthrough.
But setting up your own mailserver is a big hassle. Just pay a trusted provider and keep your inbox, and preferably all emails, encrypted with GPG.
Gmail to MXroute when Google threatened to pull the grandfathered free Gmail custom domain thing. Got their lifetime plan, easy enough to configure so outgoing mails don’t get marked as spam. However, the major downside is it’s still using Spam Assassin as spam filter.
Will check it out. Setting up postfix + dovecot with dmarc and postgres was a funny experience but it's starting to slip out of my memory how I did it and I don't want to be through it again.
I looked at this, it looks pretty rudimentary compared to something like Mailcow-dockerized which has a full docker stack with clamAV, sieve, etc that you can add Roundcube on to, and has worked very well for me for years. There are precious few jmap clients out there so that's not much of a consideration really. I'd rather have rspamd itself rather than their fork of it because then I can depend on the original's documentation, because their documentation doesn't seem very comprehensive comparatively.
Plus, I'd rather have a stack of separate docker containers rather than a single container that munges it all together, but maybe that's not a big deal. I like to let Postgres manage the postgres container image and not put another layer in there.
I don't think it's you, it generally is a bad practice to have multiple processes inside a container. It usually defeats most of the isolation, introduces problems with handling zombie processes (therefore you need an init) and restarting tools when they crash (then you need something like supervisord, which I guess this image might use - I didn't check). Each software adds dependencies, which can conflict (again defeating the idea of containers), and of course CVEs. Then you have a problem with users etc.
So yeah, containers are generally not meant to be used this way. The project might be cool but I would be very uncomfortable running it like this, especially if that's going to be my primary email, with all the password resetting capabilities etc.
I tried to set this up beside my existing mailcow server. Mailcow runs smooth and has a web interface. And I am not on my way to ditch it just for jmap.
Idk, what's happening earlier:
1.dovecot integrates jmap (I would stay with mailcow)
2. More clients support jmap (eventually switch to stalwart)
3. Stalwart get an webinterface (eventually switch to stalwart)