No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.

README.md 6.1 KiB

hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 5 años
hace 4 años
hace 4 años
hace 5 años
hace 5 años
hace 4 años
hace 5 años
hace 5 años
hace 5 años
hace 4 años
hace 5 años
hace 4 años
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138
  1. # Email server setup script
  2. I wrote this script during the gruelling process of installing and setting up
  3. an email server. It perfectly reproduces my successful steps to ensure the
  4. same setup time and time again.
  5. I've linked this file on Github to a shorter, more memorable address on my
  6. website so you can get it on your machine with this short command:
  7. ```
  8. curl -LO lukesmith.xyz/emailwiz.sh
  9. ```
  10. When prompted by a dialog menu at the beginning, select "Internet Site", then
  11. give your full domain without any subdomain, i.e. `lukesmith.xyz`.
  12. Read this readme and peruse the script's comments before running it. Expect it
  13. to fail and you have to do bug testing and you will be very happy when it
  14. actually works perfectly.
  15. ## This script installs
  16. - **Postfix** to send and receive mail.
  17. - **Dovecot** to get mail to your email client (mutt, Thunderbird, etc).
  18. - Config files that unique the two above securely with native log-ins.
  19. - **Spamassassin** to prevent spam and allow you to make custom filters.
  20. - **OpenDKIM** to validate you so you can send to Gmail and other big sites.
  21. ## This script does _not_
  22. - use a SQL database or anything like that.
  23. - set up a graphical interface for mail like Roundcube or Squirrel Mail. If you
  24. want that, you'll have to install it yourself. I just use
  25. [isync/msmtp/mutt-wizard](https://github.com/lukesmithxyz/mutt-wizard) to
  26. have an offline mirror of my email setup and I recommend the same. There are
  27. other ways of doing it though, like Thunderbird, etc.
  28. ## Requirements
  29. 1. A **Debian or Ubuntu server**. I've tested this on a
  30. [Vultr](https://www.vultr.com/?ref=8384069-6G) Debian server and one running
  31. Ubuntu and their setup works, but I suspect other VPS hosts will have
  32. similar/possibly identical default settings which will let you run this on
  33. them. Note that the affiliate link there to Vultr gives you a $100 credit
  34. for the first month to play around.
  35. 2. **A Let's Encrypt SSL certificate for your site's `mail.` subdomain**.
  36. Create a nginx/apache site at `mail.<yourdomain.com>` and get a certificate
  37. for it with Let's Encrypt's [Certbot](https://certbot.eff.org/).
  38. 3. You need two little DNS records set on your domain registrar's site/DNS
  39. server: (1) an **MX record** pointing to your own main domain/IP and (2) a
  40. **CNAME record** for your `mail.` subdomain.
  41. 4. **A Reverse DNS entry for your site.** Go to your VPS settings and add an
  42. entry for your IPV4 Reverse DNS that goes from your IP address to
  43. `<yourdomain.com>` (not mail subdomain). If you would like IPV6, you can do
  44. the same for that. This has been tested on Vultr, and all decent VPS hosts
  45. will have a section on their instance settings page to add a reverse DNS PTR
  46. entry.
  47. You can use the 'Test Email Server' or ':smtp' tool on
  48. [mxtoolbox](https://mxtoolbox.com/SuperTool.aspx) to test if you set up
  49. a reverse DNS correctly. This step is not required for everyone, but some
  50. big email services like gmail will stop emails coming from mail servers
  51. with no/invalid rDNS lookups. This means your email will fail to even
  52. make it to the receipients spam folder; it will never make it to them.
  53. 5. `apt purge` all your previous (failed) attempts to install and configure a
  54. mailserver. Get rid of _all_ your system settings for Postfix, Dovecot,
  55. OpenDKIM and everything else. This script builds off of a fresh install.
  56. 6. Some VPS providers block port 25 (used to send mail). You may need to
  57. request that this port be opened to send mail successfully. Although I have
  58. never had to do this on a Vultr VPS, others have had this issue so if you
  59. cannot send, contact your VPS provider.
  60. ## Post-install requirement!
  61. - After the script runs, you'll have to add additional DNS TXT records which
  62. are displayed at the end when the script is complete. They will help ensure
  63. your mail is validated and secure.
  64. ## Making new users/mail accounts
  65. Let's say we want to add a user Billy and let him receive mail, run this:
  66. ```
  67. useradd -m -G mail billy
  68. passwd billy
  69. ```
  70. Any user added to the `mail` group will be able to receive mail. Suppose a user
  71. Cassie already exists and we want to let her receive mail to. Just run:
  72. ```
  73. usermod -a -G mail cassie
  74. ```
  75. A user's mail will appear in `~/Mail/`. If you want to see your mail while ssh'd
  76. in the server, you could just install mutt, add `set spoolfile="+Inbox"` to
  77. your `~/.muttrc` and use mutt to view and reply to mail. You'll probably want
  78. to log in remotely though:
  79. ## Logging in from Thunderbird or mutt (and others) remotely
  80. Let's say you want to access your mail with Thunderbird or mutt or another
  81. email program. For my domain, the server information will be as follows:
  82. - SMTP server: `mail.lukesmith.xyz`
  83. - SMTP port: 587
  84. - IMAP server: `mail.lukesmith.xyz`
  85. - IMAP port: 993
  86. - Username `luke` (I.e. *not* `luke@lukesmith.xyz`)
  87. The last point is important. Many email systems use a full email address on
  88. login. Since we just simply use local PAM logins, only the user's name is used
  89. (this makes a difference if you're using my
  90. [mutt-wizard](https://github.com/lukesmithxyz/mutt-wizard), etc.).
  91. ## Tweaking things
  92. You're a big boy now if you have your own mail server!
  93. You can tweak Postfix (sending mail
  94. ## Benefited from this?
  95. If this script or documentation has saved you some frustration, you can donate
  96. to support me at [lukesmith.xyz/donate](https://lukesmith.xyz/donate.html).
  97. ## Troubleshooting -- Can't send mail?
  98. - Always check `journalctl -xe` to see the specific problem.
  99. - Go to [this site](https://appmaildev.com/en/dkim) to test your TXT records.
  100. If your DKIM, SPF or DMARC tests fail you probably copied in the TXT records
  101. incorrectly.
  102. - If everything looks good and you *can* send mail, but it still goes to Gmail
  103. or another big provider's spam directory, your domain (especially if it's a
  104. new one) might be on a public spam list. Check
  105. [this site](https://mxtoolbox.com/blacklists.aspx) to see if it is. Don't
  106. worry if you are: sometimes especially new domains are automatically assumed
  107. to be spam temporaily. If you are blacklisted by one of these, look into it
  108. and it will explain why and how to remove yourself.