{"id":115,"date":"2026-10-06T13:43:02","date_gmt":"2026-10-06T10:43:02","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/dmarc-alignment-uyum-relaxed-strict\/"},"modified":"2026-10-06T13:43:02","modified_gmt":"2026-10-06T10:43:02","slug":"dmarc-alignment-uyum-relaxed-strict","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/dmarc-alignment-uyum-relaxed-strict\/","title":{"rendered":"DMARC Alignment (Uyum) Nedir? Relaxed ve Strict Modlar\u0131 Nas\u0131l Se\u00e7ilir?"},"content":{"rendered":"<h2>DMARC alignment (uyum) ne demektir?<\/h2>\n<p>DMARC, bir e-postan\u0131n ger\u00e7ekten alan ad\u0131n\u0131z ad\u0131na g\u00f6nderilip g\u00f6nderilmedi\u011fini de\u011ferlendirirken iki temel sinyale bakar: SPF ve DKIM sonu\u00e7lar\u0131. Ancak DMARC i\u00e7in sadece \u201cSPF ge\u00e7ti\u201d veya \u201cDKIM ge\u00e7ti\u201d demek yeterli de\u011fildir. As\u0131l kritik nokta alignment (uyum) dedi\u011fimiz kontrollerdir.<\/p>\n<p>Alignment, kimlik do\u011frulama kontrol\u00fcn\u00fcn (SPF veya DKIM) hangi alan ad\u0131na ba\u011fland\u0131\u011f\u0131n\u0131, e-postada g\u00f6r\u00fcnen From (G\u00f6nderen) alan\u0131ndaki domain ile e\u015fle\u015ftirir. Yani DMARC \u015fu soruyu sorar: \u201cKullan\u0131c\u0131n\u0131n ekranda g\u00f6rd\u00fc\u011f\u00fc From domain\u2019i ile SPF\/DKIM\u2019in do\u011frulad\u0131\u011f\u0131 domain ayn\u0131 m\u0131?\u201d Bu yakla\u015f\u0131m, sahte From adresi kullan\u0131larak yap\u0131lan oltalama ve spoofing giri\u015fimlerini azaltman\u0131n temel par\u00e7alar\u0131ndan biridir.<\/p>\n<h2>DMARC neden From alan\u0131na odaklan\u0131r?<\/h2>\n<p>\u00c7o\u011fu al\u0131c\u0131, mesaj\u0131n ger\u00e7ek kayna\u011f\u0131n\u0131 teknik header\u2019lardan de\u011fil From sat\u0131r\u0131ndan anlar. Sald\u0131rganlar da bu y\u00fczden genellikle From\u2019u taklit eder. SPF \u00e7o\u011fu zaman g\u00f6r\u00fcnmeyen Return-Path (MAIL FROM) veya HELO kimli\u011fini do\u011frular; DKIM ise bir imzaya ba\u011fl\u0131 d= alan\u0131 ile domain belirtir. DMARC, bu mekanizmalar\u0131 From domain\u2019iyle \u201cuyumlu\u201d hale getirerek al\u0131c\u0131n\u0131n g\u00f6rd\u00fc\u011f\u00fc marka\/alan ad\u0131 ile do\u011frulama sonu\u00e7lar\u0131n\u0131 ili\u015fkilendirir.<\/p>\n<h2>SPF alignment nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>SPF kontrol\u00fc, g\u00f6nderen sunucunun IP\u2019sinin bir alan ad\u0131n\u0131n SPF kayd\u0131nda izinli olup olmad\u0131\u011f\u0131na bakar. DMARC a\u00e7\u0131s\u0131ndan \u00f6nemli olan, SPF\u2019in ge\u00e7ti\u011fi domain\u2019in (SPF domain\u2019i) From domain\u2019i ile uyumlu olup olmad\u0131\u011f\u0131d\u0131r.<\/p>\n<h3>Hangi domain k\u0131yaslan\u0131r?<\/h3>\n<p>DMARC, SPF i\u00e7in genellikle Return-Path (envelope-from \/ MAIL FROM) alan\u0131ndaki domain\u2019i baz al\u0131r. Baz\u0131 durumlarda HELO\/EHLO domain\u2019i de devreye girebilir; fakat pratikte alignment tart\u0131\u015fmas\u0131 \u00e7o\u011funlukla Return-Path \u00fczerindendir.<\/p>\n<h3>\u00d6rnek<\/h3>\n<p>From: example.com g\u00f6r\u00fcn\u00fcyor diyelim. E\u011fer mesaj\u0131n Return-Path\u2019i bounce.example.com ve SPF bu domain \u00fczerinden ge\u00e7iyorsa, alignment politikas\u0131 relaxed ise genellikle uyum kabul edilir; strict ise From ile birebir ayn\u0131 domain aran\u0131r (example.com).<\/p>\n<h2>DKIM alignment nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>DKIM, mesaj\u0131n belirli b\u00f6l\u00fcmlerinin de\u011fi\u015fmedi\u011fini ve bir domain taraf\u0131ndan imzaland\u0131\u011f\u0131n\u0131 kriptografik olarak do\u011frular. DMARC i\u00e7in kritik olan, imzada yer alan d= domain\u2019inin From domain\u2019i ile uyumudur.<\/p>\n<h3>\u00d6rnek<\/h3>\n<p>From: example.com iken DKIM imzas\u0131nda d=mailer.example.com ise relaxed modda uyum say\u0131labilir. Strict modda From ile d= alan\u0131n\u0131n birebir ayn\u0131 olmas\u0131 gerekir.<\/p>\n<h2>Relaxed ve Strict: Uyum modlar\u0131 ne anlama gelir?<\/h2>\n<p>DMARC\u2019ta alignment i\u00e7in iki mod vard\u0131r: relaxed (r) ve strict (s). Bu modlar SPF ve DKIM i\u00e7in ayr\u0131 ayr\u0131 tan\u0131mlanabilir.<\/p>\n<ul>\n<li><strong>Relaxed alignment:<\/strong> From domain\u2019i ile SPF\/DKIM domain\u2019i ayn\u0131 \u201corganizational domain\u201d alt\u0131nda ise uyumlu kabul edilir. \u00d6rne\u011fin example.com ile mail.example.com \u00e7o\u011fu senaryoda uyumludur.<\/li>\n<li><strong>Strict alignment:<\/strong> Domain\u2019in birebir ayn\u0131 olmas\u0131 gerekir. example.com ile mail.example.com uyumlu say\u0131lmaz.<\/li>\n<\/ul>\n<p>DMARC kayd\u0131n\u0131zda bu ayarlar adkim (DKIM alignment) ve aspf (SPF alignment) parametreleri ile yap\u0131l\u0131r.<\/p>\n<h2>Organizational domain (kurumsal ana domain) neden \u00f6nemlidir?<\/h2>\n<p>Relaxed modun temelinde \u201corganizational domain\u201d kavram\u0131 vard\u0131r. Basit\u00e7e anlatmak gerekirse, bir alan ad\u0131n\u0131n as\u0131l k\u00f6k\u00fcne dayal\u0131 de\u011ferlendirme yap\u0131l\u0131r. \u00d6rne\u011fin mail.example.com ile example.com ayn\u0131 organizasyon domain\u2019inde oldu\u011fu i\u00e7in relaxed uyum sa\u011flayabilir. Bu, \u015firketlerin alt alan adlar\u0131yla (subdomain) e-posta ak\u0131\u015flar\u0131n\u0131 y\u00f6netmesini kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>Ancak bu kolayl\u0131k, yanl\u0131\u015f kurgulanm\u0131\u015f g\u00f6nderim altyap\u0131lar\u0131nda beklenmedik sonu\u00e7lara da yol a\u00e7abilir. \u00d6zellikle pazarlama servisleri, bildirim sistemleri veya farkl\u0131 departmanlar\u0131n farkl\u0131 subdomain\u2019ler kullanmas\u0131 durumunda, uyum stratejisi net olmal\u0131d\u0131r.<\/p>\n<h2>Hangi durumda relaxed se\u00e7ilmeli?<\/h2>\n<p>Relaxed alignment, \u00e7o\u011fu i\u015fletme i\u00e7in ba\u015flang\u0131\u00e7 ve genel kullan\u0131m a\u00e7\u0131s\u0131ndan daha toleransl\u0131 ve pratiktir. A\u015fa\u011f\u0131daki senaryolarda relaxed tercih etmek daha az kesintiyle ilerlemenizi sa\u011flar:<\/p>\n<ul>\n<li><strong>Alt alan adlar\u0131yla g\u00f6nderim:<\/strong> transactional.example.com, mail.example.com gibi subdomain\u2019lerden d\u00fczenli g\u00f6nderim yap\u0131l\u0131yorsa.<\/li>\n<li><strong>Birden fazla sistemle e-posta g\u00f6nderimi:<\/strong> CRM, bilet sistemi, uygulama bildirimleri gibi farkl\u0131 kaynaklar ayn\u0131 g\u00f6r\u00fcnen From domain\u2019ini kullan\u0131yorsa ve hepsini strict hizaya getirmek k\u0131sa vadede zorsa.<\/li>\n<li><strong>Ge\u00e7i\u015f s\u00fcreci:<\/strong> DMARC\u2019\u0131 raporlama (p=none) veya kademeli uygulama ile devreye al\u0131rken, \u00f6nce relaxed ile g\u00f6r\u00fcn\u00fcrl\u00fck elde etmek isteniyorsa.<\/li>\n<\/ul>\n<p>Relaxed se\u00e7mek \u201cdaha az g\u00fcvenli\u201d gibi anla\u015f\u0131lmamal\u0131d\u0131r. Do\u011fru kurgu ve d\u00fczenli takip ile relaxed, hem y\u00f6netilebilirlik hem de koruma a\u00e7\u0131s\u0131ndan iyi bir denge sa\u011flayabilir.<\/p>\n<h2>Hangi durumda strict se\u00e7ilmeli?<\/h2>\n<p>Strict alignment, kurumsal kimli\u011finizi daha s\u0131k\u0131 kurallarla korumak istedi\u011finizde anlam kazan\u0131r. Fakat strict se\u00e7meden \u00f6nce t\u00fcm g\u00f6nderen sistemlerin birebir ayn\u0131 domain \u00fczerinden hizalanabildi\u011finden emin olmak gerekir.<\/p>\n<ul>\n<li><strong>Tek bir From domain standard\u0131:<\/strong> T\u00fcm e-postalar sadece example.com From\u2019u ile \u00e7\u0131k\u0131yor ve imza\/Return-Path da ayn\u0131 domain\u2019e kolayca ba\u011flanabiliyorsa.<\/li>\n<li><strong>Y\u00fcksek riskli hedef profili:<\/strong> Finans, y\u00f6netim, bordro gibi BEC ve kimli\u011fe b\u00fcr\u00fcnme riskinin y\u00fcksek oldu\u011fu ekiplerin alan ad\u0131nda maksimum tutarl\u0131l\u0131k hedefleniyorsa.<\/li>\n<li><strong>Subdomain karma\u015fas\u0131 istenmiyorsa:<\/strong> Pazarlama, bildirim ve operasyonel e-postalar\u0131n farkl\u0131 domain\/subdomain\u2019lere ayr\u0131ld\u0131\u011f\u0131 net bir mimari kurulmu\u015fsa.<\/li>\n<\/ul>\n<p>Strict modun dezavantaj\u0131, k\u00fc\u00e7\u00fck bir yap\u0131land\u0131rma sapmas\u0131n\u0131n bile DMARC ba\u015far\u0131s\u0131zl\u0131\u011f\u0131na yol a\u00e7abilmesidir. Bu da teslimat sorunlar\u0131na veya beklenmedik reddedilmelere neden olabilir.<\/p>\n<h2>Alignment hatalar\u0131 \u015firkette nas\u0131l belirtiler \u00fcretir?<\/h2>\n<p>Alignment sorunlar\u0131 genellikle \u201cSPF ge\u00e7iyor ama DMARC fail\u201d veya \u201cDKIM pass var ama DMARC fail\u201d gibi kafa kar\u0131\u015ft\u0131r\u0131c\u0131 durumlar yarat\u0131r. \u00c7\u00fcnk\u00fc DMARC de\u011ferlendirmesi, tek tek SPF\/DKIM sonu\u00e7lar\u0131ndan ziyade \u201cpass + alignment\u201d ko\u015fulunu arar.<\/p>\n<p>Tipik belirtiler:<\/p>\n<ul>\n<li>Belirli al\u0131c\u0131larda e-postalar\u0131n spam\u2019a d\u00fc\u015fmesi<\/li>\n<li>Baz\u0131 sistemlerden giden e-postalar\u0131n reddedilmesi<\/li>\n<li>DMARC raporlar\u0131nda farkl\u0131 domain\u2019lerin g\u00f6r\u00fcn\u00fcyor olmas\u0131 (\u00f6zellikle beklenmeyen Return-Path veya d= de\u011ferleri)<\/li>\n<\/ul>\n<h2>Do\u011fru alignment stratejisi nas\u0131l planlan\u0131r?<\/h2>\n<h3>1) G\u00f6nderim kaynaklar\u0131n\u0131 envanterleyin<\/h3>\n<p>\u015eirket ad\u0131na e-posta g\u00f6nderen t\u00fcm sistemleri listeleyin: kullan\u0131c\u0131 mailbox\u2019lar\u0131, web uygulamalar\u0131, b\u00fclten\/duyuru g\u00f6nderimleri, helpdesk, ERP\/CRM, cihaz alarmlar\u0131 ve \u00fc\u00e7\u00fcnc\u00fc taraf entegrasyonlar.<\/p>\n<h3>2) From domain standard\u0131n\u0131 belirleyin<\/h3>\n<p>Her sistemin From olarak hangi domain\u2019i kullanaca\u011f\u0131n\u0131 kararla\u015ft\u0131r\u0131n. M\u00fcmk\u00fcnse pazarlama ve otomasyon trafi\u011fini ayr\u0131 subdomain\u2019lere ay\u0131rmak operasyonel e-postalar\u0131n itibar\u0131n\u0131 korumaya yard\u0131mc\u0131 olabilir.<\/p>\n<h3>3) SPF ve DKIM\u2019i From ile hizalay\u0131n<\/h3>\n<p>Her kaynak i\u00e7in ya SPF alignment ya da DKIM alignment (ideal olarak ikisi de) sa\u011flanmal\u0131d\u0131r. Bu, Return-Path domain\u2019inin ve DKIM d= domain\u2019inin From domain politikas\u0131yla tutarl\u0131 olmas\u0131n\u0131 gerektirir.<\/p>\n<h3>4) DMARC parametrelerini bilin\u00e7li se\u00e7in<\/h3>\n<p>Relaxed\/strict karar\u0131n\u0131z\u0131, altyap\u0131n\u0131z\u0131n olgunlu\u011funa g\u00f6re verin. Bir\u00e7ok kurum i\u00e7in ba\u015flang\u0131\u00e7ta relaxed, daha sonra belirli ak\u0131\u015flarda strict yakla\u015f\u0131m\u0131 uygulanabilir bir yol haritas\u0131d\u0131r.<\/p>\n<h3>5) De\u011fi\u015fiklikleri kontroll\u00fc uygulay\u0131n<\/h3>\n<p>Tek seferde t\u00fcm ak\u0131\u015flar\u0131 de\u011fi\u015ftirmek yerine, \u00f6nce en kritik ve en y\u00fcksek hacimli kaynaklardan ba\u015flay\u0131n. B\u00f6ylece olas\u0131 hatalar\u0131 daha h\u0131zl\u0131 izole edebilirsiniz.<\/p>\n<h2>Yayg\u0131n senaryolar ve pratik kararlar<\/h2>\n<h3>\u00dc\u00e7\u00fcnc\u00fc taraf \u00fczerinden g\u00f6nderim<\/h3>\n<p>Bir sa\u011flay\u0131c\u0131 \u00fczerinden, sizin alan ad\u0131n\u0131zla From kullanarak e-posta g\u00f6nderiyorsan\u0131z alignment kritik hale gelir. Bu durumda sa\u011flay\u0131c\u0131n\u0131n DKIM imzas\u0131n\u0131 sizin From domain\u2019inizle uyumlu \u00e7al\u0131\u015ft\u0131rmak \u00e7o\u011fu zaman en temiz \u00e7\u00f6z\u00fcmd\u00fcr. SPF taraf\u0131nda ise Return-Path domain\u2019i farkl\u0131 kalabiliyorsa, strict SPF alignment se\u00e7mek gereksiz hata \u00fcretebilir.<\/p>\n<h3>Hem SPF hem DKIM gerekiyor mu?<\/h3>\n<p>DMARC i\u00e7in teknik olarak SPF veya DKIM\u2019den birinin \u201cpass + alignment\u201d sa\u011flamas\u0131 yeterlidir. Ancak operasyonel dayan\u0131kl\u0131l\u0131k i\u00e7in ikisini birden do\u011fru kurgulamak iyi bir uygulamad\u0131r. Bir taraf bozuldu\u011funda di\u011feri koruma sa\u011flayabilir.<\/p>\n<h2>Son kontrol listesi<\/h2>\n<ul>\n<li><strong>From domain<\/strong> \u015firket standard\u0131na uygun mu?<\/li>\n<li><strong>Return-Path domain<\/strong> biliniyor ve y\u00f6netiliyor mu?<\/li>\n<li><strong>DKIM d= domain<\/strong> beklenen domain\/subdomain mi?<\/li>\n<li><strong>aspf\/adkim<\/strong> relaxed mi strict mi, bilin\u00e7li mi se\u00e7ildi?<\/li>\n<li>Yeni bir sistem devreye girdi\u011finde bu hizalama kurallar\u0131 tekrar kontrol ediliyor mu?<\/li>\n<\/ul>\n<h2>Sonu\u00e7: Uyum do\u011fruysa DMARC ger\u00e7ekten \u00e7al\u0131\u015f\u0131r<\/h2>\n<p>DMARC\u2019\u0131n ba\u015far\u0131s\u0131, SPF ve DKIM\u2019in varl\u0131\u011f\u0131ndan \u00e7ok alignment kurgusunun do\u011frulu\u011funa ba\u011fl\u0131d\u0131r. Relaxed mod, \u00e7oklu sistem ve subdomain yap\u0131lar\u0131nda esneklik sa\u011flarken; strict mod, kontrol edilebilir ve standartla\u015fm\u0131\u015f ortamlarda daha s\u0131k\u0131 bir tutarl\u0131l\u0131k sunar. En do\u011fru se\u00e7im, \u015firketinizin g\u00f6nderim mimarisi, operasyonel disiplin seviyesi ve risk profilinin birlikte de\u011ferlendirilmesiyle yap\u0131l\u0131r.<\/p>\n<p>Alan ad\u0131n\u0131z\u0131 MX1Mail \u00fczerinde y\u00f6netiyor veya MX1Mail\u2019e ge\u00e7i\u015f planl\u0131yorsan\u0131z, SPF\/DKIM\/DMARC yap\u0131land\u0131rmalar\u0131n\u0131 yaparken alignment mant\u0131\u011f\u0131n\u0131 ba\u015ftan do\u011fru tasarlamak; teslimat s\u00fcreklili\u011fi ve marka g\u00fcvenilirli\u011fi a\u00e7\u0131s\u0131ndan i\u015fleri belirgin \u015fekilde kolayla\u015ft\u0131r\u0131r.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>DMARC alignment kavram\u0131n\u0131, SPF\/DKIM uyumunun nas\u0131l kontrol edildi\u011fini ve relaxed\/strict ayarlar\u0131n\u0131n \u015firketler i\u00e7in ne zaman uygun oldu\u011funu ad\u0131m ad\u0131m \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[261],"tags":[104,109,99],"class_list":["post-115","post","type-post","status-publish","format-standard","hentry","category-e-posta-kimlik-dogrulama","tag-dkim","tag-dmarc","tag-spf"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/115","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=115"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/115\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=115"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=115"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=115"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}