this post was submitted on 27 Dec 2023
121 points (99.2% liked)

Selfhosted

40246 readers
867 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
121
Stalwart v0.5.0 (stalw.art)
submitted 10 months ago* (last edited 10 months ago) by Parachute4196@lemmy.world to c/selfhosted@lemmy.world
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] sudneo@lemmy.world 7 points 10 months ago (2 children)

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.

[–] ace@lemmy.ananace.dev 2 points 10 months ago

Reading the Dockerfile in their repo, it's simply a clean debian:slim with four compiled rust binaries placed into it. There's no services, no supervisord, nothing except the mail server binaries themselves.

[–] eskuero@lemmy.fromshado.ws 1 points 10 months ago

Does it run multiple processes inside the container? Looks like the entrypoint only launchs one.