Closed tbar0970 closed 6 months ago
DMARC is the standard which is starting to be applied by major email vendors. It requires SPF/DKIM verification on the RFC5322.From address specifically. It doesn't really care about the sender address.
In the case where the relevant email domain somechurch.org
hasn't been configured with SPF/DKIM records to allow Jethro to send from it, the best solution would be for Jethro emails to be From: noreply@jethrohost.net
(DMARC complaint) and Reply-to:info@somechurch.org
We'll need to add new config settings to allow for this.
As well as member account rego, consider task reminders, emailed reports, date reminders
Another possible implementation:
Add a config setting 'OVERRIDE_EMAIL_FROM', set in the conf.php file If it's set, then include/emailer.class.php will use OVERRIDE_EMAIL_FROM as the actual from address, and convert any user-supplied 'from' address to a 'reply-to'
That way we don't have to add reply-to support in a a bunch of different places.
Jethro system admins can configure the from-address for account rego emails. This can lead to issues if their domain doesn't have DKIM config to allow the Jethro sender to send from it.
To investigate: Can we use the "sender" header, or just "reply to" header, to avoid the need for DKIM reconfig.