1223471 - SUMO: change email backend in settings_local.py

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Michael Cooper [:mythmon]]

To help with debugging email problems on Sumo, we're adding a bunch of logging. To do this, we'll need to change our email backend.

In kitsune/settings_local.py there is something like

  EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend

Please change this to

  EMAIL_LOGGING_REAL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'

To be clear: This is just changing the name of the variable form EMAIL_BACKEND to EMAIL_LOGGING_REAL_BACKEND.

This change can't go into effect until we merge and deploy the code in https://github.com/mozilla/kitsune/pull/2708. I'll update this bug when we can make these changes.

Comment 1

[:Atoll]

SUMO isn't hosted in community, so moving this out of that.

Setting needinfo? :mythmon since we can't proceed until you say so.

Comment 2

[Michael Cooper [:mythmon]]

Sorry. I cloned an old Sumo settings bug for this, which is why it had the wrong component. Thanks for the needs info. I'll clear it when this is ready to go.

Comment 3

[Michael Cooper [:mythmon]]

The related pull request has been deployed to the Sumo servers, so we can start this work now.

Can we do this first on stage, and then let it sit for a bit to make sure nothing explodes before moving on to prod? I'd really hate to break email on prod.

Comment 4

[C. Liang [:cyliang]]

* Added syslog invocation (include webapp::support::syslog) to SUMO web servers.
* Settings change pushed to stage; apache and celery processes restarted.

Comment 5

[Michael Cooper [:mythmon]]

I tested this. There was one small problem, which required a code change. After that, stage worked fine. I sent an email to myself with Sumo's PM system, and there were logs coming out.

The code change that is needed is in a PR here: https://github.com/mozilla/kitsune/pull/2731. After that land and gets deployed to prod, we can make the settings change there too.

Comment 6

[Michael Cooper [:mythmon]]

The code change is on prod. The settings change can happen on prod now.

Comment 7

[C. Liang [:cyliang]]

* Settings change pushed to production; apache and celery processes restarted.

I've confirmed that email logging entries now appear in the log (/var/log/local7.sumo.log).