{"id":2824,"date":"2026-10-09T15:00:00","date_gmt":"2026-10-09T12:00:00","guid":{"rendered":"https:\/\/narhost.com\/blog\/?p=2824"},"modified":"2026-09-26T23:21:35","modified_gmt":"2026-09-26T20:21:35","slug":"dmarc-politikasi","status":"publish","type":"post","link":"https:\/\/narhost.com\/blog\/dmarc-politikasi\/","title":{"rendered":"DMARC Politikas\u0131 p=none mu quarantine mi reject mi"},"content":{"rendered":"<div id=\"ai-ozet\" class=\"ai-box\">\n<p class=\"ai-box-title\">K\u0131saca \u00f6zet<\/p>\n<ul>\n<li>DMARC politikas\u0131, SPF ve DKIM denetiminden ge\u00e7emeyen ve alan ad\u0131n\u0131z\u0131 g\u00f6nderen olarak g\u00f6steren e-postalara al\u0131c\u0131 sunucunun ne yapmas\u0131n\u0131 istedi\u011finizi s\u00f6yleyen DNS kayd\u0131d\u0131r.<\/li>\n<li>p=none yaln\u0131z izler ve rapor toplar, p=quarantine ba\u015far\u0131s\u0131z iletiyi spam klas\u00f6r\u00fcne y\u00f6nlendirir, p=reject iletiyi hi\u00e7 kabul ettirmez.<\/li>\n<li>Do\u011frudan p=reject ile ba\u015flamak, kendi faturalama sisteminiz ya da b\u00fclten arac\u0131n\u0131z gibi me\u015fru g\u00f6nderenlerin e-postalar\u0131n\u0131 da kaybettirebilir.<\/li>\n<li>Do\u011fru s\u0131ra, p=none ile rua raporlar\u0131n\u0131 birka\u00e7 hafta okumak, t\u00fcm me\u015fru kaynaklar\u0131 hizalamak, sonra quarantine ve reject&#8217;e ge\u00e7mektir.<\/li>\n<li>Google, g\u00fcnde 5.000&#8217;den fazla ileti g\u00f6nderenlerden DMARC kayd\u0131 istiyor; bu g\u00f6nderenler i\u00e7in en az p=none yeterli say\u0131l\u0131yor.<\/li>\n<li>DMARC&#8217;\u0131n g\u00fcncel standard\u0131 May\u0131s 2026&#8217;da yay\u0131mlanan RFC 9989&#8217;dur; RFC 7489&#8217;u ge\u00e7ersiz k\u0131ld\u0131 ve pct etiketini tarihsel kabul etti.<\/li>\n<\/ul>\n<\/div>\n<p>SPF ve DKIM kay\u0131tlar\u0131n\u0131 kurdunuz, ama e-posta kontrol ara\u00e7lar\u0131 h\u00e2l\u00e2 &#8220;DMARC politikas\u0131 zay\u0131f&#8221; uyar\u0131s\u0131 veriyor. Kayd\u0131 eklemek iki dakika s\u00fcr\u00fcyor; as\u0131l soru p de\u011ferinin ne olaca\u011f\u0131. p=reject en g\u00fcvenlisi gibi g\u00f6r\u00fcn\u00fcyor, fakat yanl\u0131\u015f zamanda a\u00e7\u0131ld\u0131\u011f\u0131nda m\u00fc\u015fterilere giden faturalar, ileti\u015fim formundan gelen bildirimler ve b\u00fclten g\u00f6nderimleri sessizce kaybolabiliyor. \u00dc\u00e7 politika aras\u0131ndaki fark teknik olarak basit; zor olan ge\u00e7i\u015fi kimseyi kesintiye u\u011fratmadan yapmak.<\/p>\n<h2>DMARC Politikas\u0131 Ne \u0130\u015fe Yarar<\/h2>\n<p>SPF, iletiyi g\u00f6nderen sunucunun alan ad\u0131n\u0131z ad\u0131na g\u00f6ndermeye yetkili olup olmad\u0131\u011f\u0131n\u0131 denetler. DKIM, iletinin yolda de\u011fi\u015fmedi\u011fini ve imzalayan alan ad\u0131n\u0131 do\u011frular. \u0130kisinin de ortak eksi\u011fi, okuyucunun g\u00f6rd\u00fc\u011f\u00fc &#8220;Kimden&#8221; adresine do\u011frudan ba\u011fl\u0131 olmamalar\u0131d\u0131r. Doland\u0131r\u0131c\u0131, kendi alan ad\u0131yla SPF&#8217;den ge\u00e7ip &#8220;Kimden&#8221; alan\u0131na sizin adresinizi yazabilir.<\/p>\n<p>DMARC bu bo\u015flu\u011fu hizalama (alignment) kural\u0131yla kapat\u0131r. \u0130letinin DMARC&#8217;tan ge\u00e7mesi i\u00e7in SPF veya DKIM&#8217;in ba\u015far\u0131l\u0131 olmas\u0131 yetmez; ba\u015far\u0131l\u0131 olan denetimin alan ad\u0131, &#8220;Kimden&#8221; adresindeki alan ad\u0131yla e\u015fle\u015fmelidir. DMARC politikas\u0131 da bu denetim ba\u015far\u0131s\u0131z oldu\u011funda al\u0131c\u0131dan ne istedi\u011finizi s\u00f6yler. Standart, <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9989\" title=\"RFC 9989 \u2014 Domain-based Message Authentication, Reporting, and Conformance (DMARC)\" target=\"_blank\" rel=\"noopener\">RFC 9989<\/a> numaras\u0131yla May\u0131s 2026&#8217;da yay\u0131mland\u0131 ve 2015 tarihli RFC 7489&#8217;un yerini ald\u0131.<\/p>\n<div class=\"highlight-box\">\n<p class=\"label\">Bilgi<\/p>\n<p>DMARC kayd\u0131 alan ad\u0131n\u0131z\u0131n DNS b\u00f6lgesine, <code>_dmarc<\/code> adl\u0131 bir TXT kayd\u0131 olarak eklenir. En sade h\u00e2li <code>v=DMARC1; p=none; rua=mailto:dmarc@alanadiniz.com<\/code> \u015feklindedir. cPanel Zone Editor&#8217;da kayd\u0131n ad\u0131m ad\u0131m nas\u0131l eklenece\u011fi <a href=\"https:\/\/narhost.com\/destek\/dmarc-kaydi-nasil-olusturulur\/\" title=\"DMARC Kayd\u0131 Nas\u0131l Olu\u015fturulur \u2014 Narhost Destek Merkezi\">DMARC kayd\u0131 olu\u015fturma rehberinde<\/a> anlat\u0131l\u0131yor.<\/p>\n<\/div>\n<h2>p=none, quarantine ve reject Fark\u0131<\/h2>\n<p>\u00dc\u00e7 de\u011fer, al\u0131c\u0131 sunucuya verdi\u011finiz \u00fc\u00e7 farkl\u0131 talimatt\u0131r. Hi\u00e7biri al\u0131c\u0131y\u0131 zorlamaz; al\u0131c\u0131 kendi politikas\u0131yla birlikte de\u011ferlendirir. Yine de b\u00fcy\u00fck e-posta sa\u011flay\u0131c\u0131lar\u0131 bu talimata b\u00fcy\u00fck \u00f6l\u00e7\u00fcde uyar.<\/p>\n<table>\n<thead>\n<tr>\n<th>Politika<\/th>\n<th>Ba\u015far\u0131s\u0131z iletiye ne olur<\/th>\n<th>Ne zaman kullan\u0131l\u0131r<\/th>\n<th>Risk<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>p=none<\/td>\n<td>Ola\u011fan \u015fekilde teslim edilir, yaln\u0131z raporlan\u0131r<\/td>\n<td>Ba\u015flang\u0131\u00e7ta, g\u00f6nderen kaynaklar\u0131 ke\u015ffederken<\/td>\n<td>Sahte iletiye kar\u015f\u0131 koruma sa\u011flamaz<\/td>\n<\/tr>\n<tr>\n<td>p=quarantine<\/td>\n<td>Spam veya karantina klas\u00f6r\u00fcne gider<\/td>\n<td>Me\u015fru kaynaklar hizaland\u0131ktan sonra ara ad\u0131m<\/td>\n<td>Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f me\u015fru ileti spama d\u00fc\u015fer<\/td>\n<\/tr>\n<tr>\n<td>p=reject<\/td>\n<td>Al\u0131c\u0131 sunucu iletiyi kabul etmez<\/td>\n<td>Raporlar temiz, t\u00fcm kaynaklar hizal\u0131 oldu\u011funda<\/td>\n<td>Hata varsa me\u015fru ileti tamamen kaybolur<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bunlara ek olarak <code>sp<\/code> etiketi alt alan adlar\u0131 i\u00e7in ayr\u0131 politika tan\u0131mlar. RFC 9989 ile gelen <code>np<\/code> etiketi ise var olmayan alt alan adlar\u0131 i\u00e7in politika belirler; &#8220;fatura.alanadiniz.com&#8221; gibi hi\u00e7 kullanmad\u0131\u011f\u0131n\u0131z bir alt alan ad\u0131n\u0131n taklit edilmesini kapatmak i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n<h2>Raporlama, rua Adresi Neden \u015eart<\/h2>\n<p>DMARC politikas\u0131n\u0131 g\u00fcvenle s\u0131k\u0131la\u015ft\u0131rman\u0131n tek yolu, alan ad\u0131n\u0131z ad\u0131na kimlerin e-posta g\u00f6nderdi\u011fini g\u00f6rmektir. <code>rua<\/code> etiketine yazd\u0131\u011f\u0131n\u0131z adrese, e-posta alan b\u00fcy\u00fck sa\u011flay\u0131c\u0131lar toplu raporlar g\u00f6nderir. Bu raporlar XML bi\u00e7imindedir ve hangi IP adresinden ka\u00e7 ileti geldi\u011fini, SPF ve DKIM sonucunu, hizalaman\u0131n tutup tutmad\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/p>\n<p>Raporlar\u0131 ham XML olarak okumak zordur; bir DMARC rapor analiz arac\u0131 ya da ayr\u0131 bir posta kutusu ve d\u00fczenli bir inceleme al\u0131\u015fkanl\u0131\u011f\u0131 gerekir. \u0130lk haftalarda genelde s\u00fcrprizler \u00e7\u0131kar; unutulmu\u015f bir ileti\u015fim formu eklentisi, muhasebe yaz\u0131l\u0131m\u0131n\u0131n kendi sunucusundan g\u00f6nderdi\u011fi faturalar ya da e-b\u00fclten hizmeti. Bunlar\u0131n her biri SPF&#8217;ye eklenmeli ya da kendi alan ad\u0131n\u0131zla DKIM imzalamal\u0131d\u0131r. <code>ruf<\/code> etiketiyle istenen ileti bazl\u0131 hata raporlar\u0131n\u0131 ise bir\u00e7ok b\u00fcy\u00fck sa\u011flay\u0131c\u0131 gizlilik nedeniyle g\u00f6ndermez; as\u0131l bilgi kayna\u011f\u0131 toplu raporlard\u0131r.<\/p>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>rua adresi ba\u015fka bir alan ad\u0131ndaysa, o alan ad\u0131n\u0131n DNS&#8217;inde raporlar\u0131 kabul etti\u011fini g\u00f6steren ek bir yetki kayd\u0131 gerekir. Bu kay\u0131t yoksa al\u0131c\u0131lar raporu g\u00f6ndermez ve siz &#8220;rapor gelmiyor&#8221; diye beklersiniz. En kolay yol, rapor adresini ayn\u0131 alan ad\u0131nda a\u00e7makt\u0131r.<\/p>\n<\/div>\n<h2>SPF ve DKIM Hizalamas\u0131 Nas\u0131l Kurulur<\/h2>\n<p>Hizalaman\u0131n iki modu vard\u0131r. Varsay\u0131lan gev\u015fek (relaxed) modda alt alan ad\u0131 ile ana alan ad\u0131 e\u015fle\u015fmi\u015f say\u0131l\u0131r; &#8220;bulten.alanadiniz.com&#8221; ile imzalanan ileti &#8220;alanadiniz.com&#8221; adresinden g\u00f6nderildi\u011finde hizalama tutar. Kat\u0131 (strict) modda ise alan adlar\u0131 birebir ayn\u0131 olmal\u0131d\u0131r. <code>adkim<\/code> ve <code>aspf<\/code> etiketleri bu modu se\u00e7er. \u00c7o\u011fu i\u015fletme i\u00e7in gev\u015fek mod yeterlidir.<\/p>\n<p>Pratikte hizalaman\u0131n k\u0131r\u0131ld\u0131\u011f\u0131 yer \u00fc\u00e7\u00fcnc\u00fc taraf g\u00f6nderim hizmetleridir. Bir b\u00fclten arac\u0131 iletiyi kendi alan ad\u0131yla imzalay\u0131p kendi d\u00f6n\u00fc\u015f adresini kullan\u0131yorsa, SPF ve DKIM ba\u015far\u0131l\u0131 g\u00f6r\u00fcn\u00fcr ama hizalama tutmaz. \u00c7\u00f6z\u00fcm, o hizmette kendi alan ad\u0131n\u0131z i\u00e7in DKIM anahtar\u0131 olu\u015fturup DNS&#8217;e eklemektir. DKIM kayd\u0131n\u0131n cPanel&#8217;de nas\u0131l eklendi\u011fi <a href=\"https:\/\/narhost.com\/destek\/dkim-kaydi-nasil-eklenir\/\" title=\"DKIM Kayd\u0131 Nas\u0131l Eklenir \u2014 Narhost Destek Merkezi\">DKIM kayd\u0131 rehberinde<\/a> anlat\u0131l\u0131yor. Spama d\u00fc\u015fmenin di\u011fer nedenlerini de <a href=\"https:\/\/narhost.com\/blog\/e-postalar-neden-spama-duser\/\" title=\"E-postalar Neden Spama D\u00fc\u015fer \u2014 Narhost Blog\">e-postalar neden spama d\u00fc\u015fer yaz\u0131s\u0131nda<\/a> toplad\u0131k.<\/p>\n<figure class=\"nh-sema\"><img loading=\"lazy\" src=\"https:\/\/narhost.com\/blog\/wp-content\/uploads\/2026\/09\/dmarc-politikasi-sema-narhost.webp\" alt=\"dmarc politikas\u0131 i\u00e7in p=none ile raporlama, kaynaklar\u0131 hizalama, quarantine ve reject a\u015famalar\u0131n\u0131 g\u00f6steren \u015fema\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>G\u00fcvenli ge\u00e7i\u015f her a\u015famada rua raporlar\u0131n\u0131n temiz oldu\u011funu g\u00f6rmeye dayan\u0131r.<\/figcaption><\/figure>\n<h2>A\u015famal\u0131 Ge\u00e7i\u015f Plan\u0131, none&#8217;dan reject&#8217;e<\/h2>\n<p>G\u00fcvenli ge\u00e7i\u015f, her ad\u0131mda raporlar\u0131n temiz oldu\u011funu g\u00f6rmeye dayan\u0131r. Takvim alan ad\u0131n\u0131n b\u00fcy\u00fckl\u00fc\u011f\u00fcne g\u00f6re de\u011fi\u015fir; tek sunucudan g\u00f6nderen k\u00fc\u00e7\u00fck bir i\u015fletme birka\u00e7 haftada, \u00e7ok say\u0131da g\u00f6nderim hizmeti kullanan bir \u015firket birka\u00e7 ayda reject&#8217;e ula\u015f\u0131r.<\/p>\n<p>Birinci a\u015famada p=none ve rua adresiyle ba\u015flay\u0131n, en az iki \u00fc\u00e7 haftal\u0131k rapor toplay\u0131n. \u0130kinci a\u015famada raporlarda \u00e7\u0131kan her me\u015fru kayna\u011f\u0131 SPF ve DKIM ile hizalay\u0131n. \u00dc\u00e7\u00fcnc\u00fc a\u015famada p=quarantine&#8217;e ge\u00e7in ve bir iki hafta daha izleyin. Son a\u015famada p=reject&#8217;e ge\u00e7in. Eski standartta bu ge\u00e7i\u015fi yumu\u015fatan <code>pct<\/code> etiketi RFC 9989&#8217;da tarihsel kabul edildi, \u00e7\u00fcnk\u00fc uygulamalar tutars\u0131z davran\u0131yordu. Yerine gelen <code>t=y<\/code> test modu etiketi, politikay\u0131 yay\u0131mlay\u0131p al\u0131c\u0131dan hen\u00fcz uygulamamas\u0131n\u0131 istemenin yoludur; ancak her al\u0131c\u0131n\u0131n yeni etiketi destekledi\u011fini varsaymay\u0131n.<\/p>\n<div class=\"senaryo-block\">\n<p class=\"label\">\u00d6rnek senaryo<\/p>\n<p>Bursa&#8217;da yirmi \u00e7al\u0131\u015fanl\u0131 bir yedek par\u00e7a toptanc\u0131s\u0131, sahte &#8220;\u00f6deme bilgisi de\u011fi\u015fti&#8221; e-postalar\u0131 m\u00fc\u015fterilerine ula\u015f\u0131nca DMARC politikas\u0131 kurmaya karar veriyor. p=none ile ba\u015fl\u0131yor; ilk hafta raporlarda \u00fc\u00e7 kaynak g\u00f6r\u00fcyor: kendi e-posta sunucusu, muhasebe yaz\u0131l\u0131m\u0131n\u0131n fatura sunucusu ve web sitesindeki ileti\u015fim formu. Fatura sunucusunu SPF&#8217;ye ekliyor, ileti\u015fim formunu kimli\u011fi do\u011frulanm\u0131\u015f SMTP ile g\u00f6nderecek \u015fekilde d\u00fczenliyor. D\u00f6rd\u00fcnc\u00fc haftada quarantine&#8217;e, yedinci haftada reject&#8217;e ge\u00e7iyor. Sahte iletiler art\u0131k m\u00fc\u015fterilerin gelen kutusuna ula\u015fm\u0131yor.<\/p>\n<\/div>\n<h2>Google ve Yahoo G\u00f6nderici Kurallar\u0131 Ne \u0130stiyor<\/h2>\n<p>Google, 1 \u015eubat 2024&#8217;ten itibaren Gmail hesaplar\u0131na g\u00fcnde 5.000&#8217;den fazla ileti g\u00f6nderenlerden SPF, DKIM ve DMARC&#8217;\u0131n \u00fc\u00e7\u00fcn\u00fc birden istiyor. <a href=\"https:\/\/support.google.com\/mail\/answer\/81126\" title=\"Google \u2014 E-posta g\u00f6nderen y\u00f6nergeleri\" target=\"_blank\" rel=\"noopener\">Google&#8217;\u0131n g\u00f6nderen y\u00f6nergelerine<\/a> g\u00f6re bu g\u00f6nderenler i\u00e7in DMARC politikas\u0131 none olabilir; ayr\u0131ca &#8220;Kimden&#8221; alan\u0131ndaki alan ad\u0131n\u0131n SPF ya da DKIM alan ad\u0131yla hizal\u0131 olmas\u0131 gerekiyor. T\u00fcm g\u00f6nderenler i\u00e7in ise en az SPF veya DKIM \u015fart. Yahoo da ayn\u0131 d\u00f6nemde benzer kurallar duyurdu.<\/p>\n<p>Yani b\u00fcy\u00fck sa\u011flay\u0131c\u0131lar herkesi reject&#8217;e zorlam\u0131yor; zorunlu olan kayd\u0131n var olmas\u0131 ve hizalaman\u0131n tutmas\u0131. Reject, taklit edilme riskini ortadan kald\u0131rmak isteyen alan ad\u0131 sahibinin kendi karar\u0131d\u0131r. Kurumsal alan adlar\u0131nda, \u00f6zellikle \u00f6deme ve fatura yaz\u0131\u015fmas\u0131 yap\u0131lan i\u015fletmelerde, bu karar genelde reject y\u00f6n\u00fcnde verilir. \u015eirket e-postas\u0131n\u0131 s\u0131f\u0131rdan kuruyorsan\u0131z alan ad\u0131, hesaplar ve DNS kay\u0131tlar\u0131n\u0131n b\u00fct\u00fcn resmini <a href=\"https:\/\/narhost.com\/blog\/sirket-e-posta-olusturma\/\" title=\"\u015eirket E-postas\u0131 Olu\u015fturma \u2014 Narhost Blog\">\u015firket e-postas\u0131 olu\u015fturma rehberinde<\/a> bulabilirsiniz.<\/p>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p>DMARC politikas\u0131 se\u00e7imi bir g\u00fcvenlik ayar\u0131ndan \u00e7ok bir ge\u00e7i\u015f s\u00fcrecidir. p=none ile g\u00f6r\u00fcn\u00fcrl\u00fck kazan\u0131n, raporlarda \u00e7\u0131kan her me\u015fru g\u00f6ndereni hizalay\u0131n, quarantine ile ara testi yap\u0131n ve raporlar temiz kald\u0131\u011f\u0131nda reject&#8217;e ge\u00e7in. Bu s\u0131rayla ilerleyen alan ad\u0131nda hem sahte e-posta durur hem de hi\u00e7bir me\u015fru ileti kaybolmaz.<\/p>\n<\/div>\n<h2>Kontrol Listesi, DMARC Politikas\u0131 S\u0131k\u0131la\u015ft\u0131rmadan \u00d6nce<\/h2>\n<ul class=\"kontrol-listesi\">\n<li>SPF kayd\u0131n\u0131z\u0131n tek oldu\u011funu ve t\u00fcm g\u00f6nderen sunucular\u0131 kapsad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>Kendi e-posta sunucunuzda DKIM imzalaman\u0131n a\u00e7\u0131k oldu\u011funu kontrol edin.<\/li>\n<li>DMARC kayd\u0131n\u0131 p=none ve ayn\u0131 alan ad\u0131ndaki bir rua adresiyle yay\u0131mlay\u0131n.<\/li>\n<li>En az iki \u00fc\u00e7 haftal\u0131k toplu raporu kaynak kaynak inceleyin.<\/li>\n<li>B\u00fclten, fatura ve form gibi \u00fc\u00e7\u00fcnc\u00fc taraf g\u00f6nderenleri kendi alan ad\u0131n\u0131zla DKIM ile imzalat\u0131n.<\/li>\n<li>Hi\u00e7 e-posta g\u00f6ndermeyen alt alan adlar\u0131 i\u00e7in sp veya np politikas\u0131n\u0131 belirleyin.<\/li>\n<li>quarantine&#8217;de raporlar temiz kald\u0131ktan sonra reject&#8217;e ge\u00e7in ve raporlar\u0131 izlemeye devam edin.<\/li>\n<\/ul>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>DMARC politikas\u0131 p=none olarak kal\u0131rsa sak\u0131ncas\u0131 var m\u0131?<\/h3>\n<p>p=none raporlama sa\u011flar ve Google&#8217;\u0131n toplu g\u00f6nderici \u015fart\u0131n\u0131 kar\u015f\u0131lar, ama sahte iletiye kar\u015f\u0131 koruma sa\u011flamaz. Alan ad\u0131n\u0131z\u0131 taklit eden bir e-posta yine teslim edilir. Uzun s\u00fcre none&#8217;da kalmak, raporlar\u0131 okumuyorsan\u0131z DMARC&#8217;\u0131n as\u0131l faydas\u0131ndan vazge\u00e7mek demektir. Hedef, raporlar temizlendikten sonra quarantine ya da reject&#8217;tir.<\/p>\n<h3>p=reject e-postalar\u0131m\u0131n hi\u00e7 teslim edilmemesine yol a\u00e7ar m\u0131?<\/h3>\n<p>Do\u011fru hizalanm\u0131\u015f iletileriniz etkilenmez. Reject yaln\u0131z DMARC&#8217;tan ge\u00e7emeyen iletileri durdurur. Sorun, hizalanmam\u0131\u015f me\u015fru bir kayna\u011f\u0131n\u0131z varsa \u00e7\u0131kar; \u00f6rne\u011fin kendi alan ad\u0131n\u0131zla imzalamayan bir b\u00fclten arac\u0131. Bu y\u00fczden reject&#8217;e ge\u00e7meden \u00f6nce raporlarda t\u00fcm kaynaklar\u0131n DMARC&#8217;tan ge\u00e7ti\u011fini g\u00f6rmek gerekir.<\/p>\n<h3>Y\u00f6nlendirilen e-postalar DMARC&#8217;ta neden ba\u015far\u0131s\u0131z olur?<\/h3>\n<p>Y\u00f6nlendirme s\u0131ras\u0131nda ileti ba\u015fka bir sunucudan yeniden g\u00f6nderilir ve SPF denetimi bu sunucuya g\u00f6re yap\u0131l\u0131r, bu y\u00fczden SPF k\u0131r\u0131l\u0131r. DKIM imzas\u0131 ileti de\u011fi\u015fmedi\u011fi s\u00fcrece korunur ve DMARC&#8217;\u0131 tek ba\u015f\u0131na ge\u00e7irir. Konu sat\u0131r\u0131na etiket ekleyen e-posta listeleri ise DKIM&#8217;i de bozabilir; bu durum reject politikas\u0131nda liste iletilerinin kaybolmas\u0131na yol a\u00e7abilir.<\/p>\n<h3>pct etiketini h\u00e2l\u00e2 kullanmal\u0131 m\u0131y\u0131m?<\/h3>\n<p>RFC 9989 pct etiketini tarihsel kabul etti; yeni kay\u0131tlarda a\u015famal\u0131 ge\u00e7i\u015fi pct ile planlamay\u0131n. Eski standarda g\u00f6re \u00e7al\u0131\u015fan al\u0131c\u0131lar etiketi bir s\u00fcre daha okuyabilir, ancak davran\u0131\u015f\u0131 tutarl\u0131 de\u011fildi. Yeni standartta test ama\u00e7l\u0131 t=y etiketi var. En g\u00fcvenli y\u00f6ntem yine none, quarantine ve reject ad\u0131mlar\u0131n\u0131 raporlara bakarak s\u0131rayla uygulamakt\u0131r.<\/p>\n<h3>DMARC raporlar\u0131 hangi s\u0131kl\u0131kla gelir?<\/h3>\n<p>Toplu raporlar genelde g\u00fcnde bir kez, alan ad\u0131n\u0131za e-posta ula\u015ft\u0131ran her b\u00fcy\u00fck sa\u011flay\u0131c\u0131dan ayr\u0131 ayr\u0131 gelir. G\u00f6nderim hacmi d\u00fc\u015f\u00fck bir alan ad\u0131nda baz\u0131 g\u00fcnler hi\u00e7 rapor gelmeyebilir. Raporlar XML bi\u00e7iminde ve s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f olarak gelir; bu y\u00fczden ayr\u0131 bir posta kutusu a\u00e7mak ve bir analiz arac\u0131yla okumak i\u015fi kolayla\u015ft\u0131r\u0131r.<\/p>\n<\/div>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost&#8217;ta<\/p>\n<p>Kurumsal e-posta paketlerimizde alan ad\u0131n\u0131za \u00f6zel adresler, SPF ve DNS kay\u0131t deste\u011fi, e-posta g\u00f6nderi takibi ve yetkilendirilebilir y\u00f6netim paneli bulunur.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/kurumsal-e-posta\" title=\"Narhost Kurumsal E-posta paketleri\">Kurumsal e-posta paketlerini incele<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>DMARC politikas\u0131, SPF ve DKIM denetiminden ge\u00e7emeyen e-postalara al\u0131c\u0131 sunucunun ne yapaca\u011f\u0131n\u0131 s\u00f6yler. p=none izler, quarantine spama g\u00f6nderir, reject reddeder; g\u00fcvenli ge\u00e7i\u015f raporlara bakarak a\u015famal\u0131 yap\u0131l\u0131r.<\/p>\n","protected":false},"author":1,"featured_media":2825,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[],"class_list":["post-2824","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-e-posta"],"_links":{"self":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/comments?post=2824"}],"version-history":[{"count":1,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2824\/revisions"}],"predecessor-version":[{"id":2826,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2824\/revisions\/2826"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media\/2825"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media?parent=2824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/categories?post=2824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/tags?post=2824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}