emailwiz

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

commit 037439d367f052b97852fcd8d6f4d685bd05921e
parent dfb28af5e797288cbe137a2debf9717a73d4701e
Author: Luke Smith <luke@lukesmith.xyz>
Date:   Tue,  9 Jun 2020 14:52:36 -0400

ubuntu usable, cram rm'd

Diffstat:
MREADME.md | 4++--
Memailwiz.sh | 7+------
2 files changed, 3 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md @@ -30,9 +30,9 @@ Expect it to fail and you have to do bug testing and you will be very happy when ## 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 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. +- A **Debian or Ubuntu server**. 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. +- **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. You might want to create a dummy Apache/nginx record for your mail domain as this makes running Let's Encrypt's Certbot easier. - After the script runs, you'll have to add an *additional DNS TXT record* which involves the OpenDKIM key that it generates during the script. ## Caveats diff --git a/emailwiz.sh b/emailwiz.sh @@ -125,7 +125,7 @@ ssl = required ssl_cert = <$certdir/fullchain.pem ssl_key = <$certdir/privkey.pem # Plaintext login. This is safe and easy thanks to SSL. -auth_mechanisms = plain login cram-md5 +auth_mechanisms = plain login protocols = \$protocols imap @@ -133,11 +133,6 @@ protocols = \$protocols imap userdb { driver = passwd } -# Use file with cram-md5 hashed passwords to find user passwords -passdb { - driver = passwd-file - args = scheme=cram-md5 /etc/cram-md5.pwd -} #Fallback: Use plain old PAM to find user passwords passdb { driver = pam