Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subscriptions of Items are sending mails to non-subscribers #380

Closed
olli-gold opened this issue Aug 30, 2023 · 0 comments · Fixed by #381
Closed

Subscriptions of Items are sending mails to non-subscribers #380

olli-gold opened this issue Aug 30, 2023 · 0 comments · Fixed by #381
Labels

Comments

@olli-gold
Copy link

Describe the bug
The subscription script (bin/dspace subscription-send) is sending emails with wrong content to persons. After a person has gotten an email with the contents subscribed by them, the next person will get the same content (additional to the content they have really subscribed to). The problem only affects subscriptions of items (for instance persons) to get notifications, when the person was added to a publication.

To Reproduce
Steps to reproduce the behavior:

  1. Be sure, that you have at least one person with a valid item subscription on your system and many more, who do not have a subscription
  2. Be sure to have at least one publication, which was added or changed according to the existing subscription
  3. Be sure not to send unwanted emails (for example by changing the email settings mail.server.disabled = true and mail.server.fixedRecipient in local.cfg)
  4. Start the script bin/dspace subscription-send
  5. Wait, until you get an email for the existing subscription
  6. See, that after that others will follow (unless this person was the last person to be performed incidentally)

Expected behavior
The persons should only get emails about their subscribed content.

Related work
2e7ff80

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant