----- Original Message -----
> From: "Dave Crocker" <[email protected]>
> To: "Franck Martin" <[email protected]>
> Cc: [email protected]
> Sent: Wednesday, May 28, 2014 3:29:30 PM
> Subject: Re: [dmarc-ietf] Solution for DMARC disruption of normal email use
> while still offering its normal
> protection
>
> On 5/28/2014 3:28 PM, Franck Martin wrote:
> > how you get third parties sending emails on your behalf to become
> > compliant.
>
>
> Please clarify what that means.
Before one can move to p=reject, it needs to take control of all the email
streams.
Here are a few use cases:
-sending marketing emails via an ESP
-sending surveys to employees and non-employees
-contracting a third party helpdesk
-contracting a third party Customer Relation Manager
-contracting a third party travel system
-Apps in the cloud and their notifications system
-mobile phones using the telecom provider email system
-service providers sending email to employees (HR, health, insurance,
retirement,...) to their employee address or personal address
-sending emails to interns/contractors, who like to forward everything to their
primary email account
-....
Some solutions: add to spf/give dkim key, delegate a subdomain, delegate
records in a subdomain, use the third party domain.
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
