[DSpace 8.1] subscription-send script does not send emails despite valid subscription and archived item

[Lucas Silveira]

Dear DSpace team,

I'm using DSpace 8.1 on Oracle Linux 9 and encountered unexpected behavior with the subscription-send script.

Environment:

• DSpace version: 8.1 (backend and frontend)

• OS: Oracle Linux 9

• Email service: working correctly (submission and workflow notifications are sent successfully)

Scenario:

• A user subscribed to a collection (not a community) via the user interface.

• The subscription is stored correctly in the database:

  • type = content

  • eperson_id and dspace_object_id refer to the correct user and collection UUIDs

• A new item was submitted and archived in that same collection, with dc.date.accessioned set to today's date (confirmed via SQL).

• The subscription-send script was executed with all frequency modes:

  ./dspace subscription-send -f D ./dspace subscription-send -f W ./dspace subscription-send -f M

Behavior observed:

• The script only outputs:

  The script has started The script has completed

• No email is sent to the subscribed user.

• No processing logs appear, even when running with /bin/bash -x or with DEBUG level configured in log4j2-cli.xml.

• No errors are present in the logs.

• We verified that the item was correctly ingested, is publicly visible, and belongs to the subscribed collection.

Additional tests performed:

• Confirmed SMTP is functional.

• Subscribed with multiple users to the same collection.

• Submitted multiple new items.

• Confirmed the subscription in the database with this query:

  SELECT * FROM subscription WHERE dspace_object_id = 'collection-uuid';

• Verified dc.date.accessioned is correct.

Question:

Is this a known issue in DSpace 8.1?
Are there any additional configuration steps required for the subscription-send script to work properly?
Should I open a formal issue in the GitHub repository?

Any help or clarification would be greatly appreciated.

Best regards,
Lucas Ângelo da Silveira