News for hackers. Stuff that matters.
Re:Small mail server best current practices by gboss on Sunday July 26, 2020 @05:17PM (#23960255)
For A) I believe that is what https://mailinabox.email/ is trying to achieve
Re:Small mail server best current practices by martinmunk on Sunday July 26, 2020 @07:31PM (#23960961)
In search of self hosting email I tried out both MailInABox and Mailcow. MailInABox wanted to control DNS records which was a no-go. The primary driver behind the project seems to have arrogant attitude towards having users do DNS records themselves. Mailcow seemed nice but was guzzling up ram for seemingly no good reason. Finally tried out Mailu a few days ago which seems to work nice, albeit with limited testing.
Re:Small mail server best current practices by mustardo on Sunday July 26, 2020 @08:36PM (#23961282)
Mail in a box suggests being the DNS server in an attempt to be more user friendly, there are a lot of DNS records to setup for mail. How ever external DNS is supported (see "System status & DNS" in https://mailinabox.email/guide.html)
Re:Small mail server best current practices by mawalu on Monday July 27, 2020 @05:23AM (#23963482)
The RAM intensive elements of mailcow are search and clamav, you can disable them both if you don't need them
Re:Small mail server best current practices by codethief on Sunday July 26, 2020 @07:32PM (#23960964)
If only it didn't come with so many things (Roundcube, NextCloud) I don't need.
Re:Small mail server best current practices by gertrunde on Monday July 27, 2020 @03:54AM (#23963048)
I thought the same thing, but then I ended up using roundcube as my default non-mobile device mail client. And I just ignore the nextcloud bit.

(This is admittedly a very small deployment for two users and 3-4 domains on a $5/month VPS).

A lot of the other stuff I evaluated at the time (3-4 years ago) came with yet more stuff.