{"id":145,"date":"2026-10-13T09:01:11","date_gmt":"2026-10-13T06:01:11","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/dmarc-fail-sorun-giderme-spf-dkim-alignment-dns\/"},"modified":"2026-10-13T09:01:11","modified_gmt":"2026-10-13T06:01:11","slug":"dmarc-fail-sorun-giderme-spf-dkim-alignment-dns","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/dmarc-fail-sorun-giderme-spf-dkim-alignment-dns\/","title":{"rendered":"DMARC Fail (Ba\u015far\u0131s\u0131z) Oldu\u011funda Sorun Giderme: SPF\/DKIM, Alignment ve DNS Kaynakl\u0131 Hatalar\u0131 H\u0131zl\u0131 Te\u015fhis Etme"},"content":{"rendered":"<h2>DMARC fail ne demektir ve neden tek ba\u015f\u0131na \u201cSPF\/DKIM bozuk\u201d anlam\u0131na gelmez?<\/h2>\n<p>DMARC, al\u0131c\u0131 taraf\u0131n bir e-postay\u0131 de\u011ferlendirirken \u201cKimlik do\u011frulama (authentication) ge\u00e7ti mi?\u201d sorusunu daha net yan\u0131tlamas\u0131n\u0131 sa\u011flar. Ancak DMARC sonucunun fail olmas\u0131, mutlaka SPF ve DKIM\u2019in ikisinin de teknik olarak \u00e7al\u0131\u015fmad\u0131\u011f\u0131 anlam\u0131na gelmez. DMARC; SPF ve DKIM sonu\u00e7lar\u0131n\u0131, ayr\u0131ca bu sonu\u00e7lar\u0131n g\u00f6nderen alan ad\u0131yla uyumunu (alignment) birlikte de\u011ferlendirir. Bu y\u00fczden \u201cSPF=pass ama DMARC=fail\u201d gibi g\u00f6r\u00fcnen durumlar pratikte s\u0131k ya\u015fan\u0131r.<\/p>\n<p>Bu makalede bir DMARC fail vakas\u0131n\u0131 h\u0131zl\u0131 te\u015fhis etmek i\u00e7in pratik bir triage (\u00f6nceliklendirilmi\u015f inceleme) yakla\u015f\u0131m\u0131 bulacaks\u0131n\u0131z. Ama\u00e7; bir e-postan\u0131n neden DMARC\u2019tan kald\u0131\u011f\u0131n\u0131, sorunun SPF taraf\u0131nda m\u0131 DKIM taraf\u0131nda m\u0131 alignment taraf\u0131nda m\u0131 yoksa DNS ve y\u00f6nlendirme gibi \u00e7evresel fakt\u00f6rlerde mi oldu\u011funu sistematik bi\u00e7imde anlamakt\u0131r.<\/p>\n<h2>H\u0131zl\u0131 te\u015fhis i\u00e7in \u00f6nce do\u011fru veriyi toplay\u0131n<\/h2>\n<p>Sorun giderme, do\u011fru \u00f6rnekle ba\u015flar. M\u00fcmk\u00fcnse a\u015fa\u011f\u0131daki verileri ayn\u0131 olay i\u00e7in tek bir yerde toplay\u0131n:<\/p>\n<ul>\n<li><strong>Al\u0131c\u0131n\u0131n verdi\u011fi hata\/uyar\u0131<\/strong>: \u201c550 DMARC fail\u201d gibi bir SMTP yan\u0131t\u0131 veya spam klas\u00f6r\u00fcne d\u00fc\u015fme bilgisi.<\/li>\n<li><strong>Mesaj\u0131n tam header\u2019\u0131<\/strong>: Authentication-Results, Received, Return-Path, From gibi alanlar kritik.<\/li>\n<li><strong>G\u00f6nderim kayna\u011f\u0131<\/strong>: Kullan\u0131c\u0131 m\u0131 g\u00f6nderdi, bir uygulama m\u0131 (web sitesi, CRM, muhasebe yaz\u0131l\u0131m\u0131), bir cihaz m\u0131 (yaz\u0131c\u0131, kamera), yoksa \u00fc\u00e7\u00fcnc\u00fc taraf bir servis mi?<\/li>\n<li><strong>DNS kay\u0131tlar\u0131<\/strong>: Alan ad\u0131n\u0131n SPF, DKIM selector kay\u0131tlar\u0131 ve DMARC kayd\u0131.<\/li>\n<\/ul>\n<p>Bu veriler olmadan yap\u0131lan yorumlar \u00e7o\u011fu zaman yanl\u0131\u015f y\u00f6nlendirir; \u00e7\u00fcnk\u00fc DMARC de\u011ferlendirmesi \u201changi alan ad\u0131, hangi IP, hangi imza, hangi envelope-from\u201d sorular\u0131n\u0131n birle\u015fimidir.<\/p>\n<h2>Ad\u0131m 1: Header\u2019dan \u201cFrom\u201d, \u201cReturn-Path\u201d ve DKIM d= alan\u0131n\u0131 ay\u0131r\u0131n<\/h2>\n<p>DMARC\u2019\u0131 anlaman\u0131n en \u00f6nemli ad\u0131m\u0131, \u00fc\u00e7 alan ad\u0131n\u0131 birbirinden ay\u0131rmakt\u0131r:<\/p>\n<ul>\n<li><strong>Header From<\/strong>: Kullan\u0131c\u0131n\u0131n g\u00f6rd\u00fc\u011f\u00fc g\u00f6nderen alan ad\u0131 (\u00f6r. user@firma.com). DMARC politikas\u0131 bu alan ad\u0131na g\u00f6re uygulan\u0131r.<\/li>\n<li><strong>Envelope From \/ Return-Path<\/strong>: SPF\u2019in kontrol etti\u011fi alan ad\u0131 (\u00f6r. bounce@mailer.firma.com veya bounces@thirdparty.example).<\/li>\n<li><strong>DKIM d=<\/strong>: DKIM imzas\u0131n\u0131n ait oldu\u011fu alan ad\u0131 (\u00f6r. d=firma.com veya d=mail.firma.com).<\/li>\n<\/ul>\n<p>DMARC pass olmas\u0131 i\u00e7in, SPF veya DKIM\u2019den en az biri pass olmal\u0131 ve ayr\u0131ca pass olan mekanizman\u0131n alan ad\u0131 Header From ile alignment sa\u011flamal\u0131d\u0131r. Alignment relaxed veya strict olabilir; organizasyonun DMARC kayd\u0131nda hangi modlar\u0131n kullan\u0131ld\u0131\u011f\u0131na ba\u011fl\u0131 olarak de\u011ferlendirme de\u011fi\u015febilir.<\/p>\n<h2>Ad\u0131m 2: \u201cSPF pass ama DMARC fail\u201d senaryosunu do\u011fru okuyun<\/h2>\n<p>Bu senaryo genelde alignment problemidir. Yani SPF ger\u00e7ekten ge\u00e7mi\u015ftir, ama SPF\u2019in kontrol etti\u011fi alan ad\u0131 (Return-Path\/envelope-from) Header From ile uyumlu de\u011fildir. \u00d6rnek tipik durumlar:<\/p>\n<ul>\n<li>Bir \u00fc\u00e7\u00fcnc\u00fc taraf servis, kendi bounce domainini kullan\u0131yordur: Return-Path thirdparty.example, From firma.com. SPF pass olur, DMARC fail olabilir.<\/li>\n<li>Kurumsal alan ad\u0131nda From kullan\u0131l\u0131rken, uygulama ba\u015fka bir domain \u00fczerinden zarf g\u00f6ndereni at\u0131yordur.<\/li>\n<li>Y\u00f6nlendirme\/forwarding veya gateway senaryolar\u0131nda SPF\u2019in de\u011ferlendirdi\u011fi yol de\u011fi\u015fmi\u015ftir.<\/li>\n<\/ul>\n<p>Bu durumda \u00e7\u00f6z\u00fcm \u00e7o\u011fu zaman DKIM\u2019i do\u011fru kurup From ile align ettirmektir; \u00e7\u00fcnk\u00fc SPF alignment\u2019\u0131 \u00fc\u00e7\u00fcnc\u00fc taraflar\u0131n kontrol\u00fcndeki bounce domain nedeniyle sa\u011flamak her zaman m\u00fcmk\u00fcn de\u011fildir.<\/p>\n<h2>Ad\u0131m 3: \u201cDKIM pass ama DMARC fail\u201d neden olur?<\/h2>\n<p>\u0130lk bak\u0131\u015fta \u00e7eli\u015fkili g\u00f6r\u00fcn\u00fcr, ama burada da alignment devreye girer. DKIM=pass demek, imza kriptografik olarak do\u011fruland\u0131 demektir. DMARC i\u00e7in ise bu imzan\u0131n d= alan\u0131 Header From ile uyumlu olmal\u0131d\u0131r. S\u0131k nedenler:<\/p>\n<ul>\n<li><strong>d= farkl\u0131 bir domain<\/strong>: \u00d6rne\u011fin d=thirdparty.example, From=firma.com.<\/li>\n<li><strong>Yanl\u0131\u015f selector\/DNS yay\u0131l\u0131m\u0131<\/strong>: Baz\u0131 al\u0131c\u0131lar eski DNS\u2019i g\u00f6r\u00fcyor ve imza do\u011frulan\u0131yor gibi g\u00f6r\u00fcnse de farkl\u0131 yollarda do\u011frulama tutars\u0131zla\u015f\u0131yor.<\/li>\n<li><strong>Mesaj\u0131n g\u00f6vdede de\u011fi\u015fmesi<\/strong>: Baz\u0131 ge\u00e7itler (disclaimer ekleme, konu sat\u0131r\u0131 de\u011fi\u015fimi, i\u00e7erik filtreleri) DKIM imzas\u0131n\u0131 bozabilir. Burada bazen \u201cpass\u201d g\u00f6r\u00fclen \u00f6rnek ile \u201cfail\u201d olan \u00f6rnek farkl\u0131 ak\u0131\u015ftan ge\u00e7iyor olabilir.<\/li>\n<\/ul>\n<p>Bu ad\u0131mda kritik kontrol, DKIM d= de\u011ferinin kurumun From alan ad\u0131yla ayn\u0131 m\u0131 (veya relaxed alignment kapsam\u0131nda alt alan ad\u0131 m\u0131) oldu\u011fudur.<\/p>\n<h2>Ad\u0131m 4: DMARC fail\u2019in DNS kaynakl\u0131 yayg\u0131n nedenleri<\/h2>\n<h3>SPF kayd\u0131 yok, yanl\u0131\u015f yerde veya s\u00f6zdizimi hatal\u0131<\/h3>\n<p>SPF kayd\u0131, domainin TXT kayd\u0131d\u0131r ve tek bir do\u011fru SPF kayd\u0131 olmas\u0131 beklenir. Birden fazla SPF TXT kayd\u0131, yanl\u0131\u015f \u201cinclude\u201d kullan\u0131m\u0131 veya s\u00f6zdizimi hatalar\u0131 SPF\u2019in \u201cpermerror\/temperror\u201d \u00fcretmesine neden olabilir. SPF bozulursa DMARC\u2019\u0131n SPF taraf\u0131ndaki \u015fans\u0131 da d\u00fc\u015fer.<\/p>\n<h3>DKIM public key kayd\u0131 yanl\u0131\u015f selector\u2019da veya yanl\u0131\u015f domain alt\u0131nda<\/h3>\n<p>DKIM\u2019de selector._domainkey.domain.tld format\u0131 kullan\u0131l\u0131r. Selector ad\u0131 yanl\u0131\u015f se\u00e7ilirse, DNS kayd\u0131 yanl\u0131\u015f yere yaz\u0131l\u0131rsa veya kopyalama s\u0131ras\u0131nda anahtar k\u0131r\u0131l\u0131rsa DKIM fail olur. Ayr\u0131ca baz\u0131 kurumlar yanl\u0131\u015fl\u0131kla DKIM\u2019i subdomain\u2019e yaz\u0131p From alan ad\u0131n\u0131 root domain\u2019de tutarak alignment sorunlar\u0131 ya\u015fayabilir.<\/p>\n<h3>DMARC kayd\u0131 hatal\u0131 veya yanl\u0131\u015f subdomain\u2019de<\/h3>\n<p>DMARC kayd\u0131 _dmarc.domain.tld alt\u0131nda bulunur. Yanl\u0131\u015f konuma yaz\u0131l\u0131rsa al\u0131c\u0131 DMARC politikas\u0131n\u0131 bulamaz veya beklenmedik de\u011ferlendirme yapabilir. Ayr\u0131ca p=reject gibi kat\u0131 bir politika, k\u00fc\u00e7\u00fck bir yap\u0131land\u0131rma hatas\u0131nda bile teslimat\u0131 do\u011frudan etkileyebilir.<\/p>\n<h2>Ad\u0131m 5: Yetkisiz g\u00f6nderim mi, yoksa yanl\u0131\u015f yap\u0131land\u0131rma m\u0131?<\/h2>\n<p>DMARC fail her zaman \u201csald\u0131r\u0131 var\u201d anlam\u0131na gelmez. \u00c7ok s\u0131k, me\u015fru bir sistem yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015ft\u0131r. Ay\u0131rt etmek i\u00e7in \u015fu sorular i\u015fe yarar:<\/p>\n<ul>\n<li><strong>G\u00f6nderim hacmi<\/strong>: Aniden artan hacim ve farkl\u0131 \u00fclkeler\/IP\u2019ler yetkisiz kullan\u0131m\u0131 i\u015faret edebilir.<\/li>\n<li><strong>G\u00f6nderim kayna\u011f\u0131 biliniyor mu?<\/strong>: Kullan\u0131c\u0131 \u201cben g\u00f6nderdim\u201d diyorsa kimlik do\u011frulama sonu\u00e7lar\u0131na bakarak hangi sistem \u00fczerinden gitti\u011fi bulunabilir.<\/li>\n<li><strong>Header tutarl\u0131l\u0131\u011f\u0131<\/strong>: From alan ad\u0131 sizin, ama Return-Path ve DKIM d= tamamen yabanc\u0131ysa spoofing olas\u0131l\u0131\u011f\u0131 artar.<\/li>\n<\/ul>\n<p>Yetkisiz g\u00f6nderim \u015f\u00fcphesi varsa, parolalar ve hesap g\u00fcvenli\u011fi ad\u0131mlar\u0131 ayr\u0131 bir olay y\u00f6netimi s\u00fcrecini gerektirir. Yine de \u00e7o\u011fu teslimat probleminde k\u00f6k neden; SPF\/DKIM alignment eksikli\u011fi ve \u00fc\u00e7\u00fcnc\u00fc taraf g\u00f6ndericilerin do\u011fru yetkilendirilmemesidir.<\/p>\n<h2>Ad\u0131m 6: Pratik bir aksiyon plan\u0131 (k\u0131sa kontrol listesi)<\/h2>\n<ol>\n<li><strong>Bir \u00f6rnek mesaj se\u00e7in<\/strong> ve tam header\u2019\u0131 al\u0131n.<\/li>\n<li><strong>Header From<\/strong>, <strong>Return-Path<\/strong> ve <strong>DKIM d=<\/strong> domainlerini yaz\u0131n.<\/li>\n<li><strong>Authentication-Results<\/strong> sat\u0131r\u0131nda SPF, DKIM ve DMARC sonu\u00e7lar\u0131n\u0131 not edin.<\/li>\n<li>DMARC fail ise <strong>hangi taraf\u0131n (SPF mi DKIM mi) \u201cpass+aligned\u201d olamad\u0131\u011f\u0131n\u0131<\/strong> belirleyin.<\/li>\n<li>\u00dc\u00e7\u00fcnc\u00fc taraf g\u00f6nderim varsa, <strong>tercihen DKIM ile From domainine align<\/strong edin; m\u00fcmk\u00fcnse \u00f6zel g\u00f6nderim domaini\/subdomain kullan\u0131n.<\/li>\n<li>DNS\u2019te SPF\/DKIM\/DMARC kay\u0131tlar\u0131n\u0131 kontrol edin: tek SPF kayd\u0131, do\u011fru selector, do\u011fru _dmarc konumu, yaz\u0131m hatalar\u0131.<\/li>\n<li>De\u011fi\u015fiklik yapt\u0131ysan\u0131z, <strong>TTL ve yay\u0131l\u0131m s\u00fcresini<\/strong> hesaba kat\u0131n ve farkl\u0131 al\u0131c\u0131lara test g\u00f6nderimi yap\u0131n.<\/li>\n<\/ol>\n<h2>DMARC fail sorunlar\u0131n\u0131 kal\u0131c\u0131 olarak azaltman\u0131n yolu<\/h2>\n<p>Kal\u0131c\u0131 \u00e7\u00f6z\u00fcm, \u201ctek bir g\u00f6nderici yokmu\u015f gibi\u201d tasarlamakt\u0131r. Modern \u015firketlerde e-posta yaln\u0131zca kullan\u0131c\u0131lardan \u00e7\u0131kmaz; uygulamalar, cihazlar ve servisler de g\u00f6nderir. Bu y\u00fczden alan ad\u0131n\u0131z ad\u0131na g\u00f6nderim yapacak her kayna\u011f\u0131n en ba\u015ftan envanterini \u00e7\u0131kar\u0131n ve her biri i\u00e7in net bir authentication stratejisi belirleyin.<\/p>\n<p>MX1Mail gibi kurumsal e-posta hizmetlerinde domaininizin DNS ve kimlik do\u011frulama kay\u0131tlar\u0131n\u0131 d\u00fczenli ve dok\u00fcmante bi\u00e7imde y\u00f6netmek, hem teslim edilebilirli\u011fi hem de operasyonel g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc art\u0131r\u0131r. DMARC fail olaylar\u0131nda da ayn\u0131 disiplin, sorunu saatler i\u00e7inde de\u011fil dakikalar i\u00e7inde s\u0131n\u0131fland\u0131rman\u0131za yard\u0131mc\u0131 olur.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>DMARC fail durumlar\u0131nda SPF ve DKIM sonu\u00e7lar\u0131n\u0131, alignment kurallar\u0131n\u0131 ve DNS kaynakl\u0131 sorunlar\u0131 ad\u0131m ad\u0131m analiz ederek h\u0131zl\u0131 bir aksiyon plan\u0131 \u00e7\u0131kar\u0131n.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[109,350,348],"class_list":["post-145","post","type-post","status-publish","format-standard","hentry","category-e-posta-guvenligi","tag-dmarc","tag-e-posta-sorun-giderme","tag-spf-dkim-2"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/145","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/comments?post=145"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/145\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=145"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=145"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}