You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Increasingly we're finding that the admin email address isn't appropriate for all situations and it would be good to separate 'system admin' and 'from address' in more places.
An example of this is where we manage the CA deployment but the site is managed by an experienced person at the customer site.
I've had a quick look through providence looking for references to __CA_ADMIN_EMAIL__ and ca_admin_email and tried to determine who would be responsible.
app/lib/Plugins/TaskQueueHandlers/dataExport.php - data exports are a customer thing
app/lib/Utils/CLIUtils/Maintenance.php - fixity reports are a hosting thing
app/lib/Utils/CLIUtils/Test.php - test emails are a hosting thing
app/lib/Utils/CLIUtils/Localization.php - probably a hosting thing
app/lib/BatchProcessor.php - batch processes are probably a customer thing
app/models/ca_users.php - account setup probably a hosting thing
app/conf/oai_provider.conf - is configurable, but i imagine it would default to customer setting.
I suggest a new setting __CA_CONTACT_EMAIL__ or similar to separate the two tasks. I'm aware this introduces the possibility that admin and contact emails would be sent to different mail servers and as such might need separate mail configuration - I haven't dug in to that part of the problem though.
The text was updated successfully, but these errors were encountered:
Oh, and I should say I didn't look at pawtucket at all. I'm aware of other places admin email displays (ban hammer error page for example), the list above is more of a starter than comprehensive list.
Increasingly we're finding that the admin email address isn't appropriate for all situations and it would be good to separate 'system admin' and 'from address' in more places.
An example of this is where we manage the CA deployment but the site is managed by an experienced person at the customer site.
I've had a quick look through providence looking for references to
__CA_ADMIN_EMAIL__
andca_admin_email
and tried to determine who would be responsible.app/lib/Plugins/TaskQueueHandlers/dataExport.php
- data exports are a customer thingapp/lib/Utils/CLIUtils/Maintenance.php
- fixity reports are a hosting thingapp/lib/Utils/CLIUtils/Test.php
- test emails are a hosting thingapp/lib/Utils/CLIUtils/Localization.php
- probably a hosting thingapp/lib/BatchProcessor.php
- batch processes are probably a customer thingapp/models/ca_users.php
- account setup probably a hosting thingapp/controllers/administrate/access/UsersController.php
- account steps hosting, comment notifications customer thingapp/conf/oai_provider.conf
- is configurable, but i imagine it would default to customer setting.I suggest a new setting
__CA_CONTACT_EMAIL__
or similar to separate the two tasks. I'm aware this introduces the possibility that admin and contact emails would be sent to different mail servers and as such might need separate mail configuration - I haven't dug in to that part of the problem though.The text was updated successfully, but these errors were encountered: