Hi Edward,

How do I make it work for Inbound if my MTA/AntiSpam does not support? Not
sure if I understood your question correctly but would appreciate if you
can shed some light on this? lets say I am on google apps.

Google Apps I guess bydefault takes care of Incoming mail. But what if I am
using third party MTA which does not support Inbound DMARC checks? Yes most
of them do support SPF and DKIM validation but not DMARC I guess.

Please correct me if I am wrong.

Thanks and regards,
Blason R

On Wed, Jan 9, 2019 at 7:00 PM Edward Siewick via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:

> Blason,
>
> Actually, consider implementing testing (SPF, DKIM) and DMARC for
> inbound.  Since you've implemented for everybody else, why not put these to
> use for your own organization?
>
> Edward S.
>
>
> On 1/8/2019 10:26 PM, Blason R via dmarc-discuss wrote:
>
> Hi DMARC Team,
>
> What I understand is DMARC is very beneficial for the mails which are
> being sent from my domain to third party. But can we stop the emails coming
> at me pretending to be my own domain? My assumption again here is we can
> not and need to have AntiSpam policy to block looking at SPF and DKIM?
>
> TIA
> Thanks and Regards
> Blason R
>
> _______________________________________________
> dmarc-discuss mailing 
> listdmarc-discuss@dmarc.orghttp://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
> dmarc-discuss@dmarc.org
> 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
dmarc-discuss@dmarc.org
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