{"id":123,"date":"2026-10-07T17:01:34","date_gmt":"2026-10-07T14:01:34","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/isletmeler-icin-subdomain-stratejisi-islemsel-pazarlama-eposta-ayirma\/"},"modified":"2026-10-07T17:01:34","modified_gmt":"2026-10-07T14:01:34","slug":"isletmeler-icin-subdomain-stratejisi-islemsel-pazarlama-eposta-ayirma","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/isletmeler-icin-subdomain-stratejisi-islemsel-pazarlama-eposta-ayirma\/","title":{"rendered":"\u0130\u015fletmeler \u0130\u00e7in Subdomain Stratejisi: \u0130\u015flemsel ve Pazarlama E-Postalar\u0131n\u0131 Ay\u0131rmak (SPF\/DKIM\/DMARC ile)"},"content":{"rendered":"<h2>Neden \u201csubdomain ile ay\u0131rma\u201d konusu \u00f6nemlidir?<\/h2>\n<p>Bir \u015firketin e-posta trafi\u011fi genellikle iki b\u00fcy\u00fck gruba ayr\u0131l\u0131r: i\u015flemsel e-postalar (sipari\u015f onay\u0131, parola s\u0131f\u0131rlama, fatura, kargo bildirimi, randevu hat\u0131rlatmas\u0131) ve pazarlama\/toplu e-postalar (b\u00fclten, kampanya, duyuru, etkinlik daveti). Bu iki t\u00fcr e-postan\u0131n hedefi, al\u0131c\u0131 davran\u0131\u015f\u0131 ve \u015fikayet oran\u0131 farkl\u0131 oldu\u011fu i\u00e7in teslim edilebilirlik ve itibar y\u00f6netimi a\u00e7\u0131s\u0131ndan ayn\u0131 \u201cg\u00f6nderen kimli\u011fi\u201d alt\u0131nda tutulmas\u0131 riskli olabilir.<\/p>\n<p>Subdomain stratejisi, ayn\u0131 ana domaini (\u00f6r. sirket.com) kullanmaya devam ederken belirli e-posta ak\u0131\u015flar\u0131n\u0131 ayr\u0131 bir alt domainde (\u00f6r. mail.sirket.com veya bulten.sirket.com) toplaman\u0131z\u0131 sa\u011flar. B\u00f6ylece kimlik do\u011frulama kay\u0131tlar\u0131n\u0131 (SPF\/DKIM\/DMARC) ve itibar etkilerini daha kontroll\u00fc y\u00f6netebilir, sorun ya\u015fanan bir ak\u0131\u015f\u0131n di\u011ferini etkilemesini s\u0131n\u0131rlayabilirsiniz.<\/p>\n<h2>\u0130\u015flemsel ve pazarlama e-postas\u0131 aras\u0131ndaki temel farklar<\/h2>\n<h3>\u0130\u015flemsel e-posta (transactional)<\/h3>\n<ul>\n<li><strong>Beklenen e-posta<\/strong>: Kullan\u0131c\u0131 bir i\u015flem yapt\u0131\u011f\u0131 i\u00e7in e-postay\u0131 bekler.<\/li>\n<li><strong>Daha y\u00fcksek etkile\u015fim<\/strong>: A\u00e7\u0131lma\/t\u0131klama oran\u0131 genellikle daha y\u00fcksektir.<\/li>\n<li><strong>Kritik zamanlama<\/strong>: Gecikme m\u00fc\u015fteri deneyimini do\u011frudan bozar.<\/li>\n<li><strong>\u015eikayet tolerans\u0131 d\u00fc\u015f\u00fck<\/strong>: Teslim edilememesi i\u015f kayb\u0131na d\u00f6n\u00fc\u015febilir.<\/li>\n<\/ul>\n<h3>Pazarlama\/toplu e-posta (marketing\/bulk)<\/h3>\n<ul>\n<li><strong>Her zaman beklenen de\u011fil<\/strong>: Al\u0131c\u0131 ilgisini yitirmi\u015f olabilir.<\/li>\n<li><strong>Spam \u015fikayeti riski<\/strong>: Abonelik y\u00f6netimi zay\u0131fsa \u015fikayet artar.<\/li>\n<li><strong>Hacim dalgalan\u0131r<\/strong>: Kampanyalarda bir anda y\u00fcksek g\u00f6nderim olabilir.<\/li>\n<li><strong>\u0130tibar\u0131 zorlar<\/strong>: Negatif sinyaller (\u015fikayet, d\u00fc\u015f\u00fck etkile\u015fim) artabilir.<\/li>\n<\/ul>\n<p>Bu farklar nedeniyle, tek bir domain \u00fczerinden her \u015feyi g\u00f6ndermek baz\u0131 durumlarda i\u015flemsel e-postalar\u0131n da gereksiz risk almas\u0131na yol a\u00e7ar.<\/p>\n<h2>Subdomain ile ay\u0131rman\u0131n pratik faydalar\u0131<\/h2>\n<h3>1) \u0130tibar\u0131n b\u00f6l\u00fcmlenmesi<\/h3>\n<p>Al\u0131c\u0131 posta sistemleri, g\u00f6ndereni de\u011ferlendirirken alan ad\u0131 ve g\u00f6nderim davran\u0131\u015f\u0131 gibi sinyalleri kullan\u0131r. Pazarlama ak\u0131\u015f\u0131nda ya\u015fanan \u015fikayet art\u0131\u015f\u0131 veya liste kalitesi sorunlar\u0131, ayn\u0131 domain \u00fczerinden giden parola s\u0131f\u0131rlama e-postalar\u0131n\u0131n da spam\u2019e d\u00fc\u015fmesine katk\u0131da bulunabilir. Subdomain ayr\u0131m\u0131, bu etkinin yay\u0131lmas\u0131n\u0131 azaltmaya yard\u0131mc\u0131 olur.<\/p>\n<h3>2) DNS ve kimlik do\u011frulama y\u00f6netiminin netle\u015fmesi<\/h3>\n<p>SPF, DKIM ve DMARC kay\u0131tlar\u0131n\u0131 ayr\u0131 subdomain \u00fczerinde y\u00f6netmek, hangi sistemin ne g\u00f6nderdi\u011fini daha g\u00f6r\u00fcn\u00fcr k\u0131lar. \u00d6zellikle birden fazla ara\u00e7 veya departman e-posta g\u00f6nderiyorsa, \u201ckim, hangi kaynaktan, hangi kimlikle g\u00f6nderiyor?\u201d sorusu daha kolay cevaplan\u0131r.<\/p>\n<h3>3) Politika ve raporlama ayr\u0131m\u0131<\/h3>\n<p>DMARC politikas\u0131 teoride domain seviyesinde uygulan\u0131r. Subdomain kullan\u0131m\u0131, raporlar\u0131 farkl\u0131 ak\u0131\u015flar i\u00e7in ayr\u0131 ayr\u0131 incelemeyi kolayla\u015ft\u0131r\u0131r. \u00d6rne\u011fin pazarlama subdomain\u2019inde daha agresif bir politika, ana domaine g\u00f6re daha farkl\u0131 bir y\u00f6netim yakla\u015f\u0131m\u0131 gerektirebilir. Buradaki ama\u00e7 \u201cdaha sert olmak\u201d de\u011fil, risk profilini do\u011fru ayr\u0131\u015ft\u0131rmakt\u0131r.<\/p>\n<h3>4) Operasyonel hata etkisini azaltma<\/h3>\n<p>Bazen bir pazarlama arac\u0131 yanl\u0131\u015fl\u0131kla b\u00fcy\u00fck bir listeye hatal\u0131 i\u00e7erik g\u00f6nderir, bounce oran\u0131 y\u00fckselir veya spam \u015fikayeti artar. Subdomain ayr\u0131m\u0131, bu hatan\u0131n i\u015flemsel ak\u0131\u015fa s\u0131\u00e7ramas\u0131n\u0131 s\u0131n\u0131rlayabilir.<\/p>\n<h2>Hangi subdomain yap\u0131s\u0131 se\u00e7ilmeli?<\/h2>\n<p>Tek bir do\u011fru yoktur; ancak y\u00f6netimi kolay ve anla\u015f\u0131l\u0131r bir yap\u0131 se\u00e7mek \u00f6nemlidir. Yayg\u0131n yakla\u015f\u0131mlar:<\/p>\n<ul>\n<li><strong>Transactional i\u00e7in<\/strong>: notify.sirket.com, mail.sirket.com, tx.sirket.com<\/li>\n<li><strong>Marketing i\u00e7in<\/strong>: newsletter.sirket.com, bulten.sirket.com, promo.sirket.com<\/li>\n<li><strong>Uygulama bazl\u0131<\/strong>: app.sirket.com (uygulama bildirimleri), events.sirket.com (etkinlik postalar\u0131)<\/li>\n<\/ul>\n<p>\u0130simlendirmede ama\u00e7, hem IT ekibi hem pazarlama ekibi i\u00e7in neyin ne oldu\u011funu a\u00e7\u0131k etmektir. \u201cmail\u201d gibi genel ifadeler zaman i\u00e7inde kar\u0131\u015f\u0131kl\u0131k yaratabilir; m\u00fcmk\u00fcnse i\u015flevi belirten isimler tercih edilebilir.<\/p>\n<h2>DNS taraf\u0131nda neleri planlamal\u0131s\u0131n\u0131z?<\/h2>\n<h3>SPF: G\u00f6nderim kaynaklar\u0131n\u0131 net tan\u0131mlama<\/h3>\n<p>Her subdomain i\u00e7in SPF kayd\u0131 tasarlarken, o subdomain \u00fczerinden e-posta g\u00f6nderecek sistemleri listelemelisiniz. En s\u0131k yap\u0131lan hata, ayn\u0131 SPF kayd\u0131n\u0131 kopyalay\u0131p gereksiz kaynaklar\u0131 eklemek veya \u00e7ok fazla \u201cinclude\u201d kullan\u0131p DNS sorgu limitlerine yakla\u015fmakt\u0131r. Subdomain ayr\u0131m\u0131 burada avantaj sa\u011flar: pazarlama arac\u0131 sadece pazarlama subdomain SPF\u2019ine girer, i\u015flemsel sunucu sadece i\u015flemsel subdomain SPF\u2019inde kal\u0131r.<\/p>\n<h3>DKIM: \u0130mza alan\u0131n\u0131 do\u011fru kurgulama<\/h3>\n<p>DKIM, e-postalar\u0131n i\u00e7eri\u011fini ve baz\u0131 ba\u015fl\u0131klar\u0131n\u0131 kriptografik olarak imzalayarak al\u0131c\u0131ya \u201cbu mesaj bu domain ad\u0131na yetkili bir sistemden \u00e7\u0131kt\u0131\u201d sinyali verir. Subdomain stratejisinde kritik nokta, DKIM imzas\u0131ndaki domain\u2019in (d=) hangi alan ad\u0131yla e\u015fle\u015fti\u011fidir. Pazarlama e-postalar\u0131n\u0131n DKIM\u2019i pazarlama subdomain\u2019i ile, i\u015flemsel e-postalar\u0131n DKIM\u2019i i\u015flemsel subdomain\u2019i ile uyumlu olacak \u015fekilde ayarlanmal\u0131d\u0131r.<\/p>\n<h3>DMARC: Uyum (alignment) ve g\u00f6r\u00fcn\u00fcrl\u00fck<\/h3>\n<p>DMARC, SPF ve DKIM sonu\u00e7lar\u0131n\u0131 \u201cFrom\u201d alan\u0131ndaki domain ile ili\u015fkilendirerek kimlik sahtecili\u011fini azaltmay\u0131 hedefler. Subdomain yakla\u015f\u0131m\u0131nda, her ak\u0131\u015f\u0131n \u201cFrom\u201d domain\u2019ini tutarl\u0131 tutmak \u00f6nemlidir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>\u0130\u015flemsel: no-reply@notify.sirket.com<\/li>\n<li>Pazarlama: kampanya@newsletter.sirket.com<\/li>\n<\/ul>\n<p>Bu ayr\u0131m hem kullan\u0131c\u0131 taraf\u0131nda daha anla\u015f\u0131l\u0131r olabilir hem de DMARC raporlar\u0131nda kaynaklar\u0131 ay\u0131rman\u0131za yard\u0131mc\u0131 olur. Ancak a\u015f\u0131r\u0131 par\u00e7alama da y\u00f6netim y\u00fck\u00fc getirir; yaln\u0131zca ihtiya\u00e7 kadar subdomain a\u00e7mak daha s\u00fcrd\u00fcr\u00fclebilirdir.<\/p>\n<h2>From, Return-Path ve Reply-To: Kar\u0131\u015f\u0131kl\u0131\u011f\u0131 azalt\u0131n<\/h2>\n<p>E-posta ba\u015fl\u0131klar\u0131nda farkl\u0131 ama\u00e7lara hizmet eden alanlar vard\u0131r. S\u0131k kar\u015f\u0131la\u015f\u0131lan sorun, pazarlama arac\u0131n\u0131n \u201cReturn-Path\u201d alan\u0131n\u0131 farkl\u0131 bir domain\u2019e \u00e7ekmesi veya \u201cFrom\u201d ile DKIM\u2019in farkl\u0131 domain\u2019lerde kalmas\u0131d\u0131r. Subdomain stratejisi uygularken \u015fu hedefleri benimseyin:<\/p>\n<ul>\n<li><strong>Tutarl\u0131l\u0131k<\/strong>: \u201cFrom\u201d domain\u2019i hangi subdomain ise, DKIM ve SPF uyumu da buna g\u00f6re kurulmal\u0131.<\/li>\n<li><strong>Yan\u0131t y\u00f6netimi<\/strong>: Yan\u0131tlar\u0131n nereye gidece\u011fi (Reply-To) net olmal\u0131; \u201cno-reply\u201d kullan\u0131l\u0131yorsa destek kanal\u0131 ayr\u0131ca belirtilmeli.<\/li>\n<li><strong>Marka okunabilirli\u011fi<\/strong>: Kullan\u0131c\u0131lar\u0131n tan\u0131yaca\u011f\u0131, g\u00fcven duyaca\u011f\u0131 bir g\u00f6nderici ad\u0131 ve adres format\u0131 se\u00e7ilmeli.<\/li>\n<\/ul>\n<h2>Ge\u00e7i\u015f plan\u0131: Mevcut d\u00fczenden subdomain ayr\u0131m\u0131na ad\u0131m ad\u0131m<\/h2>\n<ol>\n<li><strong>Ak\u0131\u015f envanteri \u00e7\u0131kar\u0131n<\/strong>: Hangi sistem hangi e-postalar\u0131 g\u00f6nderiyor? Hacimler ve kritik ak\u0131\u015flar neler?<\/li>\n<li><strong>Yeni \u201cFrom\u201d adreslerini tasarlay\u0131n<\/strong>: Transactional ve marketing i\u00e7in net adres \u015fablonlar\u0131 olu\u015fturun.<\/li>\n<li><strong>DNS kay\u0131tlar\u0131n\u0131 haz\u0131rlay\u0131n<\/strong>: Subdomain baz\u0131nda SPF\/DKIM\/DMARC kurgusunu planlay\u0131n.<\/li>\n<li><strong>Kademeli ge\u00e7i\u015f yap\u0131n<\/strong>: \u00d6nce d\u00fc\u015f\u00fck riskli bir ak\u0131\u015f\u0131 yeni subdomain\u2019e al\u0131n, sonu\u00e7lar\u0131 izleyin.<\/li>\n<li><strong>\u0130zleme ve geri bildirim<\/strong>: Bounce, \u015fikayet ve teslimat sorunlar\u0131n\u0131 takip edin; gerekirse i\u00e7erik ve liste hijyenini iyile\u015ftirin.<\/li>\n<li><strong>Dok\u00fcmantasyon<\/strong>: Hangi subdomain ne i\u00e7in kullan\u0131l\u0131yor, kim sorumlu, de\u011fi\u015fiklik s\u00fcreci nas\u0131l i\u015fleyecek yaz\u0131l\u0131 hale getirin.<\/li>\n<\/ol>\n<p>Burada ama\u00e7, \u201cbir gecede her \u015feyi de\u011fi\u015ftirmek\u201d de\u011fil, kontroll\u00fc \u015fekilde yeni yap\u0131y\u0131 oturtmakt\u0131r.<\/p>\n<h2>Yayg\u0131n hatalar ve ka\u00e7\u0131nma yollar\u0131<\/h2>\n<h3>Tek bir subdomain\u2019e her \u015feyi y\u0131\u011fmak<\/h3>\n<p>\u201cmail.sirket.com\u201d alt\u0131nda hem pazarlama hem i\u015flemsel postalar\u0131 toplamak, ayr\u0131m\u0131n faydas\u0131n\u0131 azalt\u0131r. En az\u0131ndan iki ana ak\u0131\u015f\u0131 ay\u0131rmak genellikle daha iyi sonu\u00e7 verir.<\/p>\n<h3>Liste hijyenini subdomain ile \u00e7\u00f6zmeye \u00e7al\u0131\u015fmak<\/h3>\n<p>Subdomain, k\u00f6t\u00fc liste kalitesini \u201csihirli\u201d \u015fekilde d\u00fczeltmez. \u015eikayet oran\u0131, spam tuzaklar\u0131, izinli pazarlama gibi konular ayr\u0131 disiplinlerdir. Subdomain sadece risk y\u00f6netimini ve analiz kabiliyetini iyile\u015ftirir.<\/p>\n<h3>SPF\u2019i gereksiz b\u00fcy\u00fctmek<\/h3>\n<p>Her ihtimale kar\u015f\u0131 her sistemi her SPF\u2019e eklemek, y\u00f6netimi karma\u015f\u0131kla\u015ft\u0131r\u0131r ve teknik limit riskini art\u0131r\u0131r. Her subdomain SPF\u2019inde yaln\u0131zca ger\u00e7ekten o subdomain\u2019den g\u00f6nderen kaynaklar olmal\u0131.<\/p>\n<h2>Son kontrol listesi<\/h2>\n<ul>\n<li><strong>\u0130\u015flemsel ve pazarlama ak\u0131\u015flar\u0131 ayr\u0131ld\u0131 m\u0131?<\/strong><\/li>\n<li><strong>Her subdomain i\u00e7in SPF\/DKIM\/DMARC tutarl\u0131 m\u0131?<\/strong><\/li>\n<li><strong>From adresleri kullan\u0131c\u0131 a\u00e7\u0131s\u0131ndan anla\u015f\u0131l\u0131r m\u0131?<\/strong><\/li>\n<li><strong>Yan\u0131t (Reply-To) ve destek s\u00fcre\u00e7leri net mi?<\/strong><\/li>\n<li><strong>De\u011fi\u015fiklikler dok\u00fcmante edildi mi?<\/strong><\/li>\n<\/ul>\n<h2>Sonu\u00e7: Daha y\u00f6netilebilir bir e-posta mimarisi<\/h2>\n<p>Subdomain stratejisi, i\u015fletmelerin e-posta altyap\u0131s\u0131n\u0131 b\u00fcy\u00fcrken daha kontroll\u00fc y\u00f6netmesine yard\u0131mc\u0131 olan pratik bir yakla\u015f\u0131md\u0131r. \u0130\u015flemsel e-postalar\u0131n g\u00fcvenilirli\u011fini korurken pazarlama g\u00f6nderimlerinde gerekli optimizasyonlar\u0131 ayr\u0131 bir alanda yapmak, hem teknik ekiplerin hem de i\u015f ekiplerinin i\u015fini kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>E\u011fer kurumsal e-posta altyap\u0131n\u0131z\u0131 sade ve y\u00f6netilebilir bir \u015fekilde i\u015fletmek istiyorsan\u0131z, MX1Mail \u00fczerinde domain ve DNS d\u00fczeninizi planlarken i\u015flemsel ve pazarlama ak\u0131\u015flar\u0131n\u0131 ba\u015ftan ayr\u0131 kurgulamak, ileride olu\u015fabilecek teslimat ve y\u00f6netim karma\u015fas\u0131n\u0131 azaltman\u0131za yard\u0131mc\u0131 olabilir.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u0130\u015flemsel ve pazarlama e-postalar\u0131n\u0131 subdomain ile ay\u0131rarak teslim edilebilirli\u011fi, itibar y\u00f6netimini ve kimlik do\u011frulamay\u0131 (SPF\/DKIM\/DMARC) nas\u0131l daha kontroll\u00fc hale getirece\u011finizi \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":[291],"tags":[104,109,94],"class_list":["post-123","post","type-post","status-publish","format-standard","hentry","category-e-posta-teslim-edilebilirligi","tag-dkim","tag-dmarc","tag-dns"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/123","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=123"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/123\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=123"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=123"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}