Sometimes emails are going through Mailgun instead, but Mailgun setting is nowhere to be found?

[saleemepoch]

We have an instance of Taiga installed on our production server, and I've been noticing something strange lately:

Most Taiga notifications are coming from the specified SMTP server as configured in settings/local.py.

Sometimes, let's say one in twenty, a notification of exactly the same type and nature ends up coming from Mailgun, and is understandably flagged by G Suite as possible Spam or Phishing.

We did have it configured to use Mailgun once, but for a while, we've been using our own SMTP server. I searched all the files for Mailgun related string (mg.ourdomain.com) and it's nowhere to be found.

What's really puzzling is that it only happens every so often, whereas the bulk of the emails come through our specified SMTP server.

Where can I look to trace this issue?

[theriverman]

Have you touched commons.py directly? See what git status says. Did you restart both taiga-back & taiga-celery when you removed the mail gun settings?

[saleemepoch]

I did, but only to change the locale to Europe/London, and that's the only change git status reports.

I am pretty sure I restarted taiga-back and taiga-celery when I last updated but I just re-started them again in any case.

And yet again, I received two notifications from Taiga from two different tasks, literally one minute apart. They are both titled 'Updated the task #xxx' for the same project, coming from the same email address: [email protected]

One is from our specified SMTP and the other is using Mailgun and marked as potential phishing.

I find this really weird because there is nowhere mailgun is mentioned in any of the files. I checked by running grep -R 'mailgun' taiga/ | more and there is no mention.

Is there a way to debug this?