Send a Message should originate from church email address
Posted: Mon Aug 10, 2015 7:06 am
Hello. I just went to use the Send a Message functionality from within the Leader Clerk Resources section of the website to send out a notice regarding funeral arrangements for a member from our stake. Unfortunately most the recipients did not receive the message. It looks as if the church website attempted to use my yahoo.com email address as the from email address. Which resulted in most of the messages being rejected by the receiving email servers. Shortly after sending the email from the LCR website I received a Mail Delivery Subsystem message which offered many different errors:
Emails to aol.com domain had the following result: reason: 521 5.2.1 : (DMARC:F1) This message failed DMARC Evaluation and is being refused due to the policy provided by the From domain.
Emails to gmail.com domains had the following result: reason: 550-5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's
Emails to microsoft domains (live.com, hotmail.com, msn.com etc) had the following result: reason: 550 5.7.0 (BAY004-MC2F4) Unfortunately, messages from (216.49.179.112) on behalf of (yahoo.com) could not be delivered due to domain owner policy restrictions.
Emails to yahoo.com domains had the following result: reason: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html
I believe this is a result of the church website using my personal yahoo.com email address as the from email address for the email. It would be better to have the emails originate from the church with a donotreply@lds.org email account or something along that line. You could simply append a statement at the top of the email stating who initialed the email and their personal email address if people wish to respond.
As a work around I exported the ward list and concatenate the member email addresses together to be comma separated and sent out the email directly from yahoo.com with the members blind carbon copied which worked properly and resulted in only a couple of kick back emails stating that the members email address was wrong which would be expected.
The idea of the "send a message" feature is nice but based on how it is currently being implemented it is useless as the receiving email provider servers are rejecting the messages because they do not originate from the domain they are stating to be from since you are using the members personal email address as the from email address.
Thank you!
Emails to aol.com domain had the following result: reason: 521 5.2.1 : (DMARC:F1) This message failed DMARC Evaluation and is being refused due to the policy provided by the From domain.
Emails to gmail.com domains had the following result: reason: 550-5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's
Emails to microsoft domains (live.com, hotmail.com, msn.com etc) had the following result: reason: 550 5.7.0 (BAY004-MC2F4) Unfortunately, messages from (216.49.179.112) on behalf of (yahoo.com) could not be delivered due to domain owner policy restrictions.
Emails to yahoo.com domains had the following result: reason: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html
I believe this is a result of the church website using my personal yahoo.com email address as the from email address for the email. It would be better to have the emails originate from the church with a donotreply@lds.org email account or something along that line. You could simply append a statement at the top of the email stating who initialed the email and their personal email address if people wish to respond.
As a work around I exported the ward list and concatenate the member email addresses together to be comma separated and sent out the email directly from yahoo.com with the members blind carbon copied which worked properly and resulted in only a couple of kick back emails stating that the members email address was wrong which would be expected.
The idea of the "send a message" feature is nice but based on how it is currently being implemented it is useless as the receiving email provider servers are rejecting the messages because they do not originate from the domain they are stating to be from since you are using the members personal email address as the from email address.
Thank you!