Ran in to this weird problem today. Made a form for someone and data gets sent to her gmail account. When she filled out the form to test it, she put her AOL email address in the email field of the form. The form processed fine but she immediately got an email back to her AOL address that the email was rejected. I tested it using my AOL address and confirmed what she told me. I filled it out again using a different email domain and it went through. Exact wording kicked back on the error was..

email_form_going_to@gmail.com
host gmail-smtp-in.l.google.com [74.125.70.26]
SMTP error from remote mail server after end of data:
550-5.7.1 Unauthenticated email from aol.com is not accepted due to domain's
550-5.7.1 DMARC policy. Please contact administrator of aol.com domain if this
550-5.7.1 was a legitimate mail. Please visit
550-5.7.1 https://support.google.com/mail/answer/2451690 to learn about DMARC
550 5.7.1 initiative. f9si5381203iod.184 - gsmtp


Action: failed
Final-Recipient: rfc822;email_form_going_to@gmail.com
Status: 5.0.0
Remote-MTA: dns; gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 550-5.7.1 Unauthenticated email from aol.com is not accepted due to domain's
550-5.7.1 DMARC policy. Please contact administrator of aol.com domain if this
550-5.7.1 was a legitimate mail. Please visit
550-5.7.1 https://support.google.com/mail/answer/2451690 to learn about DMARC
550 5.7.1 initiative. f9si5381203iod.184 - gsmtp.

The weirder thing is....... I did a form for someone else that uses a gmail account and I filled hers out and put in my AOL address on the form and that went through just fine.

I dont know use gmail so not sure if there is a specific setting or something. Anyone else run in to this?

OH and I just altered the email address in the error code above to email_form_going_to@gmail.com for this post (not the email I am using on the form)

Someone did reply to me in an email about this and said.....

Yahoo and AOL have implemented a DMARC security policy that requires all e-mail sent from a Yahoo/AOL address (like using Gmail’s Send Mail As option) to actually come from Yahoo/AOL servers, or it must be rejected. The outgoing SMTP configuration need to be removed and re-created to use Yahoo/AOL SMTP servers. See: https://productforums.google.com/d/topi … discussion Yahoo help article: https://help.yahoo.com/kb/mail/SLN4075.html AOL announcement: http://postmaster-blog.aol.com/2014/04/ … to-reject/ Gmail help article: https://support.google.com/mail/answer/2451690

Is there anything we can do in our form settings to overcome this?

Can we test the form?

Yes but it will only kick it back if you put an AOL address in the email field. It processes the form but an email gets sent back to whatever AOL email address is inputted
http://appleandrosephotography.com/contact.php

And here is an even stranger thing.... I have another person I made a form for that has the data come to a Gmail account. I went and tested hers and put an AOL email address in and that one goes through just fine

Have you contacted the host?

Of Gmail? Just posted in their Help forums and a rep gave me this response
Yahoo and AOL have implemented a DMARC security policy that requires all e-mail sent from a Yahoo/AOL address (like using Gmail’s Send Mail As option) to actually come from Yahoo/AOL servers, or it must be rejected. The outgoing SMTP configuration need to be removed and re-created to use Yahoo/AOL SMTP servers. See: https://productforums.google.com/d/topi … discussion Yahoo help article: https://help.yahoo.com/kb/mail/SLN4075.html AOL announcement: http://postmaster-blog.aol.com/2014/04/ … to-reject/ Gmail help article: https://support.google.com/mail/answer/2451690

Did get it working today though. In the settings for the form I only had the "Reply to" section filled out with [EMAIL] So I kept that in place and put an email address in the "From" Field that was from my server and now the form data comes through fine when a person puts in an AOL Email Address !

There you go.

Captain Ron - Thank you so much for this information. We are now having Google handle our non-profits email and ran into this problem with forms that were previously received without issue. Changing the From address has solved the problem.