![]() I went back to the Poste.io docker configuration page and added 4 paths to map: Then I thought to myself, “NPM LE stores the certificates in the AppData folder of Unraid, I could use that!” I tried getting the LE functionality in Poste.io to work with the NPM LE but couldn’t come up with a solution that would result in automatic SSL certificate renewals in the future. LE servers not able to validate that I own the domain name □ When the Poste.IO LE tries to validate domain ownership the LE server ends up calling the NPM LE, which says “uh, what, 404 for me I guess”. Poste.io does support LetsEncrypt, but trying to run LE validation behind another LE instance (NPM) is problematic. Thunderbird was getting a generic SSL certificate instead of ! I soon found out even through NPM handles the SSL offloading for port 443 (HTTPS web traffic), it doesn’t do the same for the mail ports (143, 993, etc). Once I tried to connect Thunderbird though I got SSL verification errors. The docker container comes complete with an admin site for managing users, domains, and server settings. Thanks to my local ISP I am able to have port 25 and all the rest unblocked, normally ISPs don’t allow these ports. Community Applications plugin has a template ready to goĮmail requires more ports than just 443/80, but following their documentation I was able to get it up and running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |