----- Original Message ----- > From: "Dave Crocker" <dcroc...@gmail.com> > To: "Franck Martin" <fra...@peachymango.org> > Cc: dmarc@ietf.org > Sent: Wednesday, May 28, 2014 3:48:39 PM > Subject: Re: [dmarc-ietf] Solution for DMARC disruption of normal email use > while still offering its normal > protection > > On 5/28/2014 3:45 PM, Franck Martin wrote: > > Before one can move to p=reject, it needs to take control of all the email > > streams. > > > OK. Thanks for the clarification.
You are welcome > > The examples you provide are for third parties that have a business > relationship with the domain owner. > > The interesting challenge is when a random user sends legitimate mail > from an un-associated third party. > In many cases the domain owner IT department does not know an employee decided to use/contract someone to send emails... This case is not too far from the one Jim pointed to, and amount to detect and then inform the third party to pick from a set of possible solutions. _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
