[FOLIO-2274] All patron notices aren't being sent (snapshot) Created: 20/Sep/19 Updated: 03/Jun/20 Resolved: 04/Oct/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Darcy Branchini | Assignee: | Darcy Branchini |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | cannot-reproduce | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Vega |
| Description |
|
Overview:
Steps to reproduce:
Expected results:
Actual results:
This was verified as an issue by Vega during a standup call on 9/20. |
| Comments |
| Comment by Kostyantyn Khodarev [ 24/Sep/19 ] |
|
Darcy Branchini tried to reproduce and found
{
"notificationId": "7d15a865-5227-49d7-9585-58e140d082aa",
"from": "noreply@folio.org",
"to": "kostyantyn_khodarev@epam.com",
"header": "test check out subject",
"outputFormat": "text/html",
"body": "<p>Dear kkhodarev</p><p><br></p>",
"attachments": [],
"status": "FAILURE",
"message": "Error in the 'mod-email' module, the module didn't send email | message: sending data failed: 554 Access denied: User `arn:aws:iam::786746151229:user/ses-smtp-user-noreply-at-folio-org' is not authorized to perform `ses:SendRawEmail' on resource `arn:aws:ses:us-east-1:786746151229:identity/noreply@folio.org'",
"date": "2019-09-24T15:05:14.757+0000",
"metadata": {
"createdDate": "2019-09-24T15:05:14.669+0000",
"createdByUserId": "55ba0563-b613-52ba-9466-ae78b75ebb31",
"updatedDate": "2019-09-24T15:05:14.669+0000",
"updatedByUserId": "55ba0563-b613-52ba-9466-ae78b75ebb31"
},
"deliveryChannel": "email"
}
|
| Comment by Darcy Branchini [ 26/Sep/19 ] |
|
Thanks Kostyantyn Khodarev, do you know why we'd get an access denied? Is this a send email address that was setup for notices? It's not related to the admin user, correct? |
| Comment by Kostyantyn Khodarev [ 27/Sep/19 ] |
|
Darcy Branchini i assume this issue is related to bounced email message problem (please see #hosted-reference-envs for details), SMTP credentials were changed and it was a root cause |