Send a Message Emails Not Delivered

[gordonja]

I regularly send emails via the Send a Message function on LCR (at least 2 or 3 messages a week). Until ten days ago it was working very well. Last Saturday (2/15), I sent one of my regular emails and received the confirmation email from LCR, but didn’t receive the actual message (I’m part of the recipient list and have always received both the confirmation and the message itself). The next morning, in my meeting, no one who was there had received the email. The following Saturday (2/22), when I sent my email, the same thing happened. This time I forwarded the confirmation message to the individuals who needed to receive the message via Google Mail. Last night and tonight I sent a couple other emails with the same results. I have never seen this problem before and all of my recipients have previously received my messages. I really need this feature to work in order to fulfill my responsibilities. Has anyone else reported a similar issue? Nothing I have done in the last ten days is different than what I did for months before that when it worked for me.

Thanks for any help you can provide.

James Gordon

[ambldsorg]

Last night and tonight I sent a couple other emails with the same results. I have never seen this problem before and all of my recipients have previously received my messages.

It's possible that whatever email provider they're using has changed their perception of emails coming from mail.churchofjesuschrist.org (really Amazon SES).

It's possible that there have been recent changes in the Church email infrastructure; it's hard to say since nobody in these forums is an email administrator for the Church (or hasn't been willing or able to admit as much).

Without asking you to release sensitive information about your contacts, is there a commonality between the recipients? For example, are they all from the same email provider domain (e.g. Gmail, Hotmail, Yahoo, etc.), or is it across the board? My guess is that they are Gmail since that seems to be the most common choice for people these days (though I would personally recommend almost anything else).

I hate asking this very proverbial question, but... have you and they checked the SPAM folders? Gmail especially is draconian in how they handle emails that they think that their customers don't want to see.

This is an interesting observation, and not one that I've seen before:

I sent one of my regular emails and received the confirmation email from LCR, but didn’t receive the actual message

(clarification, I've not seen it where the sender who is also a recipient gets only the confirmation, and not the actual message).

Did the confirmation list any errors or failures of any kind?

Would you mind looking at the full headers of the confirmation email that you got and sharing the domain in the Return-Path "header" if your mail system publishes said header? For example, in most emails I've seen @amazonses.com as the "envelope sender" being used, something like:

Code: Select all

Return-Path: <****************-********-****-****-****-************-******@amazonses.com>

[bobconlon]

I am having the same issue, but only when I select the Reply to All function.
This is frustrating because in my calling I need that function to be operational so people can reply to the group and to know who is receiving the email I sent.

[ambldsorg]

I am having the same issue, but only when I select the Reply to All function.

That's a potentially critical observation. I don't have the ability to test the "Reply to All" function because it is inactive for me so I cannot check it.

Can anyone else confirm whether or not there is a difference in behavior when "Reply to All" is used versus without?

I regularly send emails via the Send a Message function on LCR

Does this behavior change for you as well with or without the "Reply to All"?

[gordonja]

The Reply All functionality does seem to be the culprit. Many of the messages I send I would like for the recipients to be able to reply to all, so, as a rule, I have checked that box. Depending on the recipients, it is sometimes disabled (for example, if I am sending a message to members not in certain leadership roles, I cannot select it). When I leave the box deselected, regardless of the audience, the message is delivered. If I check the box, the message is not delivered. This seems like a bug that may have been recently introduced, because I know I never saw this behavior before approximately 2 weeks ago and nothing has changed about my approach to sending messages.

[ambldsorg]

The Reply All functionality does seem to be the culprit.

I think this should be reported as a bug since there appears to be no documentation for what to expect from the experience. You could try contacting the Global Services Department.

[gordonja]

The Reply All functionality does seem to be the culprit.

I think this should be reported as a bug since there appears to be no documentation for what to expect from the experience. You could try contacting the Global Services Department.

I logged an issue with the Global Services Department. Thank you for your suggestions!