davesudweeks wrote:
"the fact th[at] BYU seems to not forward the church emails... It appears the messages are delivered to the BYU email server "
2 cougars reports exactly
the opposite in his posting at
https://tech.churchofjesuschrist.org/fo%20...%20ng#p199065 from which I quote (underline is mine):
2cougars said:
I just got off the phone with BYU IT and they are calling the church support. One of the BYU help desk techs set up a new byu.net email and changed his church account to his new byu.net email address. He did not receive the verification email either. They were watching on the byu.net side of things and nothing arrived at their servers from the church domain. Church support said to submit feedback through the main church website.
Bottom line is the church systems were changed a few months ago and they will no longer send any emails to byu.net addresses. They need to fix the issue. It's not user error.
My conclusion from 2cougars reported discussion with byu.net system administrators is that byu.net servers
do NOT receive expected messages from LCR Messaging which are directed to byu.net email addresses. For this reason byu.net IT contacted church support.
Since 2cougars interaction with byu.net IT and their interaction with church support seems without question to indicate that the problem is with LCR messaging, and this occurred on Jul 29, 2019, and nothing has yet been done to address the problem, I despair to think that anything else could be done by myself as a user to encourage the problem to be fixed. During the past week I took the only action open to me with my current email setup, which was to put my ISP email address, with @comcast.net, into my church profile instead of the @byu.net address which has been there for many, many years. After doing so, emails from local leaders resumed, including emails about local virtual Sunday meetings announced by my ward leaders. Thus my current problem of receiving local leader communication has been solved, but not in the way which I hoped.