Has anyone found a clean workaround?
Sending email through lds.org/messaging is and has been a problem with AOL for a number of years. They started enforcing a new policy called "DEMARC". I am adding stake clerk-IT counterparts because this is a church-wide issue. Yahoo has started enforcing DEMARC policy as well. Their users hate it: http://www.spamresource.com/2014/04/up- ... olicy.html
* http://postmaster-blog.aol.com/2014/04/ ... to-reject/
** That's what the 554 code means that AOL places in the kick back alerts.
* Summary of an AOL code 554 bounce...Solution options:Church broadcast email messages pretend to be coming from your real provider (i.e. gmail.com). DEMARC policy rejects these messages as spam where the DNS address of the real sender (lds.org) doesn't match the "From:" field in the email. (gmail.com).
* Suggest members get a real email provider and dump AOL
** I am aware we can't say this from the pulpit but it would make a clerks life easier!
* A more politically correct statement from a pulpit would be:
** Please be advised AOL is rejecting ward/church broadcast messages. We are working with Church's IT Support to review options to remedy. AOL users please share your email address with your HT, so they know to call you directly in the event of urgent announcements.
* I didn't say it would be a clean message, just the best short term option.
* I've added CHQ's GSC (Global Support Center) to look into this problem, read the AOL DEMARC policy and see if any of the workarounds are reasonable.
* The stake clerk may have a more direct support path with CHQ IT.
* There is nothing more we can do.