/explore
|
You are here 
|
samhobbs.co.uk | ||
| | | | |
blog.latana.rocks
|
|
| | | | | Notice: this post is aimed to advanced users who already now how DNS works and can set up a firewall for a network. In this container-dominated era, setting up a software solution for a self-hosted mail server has become surprisingly straightforward, even for those with limited technical expertise. The use | |
| | | | |
blog.jitendrapatro.me
|
|
| | | | | ||
| | | | |
jan.wildeboer.net
|
|
| | | | | 0. The Journey - The basics and outlook (on the series, not the Microsoft mail client ;) 1. Postfix - the in and out, so to say. The robust, battle-hardened connection point for other mail servers on the internet to send emails to and receive emails from your domain(s). Also known as the MTA, the Mail Transfer Agent. 2. Dovecot - where you and your users talk to to get emails to their mail client, be it your smartphone, a mail client on your computer or just even the command line. It's the IMAP server. 3. DKIM/DMARC/SPF - Just having postfix and dovecot up and running isn't enough. We will also look at user authentication, letsencrypt certificates, DKIM, DMARC, SPF and the daily checks to make sure everything is humming along nicely. 4. The final stuff - How... | |
| | | | |
rocketee.rs
|
|
| | | How to prevent emails going to spam and improve the overall deliverability of your email domain. | ||
