[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:

  • I was trying to test notices on folio-snapshot in order to close MODTEMPENG-25 Closed . However, no notices were being received.

Steps to reproduce:

  1. Setup patron notice template for check out
  2. Setup patron notice policy with template (from above) referenced
  3. Setup circulation rules with policy (from above) referenced
  4. Setup a user with an email address that can be accessed
  5. Check out an item to user (from above)

Expected results:

  • Receive notice after check out

Actual results:

  • Patron notice not received

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
Or possibly issue with docker container
Could this bug be closed now?

Generated at Thu Feb 08 23:19:28 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.