LCR “Send a Message” application NOT sending to yahoo.com accounts

[jdlessley]

... but I would second an earlier request that a notification be posted here confirming a resolution to the issue. (An explanation of how it was resolved would be appreciated as well )

The forum is primarily user-to-user and not an official support channel. As such, we seldom get official responses to technology issues. We also do not get the how and why of issues from an official source. Even those who provide feedback through official channels seldom get any followup response to a reported issue.

[gdgroesbeck]

Same problem August 22, 2021 on our ward level message to all adult members, and on a message to all from the stake as well. All rejected messages were from Yahoo email users. It would be nice if SLC could reach out to yahoo via back channels to see if they can change their filtering algorithm to allow messages coming thru form the Church system.

[garystroble]

It appears to be fixed as of Monday, August 23. Please see earlier posts on this thread.

Suggest trying a test message to a few known yahoo accounts and see if it works correctly now.

[jbail7]

As of Saturday, August 29. It still doesn't appear to be working.

[linzogonzerelli]

I sent a ward email out this morning (8/29) and the AOL and Yahoo emails were bounced back.

[Melyssak]

We are still having problems with the church email service. I am not sure if it is only yahoo and AOL.

[garystroble]

Having problems again today also with the yahoo and aol accounts.

[ramonc]

Same problem here also. I can report that Thursday around 6:00pm MDT it did work. 8/29 got "The recipients below were rejected by the server. Please verify their email addresses." They were all yahoo.com email addresses

[dcacpa]

Similar problem. I'm serving as stake clerk. I recently sent a message to all adults in the stake and over 100 e-mails bounced back. All were Yahoo or AOL e-mail addresses. I was sending from a gmail account. It does seem blacklisting may be the issue.

[jonahern10]

I had the same problem on a Ward email sent out on 8/28.