AOL, Gmail, and Yahoo have published DMARC records, structured in a way to tell receiving servers to reject any email not originating from their mail servers. This was a step taken to address spoofed spam emails resulting from compromised email accounts at those providers.

The result is that any email sent which appears to be from aol.com, gmail.com, or yahoo.com, which originates from a different server (like eTapestry, NetCommunity, Delivra, or any other mail server not controlled by AOL, Gmail, orYahoo) will be rejected by any server checking DMARC records (including most if not all of the top domains like Hotmail, Comcast, Gmail, AOL, and Yahoo). 

The reason behind the decision can be found here http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/ and here http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders-do.

We anticipate that the rest of the free email providers will likely follow suit soon and publish their own DMARC records. 

 

What you need to do:
Stop using any address from a free email provider in the From line of mailings sent through eTapestry or NetCommunity. Switch to a domain that you own or have control over.
 
We realize that this places a burden on small businesses and organizations who may not have a domain that they own. Unfortunately, the issue is one that is controlled entirely by the email providers. 

For organizations using G Suite, settings can be changed and the SPF records can be configured to allow these emails to send. Please see https://support.google.com/a/answer/2466580?hl=en for information to set this up through Google. The IP addresses that eTapestry uses to send emails can be found in Why are emails sent from eTapestry being sent to Spam?.