sevein
commented
6 years ago Changing the logging level for this output from info to debug should (I think) also help devs see the information they need without removing this verbosity entirely. That might be worth a try.
Our default email backend is django.core.mail.backends.console.EmailBackend which is not using the logger but it's writing to sys.stdout. A good solution could be to use the file backend (https://docs.djangoproject.com/en/dev/topics/email/#file-backend) but I'm not sure what'd be a good place to put the file, maybe in the tmp inside the AM shared directory?
You can change the backend plus other settings via environment strings. They're listed in our install/ READMEs. We don't have an overview of email config in our docs yet but there are some notes here: https://github.com/artefactual/archivematica/pull/813.
Please describe the problem you'd like to be solved.
Currently, the output in the logs for the email fail report is quite verbose as it contains the entire HTML formatted message:
Describe the solution you'd like to see implemented.
I'd like to see a neater summary generated that provides developers with the logging they need for this particular script without outputting the entire content of this mail.
Describe alternatives you've considered.
Changing the logging level for this output from info to debug should (I think) also help devs see the information they need without removing this verbosity entirely. That might be worth a try.
Additional context
I am currently working in
qa/0.xbranch.