mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-11-03 12:48:53 -06:00
Rob Crittenden
03caa7f965
Add options for character set (default utf8) and message subtype (default plain). This will allow for more control for users to do either HTML mail or use ascii for the character set so the attachment is not base64-encoded to make it easier for all mail clients. Collect first and last name as well for each user in order to provide more options for the template engine. Make the From address configurable, defaulting to noreply@ipa_domain Make Subject configurable too. Don't rely on the MTA to set Message-Id: set it using the email module. Fixes: https://pagure.io/freeipa/issue/3687 Signed-off-by: Rob Crittenden <rcritten@redhat.com> Reviewed-By: Michal Polovka <mpolovka@redhat.com> Reviewed-By: Christian Heimes <cheimes@redhat.com>
Ground rules on adding new schema Brand new schema, particularly when written specifically for IPA, should be added in share/*.ldif. Any new files need to be explicitly loaded in ipaserver/install/dsinstance.py. These simply get copied directly into the new instance schema directory. Existing schema (e.g. in an LDAP draft) may either be added as a separate ldif in share or as an update in the updates directory. The advantage of adding the schema as an update is if 389-ds ever adds the schema then the installation won't fail due to existing schema failing to load during bootstrap. If the new schema requires a new container then this should be added to install/bootstrap-template.ldif.