emailwiz

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README

commit 4b89da82457fe3a78df7d73dce2a58ba6713ea55
parent 794e875808ce5dea713041361415ec62923d2651
Author: Luke Smith <luke@lukesmith.xyz>
Date:   Mon, 27 May 2019 19:42:00 -0400

I always forget which one is which.

Diffstat:
MREADME.md | 14+++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md @@ -17,10 +17,10 @@ Expect it to fail. ## This script... -- Installs a dovecot/postfix mail server for your domain of choice -- Sets up sensible default mail boxes located in `~/Mail` -- Installs and sets up Spam Assassin -- Installs and sets up OpenDKIM which validates your emails so you can send to Google and other sites with picky spam filters +- Installs a **Dovecot/Postfix mail server** for your domain of choice +- Sets up **sensible default mailboxes** located in `~/Mail` +- Installs and sets up **Spam Assassin** +- Installs and sets up **OpenDKIM** which validates your emails so you can send to Google and other sites with picky spam filters ## This script does _not_ @@ -40,9 +40,9 @@ These are the main active ingredients: ## Requirements - `apt purge` all your previous (failed) attempts to install and configure a mailserver. Get rid of _all_ your system settings for Postfix, Dovecot, OpenDKIM and everything else. This script builds off of a fresh install. -- A Debian *web server*. I suspect the script will run on Ubuntu as well prodided there aren't huge differences in the default setup. I've tested this on a [Vultr](https://www.vultr.com/?ref=7914655-4F) Debian server and their setup works, but I suspect other VPS hosts will have similar/possibly identical default settings which will let you run this on them. -- An *MX record* in your DNS settings that points to your own main domain/IP. Unless you have your own DNS server, you'll put this setting on your domain registrar's site. Look up their documentation on how to do this, but it's usually really easy. -- *SSL for your site's mail subdomain*, specifically for mail.yourdomain.tld with Let's Encrypt. the script will look to Let's Encrypt's generated configs. If you have some other SSL system, you can manually change the SSL locations in the script before running it and it should be fine. +- A Debian **web server**. I suspect the script will run on Ubuntu as well prodided there aren't huge differences in the default setup. I've tested this on a [Vultr](https://www.vultr.com/?ref=7914655-4F) Debian server and their setup works, but I suspect other VPS hosts will have similar/possibly identical default settings which will let you run this on them. +- An **MX record** in your DNS settings that points to your own main domain/IP. Unless you have your own DNS server, you'll put this setting on your domain registrar's site. Look up their documentation on how to do this, but it's usually really easy. +- **SSL for your site's mail subdomain**, specifically for mail.yourdomain.tld with Let's Encrypt. the script will look to Let's Encrypt's generated configs. If you have some other SSL system, you can manually change the SSL locations in the script before running it and it should be fine. - After the script runs, you'll have to add an *additional DNS TXT record* which involved OpenDKIM key that it generates during the script. ## Don't get offended by this section