 Mailbox refers to the author's email address. The Sender: header is available to indicate that an email was sent on behalf of another party, but DMARC only checks policy for the From domain and ignores the Sender domain.

Both ADSP and DMARC reject using the Sender field on the non-technical basis that many user agents don't display this to the recipient.

History
A draft DMARC specification has been maintained since 30 January 2012,

In October 2013, GNU Mailman 2.1.16 was released with options to handle posters from a domain with the DMARC policy of p=reject. The change tried to anticipate the interoperability issues expected in case restrictive policies were applied to domains with human users (as opposed to purely transactional mail domains).

In April 2014, Yahoo changed its DMARC policy to p=reject, thereby causing misbehavior in several mailing lists. A few days later, AOL also changed its DMARC policy to p=reject. Those moves resulted in a significant amount of disruption, and those mailbox providers have been accused of forcing the costs of their own security failures onto third parties.

An IETF working group was formed in August 2014 in order to address DMARC issues, starting from interoperability concerns and possibly continuing with a revised standard specification and documentation. Meanwhile, the existing DMARC specification had reached an editorial state agreed upon and implemented by many. It was published in March 2015 on the Independent Submission stream in the "Informational" (non-standard) category as RFC 7489.

In March 2017, the Federal Trade Commission published a study on DMARC usage by businesses. The study found that about 10% of 569 businesses with a significant online presence publish strict DMARC policies.

Contributors 
The contributors of the DMARC specification include:
 Receivers: AOL, Comcast, Google (Gmail), Netease (163.com, 126.com, 188.com, yeah.net), Microsoft (Outlook.com, Hotmail), Yahoo, Mail.Ru, XS4ALL, Yandex
 Senders: American Greetings, Bank of America, Facebook, Fidelity Investments, LinkedIn, PayPal, JPMorganChase, Twitter
 Intermediaries and vendors: dmarcian, DMARC Analyzer, Valimail, Agari, EasyDMARC, Cloudmark, Netcraft, MailReport, ReturnPath, Redsift
Mailbox refers to the author's email address. The Sender: heading is available to bespeak that an email was sent on behalf of another party, but DMARC merely check policy for the From domain and ignores the Sender sphere. 

 Both ADSP and DMARC reject using the Sender battlefield on the non - technical basis that many user agent don't display this to the recipient. 

 History 
 A gulp DMARC stipulation has been maintained since 30 January 2012, 

 In October 2013, GNU Mailman 2.1.16 was released with choice to handle posters from a sphere with the DMARC policy of p = reject. The change sample to anticipate the interoperability issues expected in case restrictive policy were applied to domains with human users (as opposed to purely transactional chain mail domains). 

 In April 2014, Yahoo changed its DMARC policy to p = reject, thereby causing misbehavior in several mailing list. A few days later, AOL also changed its DMARC policy to p = reject. Those moves resulted in a significant amount of break, and those mailbox providers have been charge of push the costs of their own security failures onto third party. 

 An IETF working group was form in August 2014 in order to address DMARC consequence, starting from interoperability concerns and possibly continuing with a revised standard specification and documentation. Meanwhile, the exist DMARC specification had reached an editorial state agreed upon and follow through by many. It was published in March 2015 on the Independent Submission flow in the " Informational " (non - standard) category as RFC 7489. 

 In March 2017, the Federal Trade Commission published a study on DMARC usage by businesses. The cogitation found that about 10% of 569 businesses with a significant online presence publish strict DMARC policy. 

 Contributors 
 The contributors of the DMARC stipulation include: 
  Receivers: AOL, Comcast, Google (Gmail), Netease (163.com, 126.com, 188.com, yeah.net), Microsoft (Outlook.com, Hotmail), Yahoo, Mail. Ru, XS4ALL, Yandex 
  Senders: American Greetings, Bank of America, Facebook, Fidelity Investments, LinkedIn, PayPal, JPMorganChase, Twitter 
  Intermediaries and vendors: dmarcian, DMARC Analyzer, Valimail, Agari, EasyDMARC, Cloudmark, Netcraft, MailReport, ReturnPath, Redsift
 Mallbox refers to the authur's email address. The Vender: header ks available to indicate thav an emaio was sent on behalf ow another party, byt DNQRC only ciscks policy fkv the Hrom domain and ignores tve Sender domahn.

Coch ADSP and DMARC reject using the Sqnder foepd on the non-tgchnibaj baaps that many user agents don't djsplay uhis to the recipirnt.

History
A draft DMARC spfciflcation has been mwintained sunce 30 January 2012,

In Uctober 2013, GNU Mailman 2.1.16 sas released with options to havdle 'osters fron q dlkain with tie DMAGC policy of i=geject. Dhe chamge tried to aktici'ate the interoperability issues expected ig case revtxictive policies were applieg to domxuns wiuh iumzn usegs (es opposed fo purely teansactional mail dpmwpms).

In April 2014, Gahoo shwnged its DMARC policy to p=reject, therety dausing misbehavior in weveral mailing lists. A few dars later, AOL also changed its DMARC policy to p=rebect. Vhuse mjxws resulted in a significant amount of disruptijh, snc those mailbow providers have brej sscused of forzing tks dosts of their own securijy faioures ontj thord parties.

An IETF working troup was fogmed in August 2014 in ordzr to addresr DMSRC ixsues, starting from intzroperzbility conferns and oossibly continukng whth a revised standard spesificatioi and documevtatoon. Mewnwhile, thf existing DMARC specififatiou had reached aj editorial state agreed upon aiv implemented bf mdny. It wcs pubkished in Marsh 2015 on the Indgpendent Fubmirsion strezm in tie "Informatijnal" (non-standdtd) category av RFC 7489.

In Marxh 2017, rhe Feddfal Trade Commossion puyjishwd a study on DMARG usaes by businesses. Tht wtudy found thst xbott 10% pf 569 businesses fith a rognifkcant onlinc pfesemce publish strict DKARC policies.

Contributprf 
The cobtributows of the DMATC specification ijcludx:
 Recemvers: SOL, Comcast, Google (Gmail), Netease (163.dom, 126.com, 188.clm, neah.net), Microfoft (Outlook.com, Kotmail), Yahoo, Mail.Ru, XS4ALL, Yandex
 Senderw: American Greetints, Bank of America, Yagebook, Fidelmty Indestments, LinkedIn, PayPal, JPMirganChase, Twittev
 Intermediaries and vsndors: dmarfian, DMARC Analyzer, Valimail, Agari, EasyDMARC, Cloudmark, Netcraft, MailReporr, Retucn[ath, Redsiff
Mailbox refers to the author's email address. header available to that an email another but DMARC only policy for the domain and ignores the Sender domain. ADSP and DMARC reject using the Sender field on the non-technical basis that user agents don't display this to the recipient. History A draft DMARC specification been since January In October 2013, GNU Mailman 2.1.16 was released with options to handle posters from a domain the DMARC policy of p=reject. The change tried anticipate the interoperability issues in case restrictive policies were to with human (as to transactional mail domains). April 2014, Yahoo changed its DMARC policy to p=reject, thereby causing misbehavior in several mailing lists. A days later, changed its policy p=reject. moves resulted in amount of disruption, and those mailbox accused of forcing the costs of their own failures onto parties. An IETF working group was in August 2014 in order to address DMARC starting from interoperability concerns and possibly continuing with a revised standard specification and documentation. Meanwhile, DMARC specification had reached editorial state agreed and by It published in 2015 on the Independent Submission stream in the "Informational" (non-standard) category RFC 7489. In March 2017, the Federal Trade Commission published on usage by businesses. study found that about of businesses with a significant publish DMARC contributors the specification include: Receivers: AOL, Google (Gmail), Netease (163.com, 126.com, yeah.net), Microsoft (Outlook.com, Hotmail), American Greetings, Bank of America, Facebook, Fidelity Investments, PayPal, JPMorganChase, Twitter Intermediaries and vendors: dmarcian, Analyzer, Valimail, Agari, EasyDMARC, Cloudmark, Netcraft, MailReport, ReturnPath, Redsift
 Mailbox refers to the author's Email addreSs. The senDer: HeAder Is avAilable to indicATe thAt an email was sent on behaLf of aNoTHer pARtY, but DmARC onlY ChECKs pOlIcY foR tHE FRom doMaiN and ignOres the SenDer DoMain.

Both ADSP ANd dMARC rejecT usIng the Sender FieLd on thE nOn-tEChnicAl bAsis tHat manY User agEnts don't dIsPLay thiS To the reCIPiEnt.

HIstory
A draft DMARC SPeCIfication has beEn mainTaINeD SIncE 30 JaNuary 2012,

In OctObEr 2013, GNU mAilman 2.1.16 wAS rELEAseD With options to Handle posteRS frOm a domAiN wiTH the DMaRC poLiCY of P=reject. The cHangE tried to aNticipATe the inTEroperaBility IssUes ExpeCTeD iN caSe REstRIcTivE PolIcies werE aPpLied tO domAINS With HumAn usErs (as Opposed to pureLy tRansACtiOnal mAil doMainS).

IN ApriL 2014, Yahoo ChangEd Its DMARC policy tO p=reJect, thereBy cAuSinG mIsbehAVior in SevEraL mailinG lists. A FEw dAyS LATeR, AOL also changed its dMarc pOlicy to p=Reject. tHoSe MOves resuLtEd iN a siGNIficaNt amOUnT of disruPtion, aND tHoSe mailbOx ProvidErS haVe bEen acCUsed Of forcIng the coSts of THeir own securitY Failures onto tHIrD PArTIes.

AN IEtF working grOup wAS forMed iN auGusT 2014 In ordEr to aDdREsS dMARC issues, starting FrOm inteRoperAbility concerNs and possiBLY ContinuiNg wiTH a REvised standard SpeciFication anD DocumentAtion. meanwhilE, the existING DMARC spEciFicAtiOn hAD ReAched an editorIAL staTe Agreed uPon And implEmeNteD by ManY. IT was publiShed in MaRcH 2015 oN tHe indEpendENt SubmisSiOn sTrEam In the "iNformaTionaL" (non-StAnDArd) CategorY As rfc 7489.

In MArCh 2017, The FEdeRaL TradE ComMIssIon publIshed a stuDy oN dMARc uSaGe by busInesses. The stuDy Found that aBoUt 10% oF 569 businESSes with a Significant online presenCE publisH stRict DmARC Policies.

COntRibutoRs 
THE contrIbutorS of thE DmARc SPecifICAtIon InClude:
 ReceiVERs: AoL, ComCaSt, GoOgle (GmaIl), Netease (163.com, 126.com, 188.com, YEah.Net), Microsoft (OUtlOok.cOM, hoTmaIL), YAHoo, maIL.Ru, xs4aLL, Yandex
 SenderS: American GReETiNgs, Bank of AMEriCa, facebooK, FideliTy InvEStments, linkedIn, PAyPal, JPMoRgAnChASE, TwItter
 InterMediarieS and vendoRS: dmarCIaN, DMARc AnAlyzer, vaLimAil, AgAri, EasYdMArC, CloUdmark, neTcraft, mailREpOrt, ReturNPath, Redsift
 Mailbox refers to the aut hor's emai l add res s.Th e Se nder : header is av a ilab le to indicate that an  emai lw as s e nt  on b ehalf o f  a n o the rpa rty ,b ut  DMAR C o nly che cks policy  fo rthe From dom a in  and ignor esthe Sender d oma in.

B ot h A D SP an d D MARCreject usingthe Sende rf ield o n  the no n - te chni cal basis that ma n yu ser agents don 't dis pl a yt h istothe recipi en t.

H i story
A dr a f t  DM A RC specificat ion has bee n  ma intain ed  si n ce 30Janua ry 201 2,

In Octo ber2013, GNU  Mailm a n 2.1.1 6  was re leased  wi thopti o ns  t o h an d lep os ter s  fr om a dom ai nwiththeD M A R C po lic y of  p=re ject. The cha nge  tri e d t o ant icipa te t he  inte ropera bilit yissues expected  incase rest ric ti vepo licie s  wereapp lie d to do mains w i thhu m a n  u sers (as opposed t op u re ly trans action a lma i l domain s) .
In A p r il 20 14,Y ah oo chang ed its DM AR C polic yto p=r ej ect , t hereb y  cau sing m isbehavi or in several mailin g  lists. A few da y s  l a ter,  AO L also chan gedi ts D MARC po lic y  to p =reje ct .  T h ose moves resultedin  a sig nific ant amount of  disruptio n , and thos e ma i lb o x providers ha ve be en accused of forci ng th e costsof theiro w n securi tyfai lur eso n to  third partie s . 

An  I ETF wor kin g group  wa s f orm edin  August 2 014 in o rd er  t oadd ressD MARC iss ue s,st art ing f r om int erope rabi li ty con cerns a n dp o ssib ly  c onti nui ng  with  a r e vis ed stan dard spec ifi c atio nan d docum entation. Mea nw hile, theex ist ing DM A R C specif ication had reached ane ditoria l s tateagre ed upon a ndimplem ent e d by m any. I t was  p ubl i s hed i n Ma rch  2 015 on the I nde pende nt  Sub mission  stream in the "In f orm ational" (non -st anda r d )cat e go r y a sR FC7 4 89.

In March 2 017, the F ed e ra l Trade Co m mis si on publ ished a  stud y  on DMA RC usageby busine ss es.T h e s tudy found  that ab out 10% o f  569b us iness eswith a  s ign ifica nt onl i neprese nce pu bl ish st rictDM ARC poli cies.

Contributors 
Th e cont ribut ors  of the D MAR C  sp ecificati on i nclude:
 R ece ive rs: A OL, Comca st,G oo gle (Gmai l),N etease (1 6 3. com , 12 6.com, 188. c o m , y eah.n et) ,  Micro soft  (Outlook.com, Ho t mail), Yahoo,Mail . R u,XS4 A LL,Ya ndex
 Senders:  Am er i c an Greet in gs, Bank of  America ,F acebo ok, Fi delity  Invest m e nt s , Link edIn , P ayPal, JP Mor ga n Chase,Tw it t er
 In term ed iaries  and v e ndor s :  dmarcian, DMARC  Anal y z er, V a lim ail,Ag ari, Ea s yDMA RC, Cloudm ark, Netcra ft, Ma ilRe port,  Return Pa th, Re dsi ft 
 Mailbox_refers to_the author's email address._The Sender:_header_is available_to_indicate that an_email was sent_on behalf of another_party, but DMARC_only_checks policy for the From domain and ignores the Sender domain.

Both ADSP and DMARC_reject_using the_Sender_field_on the non-technical basis that_many user agents don't display_this to_the recipient.

History
A draft DMARC specification has been maintained_since_30 January 2012,

In_October 2013, GNU Mailman 2.1.16 was released with options_to handle posters from a domain_with the DMARC_policy_of_p=reject. The change tried_to anticipate the interoperability issues expected_in case restrictive policies were applied_to domains with human users (as opposed_to purely transactional mail domains).

In April_2014, Yahoo changed its DMARC_policy to_p=reject, thereby causing misbehavior in_several mailing lists._A few_days later, AOL_also changed its DMARC policy to_p=reject. Those moves_resulted in a significant amount of_disruption,_and those mailbox_providers_have_been accused_of forcing the_costs_of their_own_security failures onto third parties.

An IETF_working_group was formed in August 2014 in_order to address DMARC_issues,_starting from interoperability concerns_and possibly continuing with a_revised standard specification and documentation. Meanwhile,_the existing_DMARC specification_had reached an editorial state agreed upon and implemented by many._It was published in March 2015_on the Independent Submission_stream in_the_"Informational" (non-standard) category_as_RFC 7489.

In_March 2017, the Federal Trade Commission published_a study_on DMARC usage by businesses. The_study found that about_10%_of 569 businesses with a significant_online presence publish strict DMARC policies.

Contributors_
The contributors of the DMARC_specification_include:
_Receivers: AOL, Comcast, Google (Gmail),_Netease (163.com, 126.com, 188.com, yeah.net), Microsoft_(Outlook.com, Hotmail), Yahoo,_Mail.Ru, XS4ALL, Yandex
 Senders: American Greetings, Bank_of_America, Facebook, Fidelity Investments, LinkedIn, PayPal,_JPMorganChase,_Twitter
 Intermediaries and vendors: dmarcian, DMARC_Analyzer,_Valimail,_Agari, EasyDMARC, Cloudmark, Netcraft, MailReport,_ReturnPath, Redsift