I wonder why people encounter these problems only now with DMARC in place,
if an SPF policy is set to strict you already see these issues.

Steve points it out already, to work around these issues with setting the
headers properly (option 1). (envelope-from, from, reply-to)

When building forms and you're using a protected domain (SPF/DKIM/DMARC)
which you do not have control over you are technically acting like a
phisher.

Regards,

Alwin


2014-05-05 3:09 GMT+02:00 Steve Atkins <[email protected]>:

>
> On May 4, 2014, at 4:55 PM, Gary Philips <[email protected]> wrote:
>
> > any potential customer of mine coming from my website contact page that
> has a yahoo.com reply address is blocked
> > with this explanation: Unauthenticated email from yahoo.com is not
> accepted due to domain's 550-5.7.1 DMARC policy.
> >
> > contact requests from all otherm @anyone.com comes through.
> > how can i fix this?
>
> You have several choices.
>
> 1. Change your contact form to not send mail "From:" the address that's
> given, rather have it sent from an email address you own (that is not at
> Yahoo) and put their address in the Reply-To: field.
>
> 2. Stop using Yahoo to receive your contact form emails (though stopping
> using it altogether would be an excellent idea, given they've demonstrated
> their inability to provide reliable email service).
>
> 3. Both 1 and 2.
>
> Cheers,
>   Steve
>
>
> _______________________________________________
> dmarc-discuss mailing list
> [email protected]
> http://www.dmarc.org/mailman/listinfo/dmarc-discuss
>
> NOTE: Participating in this list means you agree to the DMARC Note Well
> terms (http://www.dmarc.org/note_well.html)
>
_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)

Reply via email to