-
Notifications
You must be signed in to change notification settings - Fork 63
Initialization
Much of NEMO's functionality relies on sending emails, so it is important to ensure it interfaces correctly with your organization's email server. The Django documentation contains a reference of all email related settings that can be configured for NEMO. All the relevant settings begin with EMAIL_
. The most important ones to configure are, EMAIL_HOST
, EMAIL_PORT
, EMAIL_USE_TLS
, and EMAIL_SSL_CERTFILE
.
We highly recommend using TLS when sending email. This prevents unauthorized parties from intercepting, reading, or modifying emails.
When you're ready to test your settings, you can use django-admin
to send a test email. Configure your settings.py first. Then, invoke django-admin
from the command line:
django-admin sendtestemail [email protected]
If you get an error, or do not receive the test email, you can ask questions on the NEMO email list. If you encounter a problem that you think is particularly common, please help us by improving the documentation on this wiki.
In a production deployment of NEMO, the site should be served from a domain name such as nemo.example.org
. ALLOWED_HOSTS
controls where NEMO site content can come from.
TO DO: discuss email, LDAP servers, allowed hosts, database (with dbshell), external certs
- systemd configuration (automatic startup on boot, and more)
- ensure the firewall is open on TCP port 443