{"action":"opened","issue":{"url":"https://api.github.com/repos/BiologicalRecordsCentre/iRecord/issues/384","repository_url":"https://api.github.com/repos/BiologicalRecordsCentre/iRecord","labels_url":"https://api.github.com/repos/BiologicalRecordsCentre/iRecord/issues/384/labels{/name}","comments_url":"https://api.github.com/repos/BiologicalRecordsCentre/iRecord/issues/384/comments","events_url":"https://api.github.com/repos/BiologicalRecordsCentre/iRecord/issues/384/events","html_url":"https://github.com/BiologicalRecordsCentre/iRecord/issues/384","id":335957153,"node_id":"MDU6SXNzdWUzMzU5NTcxNTM=","number":384,"title":"Email notifications failing to send?","user":{"login":"kitenetter","id":16039111,"node_id":"MDQ6VXNlcjE2MDM5MTEx","avatar_url":"https://avatars3.githubusercontent.com/u/16039111?v=4","gravatar_id":"","url":"https://api.github.com/users/kitenetter","html_url":"https://github.com/kitenetter","followers_url":"https://api.github.com/users/kitenetter/followers","following_url":"https://api.github.com/users/kitenetter/following{/other_user}","gists_url":"https://api.github.com/users/kitenetter/gists{/gist_id}","starred_url":"https://api.github.com/users/kitenetter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kitenetter/subscriptions","organizations_url":"https://api.github.com/users/kitenetter/orgs","repos_url":"https://api.github.com/users/kitenetter/repos","events_url":"https://api.github.com/users/kitenetter/events{/privacy}","received_events_url":"https://api.github.com/users/kitenetter/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-26T19:19:48Z","updated_at":"2018-06-26T19:19:48Z","closed_at":null,"author_association":"COLLABORATOR","body":"We've now had three verifiers report that they are no longer receiving notification emails that alert them to incoming records that need verification, even though they are set up to do so and have received them in the past. When the first one was reported we thought it might be a one-off problem to do with the user's spam filtering, and @johnvanbreda suggested:\r\n\r\nIf you run:\r\n`Select * from notifications where user_id=88957 order by id desc limit 10`\r\nYou can see that the user is getting notifications (the ones for type VT are “verifier tasks”, i.e. notifications that there is stuff to do). The email_sent=t implies that the code thinks it has sent an email in relation to these notifications. \r\n\r\nSo, the possibilities are:\r\n1)\tThe code errored and didn’t send an email. This is unlikely as we would probably see other failures and trapped error messages in the logs.\r\n2)\tThe email configuration on the server failed to send the email. Again seems unlikely as it is working for other scenarios.\r\n3)\tThe email is getting trapped as spam but not ever reaching the user's spam filter (e.g. their email service is trapping it).\r\n\r\n@BirenRathod is it possible to check the logs for email sent items to investigate option 2?\r\n\r\nOne of the other users involved is user_id=14037 (let me know if you also need the third user id)."}}
{"actor":{"display_login":"kitenetter"}}