{"id":143,"date":"2026-10-12T17:01:20","date_gmt":"2026-10-12T14:01:20","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/crm-helpdesk-e-bulten-araclari-icin-spf-dkim-dmarc-coklu-gonderici-yetkilendirme\/"},"modified":"2026-10-12T17:01:20","modified_gmt":"2026-10-12T14:01:20","slug":"crm-helpdesk-e-bulten-araclari-icin-spf-dkim-dmarc-coklu-gonderici-yetkilendirme","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/crm-helpdesk-e-bulten-araclari-icin-spf-dkim-dmarc-coklu-gonderici-yetkilendirme\/","title":{"rendered":"CRM, Helpdesk ve E-B\u00fclten Ara\u00e7lar\u0131 \u0130\u00e7in SPF\/DKIM\/DMARC: \u00c7oklu G\u00f6nderici Kaynaklar\u0131n\u0131 G\u00fcvenli \u015eekilde Yetkilendirme"},"content":{"rendered":"<h2>Neden bu konu \u00f6nemlidir?<\/h2>\n<p>Bir\u00e7ok \u015firket ayn\u0131 alan ad\u0131n\u0131 (\u00f6r. @firma.com) kullanarak birden fazla sistemden e-posta g\u00f6nderir: CRM\u2019den sat\u0131\u015f otomasyon mailleri, helpdesk\u2019ten ticket bildirimleri, e-ticaret altyap\u0131s\u0131ndan sipari\u015f e-postalar\u0131, insan kaynaklar\u0131 ara\u00e7lar\u0131ndan davetler, e-b\u00fclten sisteminden kampanyalar gibi. Bu sistemlerin bir k\u0131sm\u0131 sizin mail sunucunuz \u00fczerinden de\u011fil, \u00fc\u00e7\u00fcnc\u00fc taraf sa\u011flay\u0131c\u0131lar\u0131n g\u00f6nderim altyap\u0131s\u0131 \u00fczerinden iletim yapar. Sonu\u00e7ta al\u0131c\u0131 tarafta \u201cBu alan ad\u0131na sahip maili ger\u00e7ekten bu firma m\u0131 g\u00f6nderdi?\u201d sorusuna teknik bir yan\u0131t gerekir.<\/p>\n<p>SPF, DKIM ve DMARC birlikte \u00e7al\u0131\u015farak bu yan\u0131t\u0131 \u00fcretir. Ancak \u00e7oklu g\u00f6nderici kaynaklar\u0131 s\u00f6z konusu oldu\u011funda yanl\u0131\u015f planlama; SPF limitlerine tak\u0131lma, DKIM imzas\u0131 gelmemesi, DMARC uyumsuzlu\u011fu ve en \u00f6nemlisi teslim edilebilirlik sorunlar\u0131yla sonu\u00e7lanabilir. Bu rehber, bir alan ad\u0131ndan birden fazla SaaS\/uygulama ile g\u00fcvenli ve tutarl\u0131 e-posta g\u00f6nderimi i\u00e7in pratik bir \u00e7er\u00e7eve sunar.<\/p>\n<h2>\u00d6nce resmi \u00e7\u0131kar\u0131n: Kim, ne g\u00f6nderiyor?<\/h2>\n<p>Teknik ayara ba\u015flamadan \u00f6nce en kritik ad\u0131m envanterdir. A\u015fa\u011f\u0131daki sorulara net yan\u0131t vermek sonraki t\u00fcm kararlar\u0131 kolayla\u015ft\u0131r\u0131r:<\/p>\n<ul>\n<li>Hangi sistemler \u015firket ad\u0131na e-posta g\u00f6nderiyor? (CRM, helpdesk, e-b\u00fclten, e-ticaret, uygulama sunucular\u0131, fatura sistemi vb.)<\/li>\n<li>Bu sistemler hangi adresten g\u00f6nderiyor? (From: sat\u0131\u015f@, destek@, noreply@ gibi)<\/li>\n<li>Ger\u00e7ekte hangi alan ad\u0131n\u0131 kullan\u0131yor? (ana domain mi, alt domain mi?)<\/li>\n<li>G\u00f6nderim hangi altyap\u0131dan \u00e7\u0131k\u0131yor? (Sizin SMTP\u2019niz mi, sa\u011flay\u0131c\u0131n\u0131n MTA\u2019lar\u0131 m\u0131?)<\/li>\n<li>Her sistem i\u00e7in DKIM imzas\u0131 var m\u0131 ve hangi domain\/selector ile imzalan\u0131yor?<\/li>\n<\/ul>\n<p>Bir\u00e7ok organizasyonda g\u00f6lge IT y\u00fcz\u00fcnden baz\u0131 ara\u00e7lar y\u0131llar \u00f6nce eklenmi\u015f ve kimlik do\u011frulama hi\u00e7 d\u00fc\u015f\u00fcn\u00fclmemi\u015f olabilir. DMARC raporlar\u0131 burada ayr\u0131ca yard\u0131mc\u0131 olabilir; ancak envanter \u00e7al\u0131\u015fmas\u0131 yine de \u015fartt\u0131r.<\/p>\n<h2>SPF: Kimler bu domain ad\u0131na mail g\u00f6nderebilir?<\/h2>\n<p>SPF, g\u00f6nderen sunucunun IP\u2019sinin (veya SPF kayd\u0131nda belirtilen mekanizmalar\u0131n) alan ad\u0131 taraf\u0131ndan yetkilendirilip yetkilendirilmedi\u011fini kontrol eder. \u00c7oklu SaaS kullan\u0131m\u0131 SPF\u2019i iki a\u00e7\u0131dan zorlar: \u201cinclude\u201d zincirlerinin b\u00fcy\u00fcmesi ve 10 DNS lookup limitine yakla\u015f\u0131lmas\u0131.<\/p>\n<h3>SPF\u2019te yap\u0131lacaklar<\/h3>\n<ul>\n<li>Tek bir SPF kayd\u0131 yay\u0131nlay\u0131n. Ayn\u0131 domain alt\u0131nda birden fazla SPF TXT kayd\u0131 hata \u00fcretir.<\/li>\n<li>Her \u00fc\u00e7\u00fcnc\u00fc taraf i\u00e7in onlar\u0131n \u00f6nerdi\u011fi include\/ipv4\/ipv6 kay\u0131tlar\u0131n\u0131 mevcut SPF\u2019e ekleyin.<\/li>\n<li>Politikay\u0131 ger\u00e7ek\u00e7i belirleyin: -all (fail), ~all (softfail) veya ?all (neutral). Tam reddetme karar\u0131 DMARC stratejinizle birlikte de\u011ferlendirilmelidir.<\/li>\n<li>SPF kayd\u0131n\u0131 b\u00fcy\u00fct\u00fcrken DNS lookup say\u0131s\u0131n\u0131 kontrol edin; include say\u0131s\u0131 artt\u0131k\u00e7a limit problemi olu\u015fabilir.<\/li>\n<\/ul>\n<h3>SPF\u2019te s\u0131k yap\u0131lan hatalar<\/h3>\n<ul>\n<li><strong>Birden fazla SPF TXT kayd\u0131 yay\u0131nlamak:<\/strong> \u201cv=spf1 &#8230;\u201d i\u00e7eren ikinci bir TXT eklemek sorunu \u00e7\u00f6zmez, daha da b\u00fcy\u00fct\u00fcr.<\/li>\n<li><strong>Yanl\u0131\u015f alan ad\u0131na SPF yazmak:<\/strong> Baz\u0131 ara\u00e7lar, g\u00f6ndereni farkl\u0131 bir return-path (envelope-from) alan ad\u0131yla ayarlayabilir. SPF kontrol\u00fc \u00e7o\u011funlukla envelope-from \u00fczerinde \u00e7al\u0131\u015f\u0131r.<\/li>\n<li><strong>\u2018Her \u015feyi ekleyelim\u2019 yakla\u015f\u0131m\u0131:<\/strong> Kullan\u0131lmayan sa\u011flay\u0131c\u0131lar\u0131 SPF i\u00e7inde tutmak gereksiz risk ve limit t\u00fcketimidir.<\/li>\n<\/ul>\n<h2>DKIM: \u0130\u00e7erik imzas\u0131 ve marka tutarl\u0131l\u0131\u011f\u0131<\/h2>\n<p>DKIM, e-postan\u0131n belirli ba\u015fl\u0131klar\u0131n\u0131 ve g\u00f6vdesini kriptografik olarak imzalayarak iletim s\u0131ras\u0131nda de\u011fi\u015ftirilmedi\u011fini ve imzan\u0131n ilgili domain ad\u0131na do\u011frulanabildi\u011fini g\u00f6sterir. \u00c7oklu sistemlerde DKIM\u2019in de\u011feri artar; \u00e7\u00fcnk\u00fc SPF baz\u0131 senaryolarda (\u00f6zellikle y\u00f6nlendirmeler ve baz\u0131 ge\u00e7i\u015fler) zay\u0131flayabilirken, DKIM imzas\u0131 korunabilir.<\/p>\n<h3>\u00c7oklu SaaS ortam\u0131nda DKIM plan\u0131<\/h3>\n<ul>\n<li>Her sa\u011flay\u0131c\u0131 i\u00e7in ayr\u0131 DKIM selector kullan\u0131n. \u00d6rne\u011fin: crm1, helpdesk1, newsletter1 gibi. Bu hem y\u00f6netimi kolayla\u015ft\u0131r\u0131r hem de sorun gidermede h\u0131z kazand\u0131r\u0131r.<\/li>\n<li>M\u00fcmk\u00fcnse ayn\u0131 \u201cFrom:\u201d domaini ile uyumlu DKIM imzas\u0131 kullan\u0131n. DMARC a\u00e7\u0131s\u0131ndan \u00f6nemli olan \u201calignment\u201d yani uyumdur.<\/li>\n<li>DKIM DNS kay\u0131tlar\u0131n\u0131 yay\u0131nlad\u0131ktan sonra sa\u011flay\u0131c\u0131n\u0131n panelinde do\u011frulama ad\u0131m\u0131n\u0131 tamamlay\u0131n; sadece DNS\u2019e eklemek yetmez.<\/li>\n<li>Anahtar \u00f6mr\u00fc\/rotasyon plan\u0131 yap\u0131n. Zamanla sa\u011flay\u0131c\u0131 de\u011fi\u015febilir veya anahtar rotasyonu gerekebilir.<\/li>\n<\/ul>\n<h3>DKIM\u2019de tipik sorunlar<\/h3>\n<ul>\n<li><strong>Yanl\u0131\u015f TXT de\u011feri:<\/strong> Kopyalama s\u0131ras\u0131nda t\u0131rnak, bo\u015fluk veya sat\u0131r b\u00f6l\u00fcnmesi hatalar\u0131.<\/li>\n<li><strong>Yanl\u0131\u015f kay\u0131t t\u00fcr\u00fc veya isim:<\/strong> Selector._domainkey.domain.tld yap\u0131s\u0131n\u0131n bozulmas\u0131.<\/li>\n<li><strong>Sa\u011flay\u0131c\u0131n\u0131n farkl\u0131 domain ile imzalamas\u0131:<\/strong> Baz\u0131 sistemler kendi domainleriyle DKIM imzalar; bu durumda DMARC uyumu bozulabilir.<\/li>\n<\/ul>\n<h2>DMARC: Politika, g\u00f6r\u00fcn\u00fcrl\u00fck ve tutarl\u0131 uygulama<\/h2>\n<p>DMARC, al\u0131c\u0131 tarafa iki \u015feyi s\u00f6yler: \u201cBu domain i\u00e7in SPF\/DKIM sonu\u00e7lar\u0131n\u0131 hangi uyum kurallar\u0131yla de\u011ferlendireceksin?\u201d ve \u201cBa\u015far\u0131s\u0131z olursa ne yapacaks\u0131n?\u201d. Ayr\u0131ca raporlama mekanizmalar\u0131yla g\u00f6r\u00fcn\u00fcrl\u00fck sa\u011flar.<\/p>\n<h3>DMARC\u2019in \u00e7oklu g\u00f6nderici kaynaklar\u0131ndaki rol\u00fc<\/h3>\n<ul>\n<li>Hangi sistemlerin do\u011fru yetkilendirildi\u011fini g\u00f6rmenizi sa\u011flar.<\/li>\n<li>Hatal\u0131 yap\u0131land\u0131r\u0131lm\u0131\u015f SaaS ara\u00e7lar\u0131n\u0131 erken yakalat\u0131r.<\/li>\n<li>Sahte g\u00f6nderimleri azaltmaya yard\u0131mc\u0131 olur; \u00f6zellikle politika seviyeniz s\u0131k\u0131la\u015ft\u0131k\u00e7a.<\/li>\n<\/ul>\n<h3>Pratik DMARC yakla\u015f\u0131m\u0131<\/h3>\n<ol>\n<li><strong>Ba\u015flang\u0131\u00e7ta g\u00f6r\u00fcn\u00fcrl\u00fck:<\/strong> p=none ile ba\u015flay\u0131p rapor toplay\u0131n.<\/li>\n<li><strong>Kaynaklar\u0131 s\u0131n\u0131fland\u0131r\u0131n:<\/strong> Me\u015fru kaynaklar, yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f me\u015fru kaynaklar ve yetkisiz kaynaklar.<\/li>\n<li><strong>Uyumu d\u00fczeltin:<\/strong> \u00d6ncelik, kritik i\u015f e-postalar\u0131 (fatura, \u015fifre s\u0131f\u0131rlama, sipari\u015f) olmal\u0131d\u0131r.<\/li>\n<li><strong>Kademeli s\u0131k\u0131la\u015ft\u0131rma:<\/strong> quarantine ve daha sonra reject seviyesine ge\u00e7i\u015fi kontroll\u00fc yap\u0131n.<\/li>\n<\/ol>\n<h2>Alt domain stratejisi: Riskleri ve itibar\u0131 ay\u0131r\u0131n<\/h2>\n<p>\u00c7oklu g\u00f6nderim yapan \u015firketler i\u00e7in en temiz y\u00f6ntemlerden biri i\u015f y\u00fcklerini alt domainlere b\u00f6lmektir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>news.firma.com: e-b\u00fclten ve pazarlama<\/li>\n<li>notify.firma.com: uygulama bildirimleri<\/li>\n<li>support.firma.com: helpdesk<\/li>\n<\/ul>\n<p>Bu yakla\u015f\u0131m\u0131n faydas\u0131; SPF\/DKIM\/DMARC ayarlar\u0131n\u0131n daha sade hale gelmesi, itibar\u0131n ayr\u0131\u015fmas\u0131 ve bir kanal\u0131n sorun ya\u015famas\u0131 durumunda di\u011fer kanallar\u0131n daha az etkilenmesidir. Ancak marka alg\u0131s\u0131 ve \u201cFrom:\u201d adreslerinin kullan\u0131c\u0131 beklentisi de g\u00f6zetilmelidir.<\/p>\n<h2>De\u011fi\u015fiklik y\u00f6netimi: DNS, TTL ve test<\/h2>\n<p>Kimlik do\u011frulama ayarlar\u0131 genellikle DNS \u00fczerinde y\u00fcr\u00fcr; bu da de\u011fi\u015fikliklerin yay\u0131lma s\u00fcresi ve geri d\u00f6n\u00fc\u015f plan\u0131 gerektirdi\u011fi anlam\u0131na gelir.<\/p>\n<ul>\n<li>De\u011fi\u015fiklikten \u00f6nce TTL de\u011ferlerini g\u00f6zden ge\u00e7irin; kritik de\u011fi\u015fikliklerde ge\u00e7ici olarak d\u00fc\u015f\u00fcrmek i\u015fleri kolayla\u015ft\u0131rabilir.<\/li>\n<li>Her sa\u011flay\u0131c\u0131 eklemesinden sonra k\u00fc\u00e7\u00fck kapsaml\u0131 test g\u00f6nderimleri yap\u0131n ve sonu\u00e7lar\u0131 kontrol edin.<\/li>\n<li>SPF\/DKIM\/DMARC de\u011fi\u015fikliklerini tek seferde de\u011fil, kontroll\u00fc ad\u0131mlarla uygulay\u0131n.<\/li>\n<li>Kayd\u0131 \u201ctemiz\u201d tutun: kullan\u0131lmayan include\u2019lar\u0131 kald\u0131r\u0131n, hangi sat\u0131r\u0131n hangi sisteme ait oldu\u011funu i\u00e7 dok\u00fcmantasyonda belirtin.<\/li>\n<\/ul>\n<h2>Operasyonel kontrol listesi<\/h2>\n<ul>\n<li>G\u00f6nderici envanteri \u00e7\u0131kar\u0131ld\u0131 ve sahiplik belirlendi (hangi ekip\/kim sorumlu?).<\/li>\n<li>Tek SPF kayd\u0131 var ve gereksiz include yok.<\/li>\n<li>Her sistemin DKIM\u2019i etkin ve do\u011fru domain ile uyumlu.<\/li>\n<li>DMARC raporlar\u0131 takip ediliyor ve aksiyon plan\u0131 var.<\/li>\n<li>Yeni bir SaaS eklendi\u011finde standart prosed\u00fcr: \u00f6nce alt domain karar\u0131, sonra SPF\/DKIM, sonra DMARC uyumu.<\/li>\n<li>\u0130\u015ften ayr\u0131lan \u00e7al\u0131\u015fanlar veya kapanan ara\u00e7lar sonras\u0131nda DNS temizli\u011fi yap\u0131l\u0131yor.<\/li>\n<\/ul>\n<h2>Sonu\u00e7: \u00c7oklu g\u00f6ndericiyle d\u00fczenli ve g\u00fcvenli e-posta m\u00fcmk\u00fcn<\/h2>\n<p>Modern \u015firketler tek bir mail sunucusuyla yetinmiyor; e-postan\u0131n \u00fcretildi\u011fi yerler \u00e7o\u011fal\u0131yor. Bu da kimlik do\u011frulama tasar\u0131m\u0131n\u0131 bir \u201ctek seferlik kay\u0131t\u201d i\u015finden \u00e7\u0131kar\u0131p ya\u015fayan bir y\u00f6neti\u015fim s\u00fcrecine d\u00f6n\u00fc\u015ft\u00fcr\u00fcyor. SPF\u2019in s\u0131n\u0131rlar\u0131n\u0131 ve bak\u0131m ihtiyac\u0131n\u0131 kabul edip DKIM\u2019i sa\u011flam kurmak, DMARC ile g\u00f6r\u00fcn\u00fcrl\u00fck ve politika disiplini sa\u011flamak uzun vadede teslim edilebilirli\u011fi koruman\u0131n en pratik yoludur.<\/p>\n<p>Alan ad\u0131n\u0131z\u0131n DNS\u2019ini ve kurumsal posta ak\u0131\u015f\u0131n\u0131 y\u00f6netirken, posta kutular\u0131 ve domain ayarlar\u0131n\u0131 merkezi bir \u015fekilde y\u00f6netebilece\u011finiz bir yap\u0131 operasyonel y\u00fck\u00fc azalt\u0131r. MX1Mail kullanan ekipler, bu t\u00fcr kimlik do\u011frulama de\u011fi\u015fikliklerini planlarken posta altyap\u0131s\u0131 y\u00f6netimini daha d\u00fczenli bir s\u00fcre\u00e7 haline getirebilir.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CRM, destek sistemi ve e-b\u00fclten gibi \u00fc\u00e7\u00fcnc\u00fc taraf ara\u00e7lar ayn\u0131 domainden e-posta g\u00f6nderirken SPF\/DKIM\/DMARC\u2019\u0131 nas\u0131l planlayaca\u011f\u0131n\u0131z\u0131, hatalar\u0131 nas\u0131l \u00f6nleyece\u011finizi ve teslim edilebilirli\u011fi nas\u0131l koruyaca\u011f\u0131n\u0131z\u0131 \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-143","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\/143","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=143"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/143\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}