Tech Forum

For some time now (maybe 4 years), my ward and stake have been unable to send me any email using the LCR "Send a Message" tool. If they send it from their own personal email it works fine. When they do send an email using LCR, they get back a notice from LCR that states:

The recipients below were rejected by the server. Please verify
their email addresses.

I know for a fact that the email addresses are working and that the server listed as the MX is not rejecting email so "the server" must necessarily refer to something else. We have verified that they work. The Church must have an internal blacklist to which my email address has been added. How do I request that this email address be removed from said blacklist? In a strangely ironic twist, when I called the "frontline" they sent me an email from ServiceNowGSC that requested details about the problem to which I responded with pertinent details, but I have not heard anything from that time (it's been almost a month since I responded). Perhaps they did respond but the Church blacklist also blocked them from communicating.

Just updating this topic with additional findings. The Church uses Amazon SES for sending emails to members. The switch to Amazon SES happened about 4 years ago if memory serves (which coincides with when I stopped receiving email messages).

Amazon SES does maintain a blacklist (they call it a suppression list) and it's likely that this is the cause of many woes for members who cease to receive LCR generated emails from their ward or stake.

The Church has the ability to manage this list and therefore should be empowered to remove members who end up on this list:

https://docs.aws.amazon.com/ses/latest/ ... -list.html

Amazon SES does also have a "global suppression" list, however, according to the documentation, addresses on this list are not permantently blocked but may be blocked for a period of up to 14 days:

https://docs.aws.amazon.com/ses/latest/ ... -list.html

Now, I have no authority to communicate with Amazon SES as I have no contractual relationship with them. The Church, however, does have a relationship with them by virtue of the fact that they are using the service and therefore should be able to contact them (or use the appropriate tools or APIs mentioned above) and resolve this issue. Whether or not there is anyone inclined to do so is another matter.