Bug #21754
closedReclaim email notifications
0%
Description
I have been doing my best to trigger all of the different email notifications in Reclaim. Here's my list of emails that aren't being sent. I've turned on all notifications in Settings and confirmed for group tasks that the group is set to All Email.
- Private member-to-member message
- Invite to join group
- Upload group document (sent to members of the group)
- New forum post or reply (sent to members of the group)
- New group event (sent to members of the group)
I have been checking spam, cross-referencing with GC production behavior, and using CUNY and non-CUNY emails to try and make sure I am just not receiving the emails due to something on my end. In case it helps, these are email notifications I've confirmed are being sent and received:
- Friendship request made
- Friendship request accepted
- Group details updated
- Promoted to admin or moderator
- Request to join private group (sent to admin)
- Request to join private group approved or denied
- All new account registration emails
- Password or email changed
Related issues
Updated by Boone Gorges 27 days ago
You mentioned in an earlier message that there seemed to be differences between different email addresses - you would receive emails as expected at one address, but not at another. Is that still the case? If so, how does that intersect with the report above?
Updated by Boone Gorges 27 days ago
A number of the items on the not-working list (upload group documents, new forum post, new group event) are powered by BPGES. It's likely that BPGES emails are not going to work as the server is currently configured. When you create a new activity item in a group, BPGES adds this item to a queue, and then launches an asynchronous request to trigger the batch-sending of notifications from the queue. This request uses wp_remote_get()
with an endpoint of the form https://commons.gc.cuny.edu/admin-ajax.php...
(part of the WP_Background_Processing library). This means that PHP tries to make a cURL request to https://commons.gc.cuny.edu. This is going to fail for two reasons: 1. commons.gc.cuny.edu points to the GC server (there's no custom hosts configuration, so the Reclaim server uses DNS records from public nameservers), and 2. even if it were pointed at the Reclaim dev site, the SSL cert is not configured properly, so the cURL request will likely fail. It would be nice if BPGES were a bit more resilient here, but I don't see an easy way to make it happen. I do think that it will just work as expected once we've switched over DNS, so I'd like to propose that we don't spend any more time testing or debugging BPGES-related emails.
I'm going to spend some time debugging other email types.
Updated by Colin McDonald 27 days ago
My earlier message was referencing an issue that I think was related to my Brooklyn College email address specifically, which more or less tracks because their email system has been unreliable for me in the past.
I ended up doing all of the testing for the above list with separate Commons accounts tied to my GC email and an ordinary Gmail account. Those same two accounts, tied to the same emails, on GC production deliver the emails that I noted not being able to receive on the Reclaim environment.
Thanks for the info about BPGES, Boone. I think it would be ok to hold off on testing those emails further, and be ready to test them right away post-migration to confirm everything is ok. Is it possible to generate a list of all BPGES emails that I could use as a checklist for that?
Updated by Boone Gorges 27 days ago
Is it possible to generate a list of all BPGES emails that I could use as a checklist for that?
Not easily. Basically, it's anything that creates an activity entry in the Activity tab of a group. New topic, topic reply, etc: https://commons.gc.cuny.edu/groups/test-group-1268270862/
Updated by Colin McDonald 27 days ago
Ok understood, I can do some post-migration testing based on that.
Updated by Boone Gorges 27 days ago
- Related to Feature #21456: Switching to SMTP for outgoing email added
Updated by Boone Gorges 27 days ago
- Target version set to Migration to Reclaim
I believe I've identified the issue with private message notifications. See https://redmine.gc.cuny.edu/issues/21456#note-10
Updated by Boone Gorges 27 days ago
Emails from cac-onboarding (invitations to join the Commons, a site, or a group) are not working for the same reason as BPGES emails: they rely on WP_Background_Processing. They too should begin working when DNS is switched over.
Updated by Colin McDonald 20 days ago
- Status changed from New to Resolved
I've been testing the list of emails that weren't being sent from my initial post in this ticket, and I think everything is sending and working well now. I'm going to mark this ticket as resolved.