{"id":3659,"date":"2025-12-29T17:28:09","date_gmt":"2025-12-29T14:28:09","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/"},"modified":"2025-12-29T17:28:09","modified_gmt":"2025-12-29T14:28:09","slug":"dedicated-ip-isitma-ve-e-posta-itibari-yonetimi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/","title":{"rendered":"Dedicated IP Is\u0131tma ve E-Posta \u0130tibar\u0131 Y\u00f6netimi"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Dedicated_IP_Isitma_ve_E-Posta_Itibari_Neden_Bu_Kadar_Kritik\"><span class=\"toc_number toc_depth_1\">1<\/span> Dedicated IP Is\u0131tma ve E-Posta \u0130tibar\u0131 Neden Bu Kadar Kritik?<\/a><\/li><li><a href=\"#Dedicated_IP_Shared_IP_ve_Itibar_Mantigi\"><span class=\"toc_number toc_depth_1\">2<\/span> Dedicated IP, Shared IP ve \u0130tibar Mant\u0131\u011f\u0131<\/a><\/li><li><a href=\"#Ne_Zaman_Dedicated_IP_Isitmaya_Ihtiyaciniz_Var\"><span class=\"toc_number toc_depth_1\">3<\/span> Ne Zaman Dedicated IP Is\u0131tmaya \u0130htiyac\u0131n\u0131z Var?<\/a><\/li><li><a href=\"#Isinmamis_Dedicated_IP_ile_Gonderim_Yapmanin_Riskleri\"><span class=\"toc_number toc_depth_1\">4<\/span> Is\u0131nmam\u0131\u015f Dedicated IP ile G\u00f6nderim Yapman\u0131n Riskleri<\/a><\/li><li><a href=\"#Isitma_Oncesi_Zorunlu_Teknik_Hazirlik_DNS_ve_Sunucu_Ayarlari\"><span class=\"toc_number toc_depth_1\">5<\/span> Is\u0131tma \u00d6ncesi Zorunlu Teknik Haz\u0131rl\u0131k: DNS ve Sunucu Ayarlar\u0131<\/a><ul><li><a href=\"#SPF_DKIM_ve_DMARC_Kaynaklari\"><span class=\"toc_number toc_depth_2\">5.1<\/span> SPF, DKIM ve DMARC Kaynaklar\u0131<\/a><\/li><li><a href=\"#PTR_Reverse_DNS_ve_HELOEHLO_Uyumu\"><span class=\"toc_number toc_depth_2\">5.2<\/span> PTR (Reverse DNS) ve HELO\/EHLO Uyumu<\/a><\/li><li><a href=\"#Gonderim_Alan_Adi_Stratejisi\"><span class=\"toc_number toc_depth_2\">5.3<\/span> G\u00f6nderim Alan Ad\u0131 Stratejisi<\/a><\/li><li><a href=\"#Guvenli_SMTP_MTA-STS_TLS-RPT_DANE\"><span class=\"toc_number toc_depth_2\">5.4<\/span> G\u00fcvenli SMTP: MTA-STS, TLS-RPT, DANE<\/a><\/li><\/ul><\/li><li><a href=\"#Dedicated_IP_Isitma_Stratejisi_Genel_Prensipler\"><span class=\"toc_number toc_depth_1\">6<\/span> Dedicated IP Is\u0131tma Stratejisi: Genel Prensipler<\/a><ul><li><a href=\"#Ornek_4_Haftalik_Dedicated_IP_Isitma_Plani\"><span class=\"toc_number toc_depth_2\">6.1<\/span> \u00d6rnek 4 Haftal\u0131k Dedicated IP Is\u0131tma Plan\u0131<\/a><\/li><li><a href=\"#Transactional_Maillere_Ozel_Isitma_Taktikleri\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Transactional Maillere \u00d6zel Is\u0131tma Taktikleri<\/a><\/li><li><a href=\"#Kuyruk_Retry_ve_SMTP_Hatalarini_Dogru_Yorumlamak\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Kuyruk, Retry ve SMTP Hatalar\u0131n\u0131 Do\u011fru Yorumlamak<\/a><\/li><\/ul><\/li><li><a href=\"#E-Posta_Itibari_Yonetimi_Surekli_Takip_Gerektiren_Bir_Surec\"><span class=\"toc_number toc_depth_1\">7<\/span> E-Posta \u0130tibar\u0131 Y\u00f6netimi: S\u00fcrekli Takip Gerektiren Bir S\u00fcre\u00e7<\/a><ul><li><a href=\"#DMARC_Raporlari_Postmaster_Araclari_ve_Log_Analizi\"><span class=\"toc_number toc_depth_2\">7.1<\/span> DMARC Raporlar\u0131, Postmaster Ara\u00e7lar\u0131 ve Log Analizi<\/a><\/li><li><a href=\"#Icerik_Siklik_ve_Liste_Hijyeni\"><span class=\"toc_number toc_depth_2\">7.2<\/span> \u0130\u00e7erik, S\u0131kl\u0131k ve Liste Hijyeni<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Altyapisinda_Dedicated_IP_Isitma_Icin_Onerilen_Mimariler\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost Altyap\u0131s\u0131nda Dedicated IP Is\u0131tma \u0130\u00e7in \u00d6nerilen Mimariler<\/a><ul><li><a href=\"#1_Uygulama_Sunucusuyla_Ayni_VPS_Uzerinde_MTA\"><span class=\"toc_number toc_depth_2\">8.1<\/span> 1) Uygulama Sunucusuyla Ayn\u0131 VPS \u00dczerinde MTA<\/a><\/li><li><a href=\"#2_Ayri_VPS_Uzerinde_Ozel_Mail_Sunucusu\"><span class=\"toc_number toc_depth_2\">8.2<\/span> 2) Ayr\u0131 VPS \u00dczerinde \u00d6zel Mail Sunucusu<\/a><\/li><li><a href=\"#3_Yuksek_Trafikli_WooCommerce_SaaS_icin_Gelismis_Transactional_Altyapi\"><span class=\"toc_number toc_depth_2\">8.3<\/span> 3) Y\u00fcksek Trafikli WooCommerce \/ SaaS i\u00e7in Geli\u015fmi\u015f Transactional Altyap\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Ornek_Senaryo_E-Ticaret_Sitesi_Icin_Transactional_IP_Warmup_Plani\"><span class=\"toc_number toc_depth_1\">9<\/span> \u00d6rnek Senaryo: E-Ticaret Sitesi \u0130\u00e7in Transactional IP Warmup Plan\u0131<\/a><\/li><li><a href=\"#Sik_Yapilan_Hatalar_ve_Kurtarma_Adimlari\"><span class=\"toc_number toc_depth_1\">10<\/span> S\u0131k Yap\u0131lan Hatalar ve Kurtarma Ad\u0131mlar\u0131<\/a><\/li><li><a href=\"#Sonuc_Transactional_Mailleriniz_Icin_Saglam_Bir_Temel_Kurun\"><span class=\"toc_number toc_depth_1\">11<\/span> Sonu\u00e7: Transactional Mailleriniz \u0130\u00e7in Sa\u011flam Bir Temel Kurun<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Dedicated_IP_Isitma_ve_E-Posta_Itibari_Neden_Bu_Kadar_Kritik\">Dedicated IP Is\u0131tma ve E-Posta \u0130tibar\u0131 Neden Bu Kadar Kritik?<\/span><\/h2>\n<p>Transactional e-postalar; \u015fifre s\u0131f\u0131rlama, sipari\u015f onay\u0131, fatura, g\u00fcvenlik uyar\u0131s\u0131 gibi i\u015finizin kalbinde duran bildirimlerdir. Bu mailler zaman\u0131nda ve g\u00fcvenle gitmezse, sadece kullan\u0131c\u0131 deneyimi bozulmaz; destek maliyetiniz artar, iade oranlar\u0131n\u0131z y\u00fckselir, hatta gelir kayb\u0131 ya\u015fars\u0131n\u0131z. Bu noktada <strong>dedicated IP \u0131s\u0131tma<\/strong> ve e-posta itibar\u0131 y\u00f6netimi, \u00f6zellikle kendi SMTP altyap\u0131s\u0131n\u0131 kuran ekipler i\u00e7in kritik hale geliyor.<\/p>\n<p>Yeni ald\u0131\u011f\u0131n\u0131z bir <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>ya MTA (Postfix, Exim vb.) kurup transactional e-posta g\u00f6ndermeye ba\u015flad\u0131\u011f\u0131n\u0131zda, IP\u2019niz al\u0131c\u0131 servisler i\u00e7in tamamen \u201cbilinmeyen\u201d durumdad\u0131r. Bir anda y\u00fcksek hacimde e-posta g\u00f6nderirseniz, Gmail, Outlook ve di\u011fer sa\u011flay\u0131c\u0131lar bu IP\u2019yi agresif \u015fekilde s\u0131n\u0131rlar, greylist uygular veya do\u011frudan spam klas\u00f6r\u00fcne atar. Bu sadece IP itibar\u0131n\u0131 de\u011fil, ayn\u0131 zamanda alan ad\u0131n\u0131z\u0131n itibar\u0131n\u0131 da zedeler.<\/p>\n<p>DCHost olarak sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en b\u00fcy\u00fck sorunlardan biri, gayet temiz yaz\u0131lm\u0131\u015f SPF\/DKIM\/DMARC kay\u0131tlar\u0131na sahip projelerin, <strong>IP \u0131s\u0131nma s\u00fcreci d\u00fczg\u00fcn y\u00f6netilmedi\u011fi i\u00e7in<\/strong> teslim edilebilirlikte duvara \u00e7arpmas\u0131. Bu rehberde, tamamen pratik bir bak\u0131\u015f a\u00e7\u0131s\u0131yla, dedicated IP \u0131s\u0131s\u0131n\u0131 g\u00fcvenle nas\u0131l y\u00fckseltece\u011finizi ve transactional e-posta itibar\u0131n\u0131z\u0131 nas\u0131l koruyaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m anlataca\u011f\u0131z.<\/p>\n<h2><span id=\"Dedicated_IP_Shared_IP_ve_Itibar_Mantigi\">Dedicated IP, Shared IP ve \u0130tibar Mant\u0131\u011f\u0131<\/span><\/h2>\n<p>\u00d6nce temel kavramlar\u0131 netle\u015ftirelim. E-posta g\u00f6nderiminde iki ana itibar katman\u0131 vard\u0131r:<\/p>\n<ul>\n<li><strong>IP itibar\u0131n\u0131z<\/strong> (IP reputation)<\/li>\n<li><strong>Alan ad\u0131 itibar\u0131n\u0131z<\/strong> (domain reputation)<\/li>\n<\/ul>\n<p>Payla\u015f\u0131ml\u0131 hosting veya kimi e-posta servislerinde, IP\u2019yi ba\u015fka g\u00f6ndericilerle ortak kullan\u0131rs\u0131n\u0131z (shared IP). Oradaki di\u011fer m\u00fc\u015fteriler spam g\u00f6nderiyorsa, siz de bundan etkilenirsiniz. Kendi VPS veya dedicated sunucunuzda ise genellikle <strong>dedicated IP<\/strong> (size \u00f6zel IP) ile \u00e7al\u0131\u015f\u0131rs\u0131n\u0131z; yani t\u00fcm itibar do\u011frudan sizin g\u00f6nderim davran\u0131\u015f\u0131n\u0131za ba\u011fl\u0131d\u0131r.<\/p>\n<p>Dedicated IP\u2019nin avantajlar\u0131:<\/p>\n<ul>\n<li>\u0130yi bir g\u00f6nderim davran\u0131\u015f\u0131 ile <strong>\u00e7ok g\u00fc\u00e7l\u00fc bir itibar<\/strong> in\u015fa etme imk\u00e2n\u0131<\/li>\n<li>Ba\u015fkas\u0131n\u0131n hatas\u0131ndan etkilenmeme<\/li>\n<li>Hacmi, h\u0131z limitlerini ve kuyruk davran\u0131\u015f\u0131n\u0131 tamamen kontrol edebilme<\/li>\n<\/ul>\n<p>Dezavantaj\u0131 ise \u015fu: <strong>Is\u0131nmam\u0131\u015f bir dedicated IP, hi\u00e7bir ge\u00e7mi\u015fi olmad\u0131\u011f\u0131 i\u00e7in s\u0131f\u0131r g\u00fcvenle ba\u015flar<\/strong>. \u0130\u015fte bu y\u00fczden, so\u011fuk bir IP\u2019yi yava\u015f yava\u015f ve kontroll\u00fc \u015fekilde \u201c\u0131s\u0131nd\u0131rman\u0131z\u201d gerekir.<\/p>\n<h2><span id=\"Ne_Zaman_Dedicated_IP_Isitmaya_Ihtiyaciniz_Var\">Ne Zaman Dedicated IP Is\u0131tmaya \u0130htiyac\u0131n\u0131z Var?<\/span><\/h2>\n<p>IP \u0131s\u0131nma sadece \u201cyeni sunucu kurarken\u201d yap\u0131lacak bir \u015fey de\u011fil. DCHost taraf\u0131nda en \u00e7ok kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z senaryolar \u015f\u00f6yle:<\/p>\n<ul>\n<li><strong>Yeni VPS veya dedicated sunucu a\u00e7t\u0131n\u0131z<\/strong> ve kendi MTA\u2019n\u0131z\u0131 kurdunuz.<\/li>\n<li><strong>Mevcut e-posta altyap\u0131n\u0131z\u0131 yeni bir IP blokuna ta\u015f\u0131d\u0131n\u0131z<\/strong> (\u00f6rne\u011fin IP fiyatlar\u0131 veya lokasyon stratejisi nedeniyle).<\/li>\n<li><strong>Blacklist\u2019ten \u00e7\u0131kt\u0131n\u0131z<\/strong> ve itibar\u0131n\u0131z\u0131 tekrar in\u015fa etmeniz gerekiyor.<\/li>\n<li><strong>Transactional ve pazarlama maillerini ay\u0131rd\u0131n\u0131z<\/strong> ve transactional taraf i\u00e7in yeni bir dedicated IP devreye ald\u0131n\u0131z.<\/li>\n<li><strong>Yedek\/DR (disaster recovery) i\u00e7in ikinci bir MTA\/IP haz\u0131rlad\u0131n\u0131z<\/strong> ve bu IP\u2019nin de \u201cso\u011fuk\u201d kalmamas\u0131n\u0131 istiyorsunuz.<\/li>\n<\/ul>\n<p>Bu durumlar\u0131n hepsinde, IP \u0131s\u0131nma plan\u0131 yapmadan \u00fcretime ge\u00e7erseniz, \u00f6zellikle transactional e-postalarda anl\u0131k kesintiler, gecikmeler ve spam klas\u00f6r\u00fc problemleri ya\u015fama ihtimaliniz \u00e7ok y\u00fcksektir.<\/p>\n<h2><span id=\"Isinmamis_Dedicated_IP_ile_Gonderim_Yapmanin_Riskleri\">Is\u0131nmam\u0131\u015f Dedicated IP ile G\u00f6nderim Yapman\u0131n Riskleri<\/span><\/h2>\n<p>So\u011fuk bir IP ile bir anda binlerce mail patlatman\u0131n sonu\u00e7lar\u0131n\u0131, operasyonel tarafta \u00e7ok kez g\u00f6zlemledik:<\/p>\n<ul>\n<li><strong>Yo\u011fun gecikme (deferral)<\/strong>: 4xx hata kodlar\u0131yla \u201csonra dene\u201d yan\u0131tlar\u0131, artan kuyruklar.<\/li>\n<li><strong>Hard bounce art\u0131\u015f\u0131<\/strong>: \u00d6zellikle eski listelerdeki ge\u00e7ersiz adresler, IP itibar\u0131n\u0131 h\u0131zla a\u015fa\u011f\u0131 \u00e7eker.<\/li>\n<li><strong>Spam klas\u00f6r\u00fcne d\u00fc\u015fme<\/strong>: Kullan\u0131c\u0131lar mailinizi g\u00f6rse bile spam klas\u00f6r\u00fcnden \u00e7\u0131karmad\u0131\u011f\u0131 s\u00fcrece etkile\u015fim alamazs\u0131n\u0131z.<\/li>\n<li><strong>Oran s\u0131n\u0131rlama (rate limit)<\/strong>: Baz\u0131 sa\u011flay\u0131c\u0131lar IP ba\u015f\u0131na dakika\/saat limitlerini \u00e7ok agresif uygular.<\/li>\n<li><strong>Domain itibar\u0131n\u0131n da bozulmas\u0131<\/strong>: Ayn\u0131 alan ad\u0131ndan web veya ba\u015fka IP\u2019ler \u00fczerinden g\u00f6nderilen mailler de olumsuz etkilenebilir.<\/li>\n<\/ul>\n<p>\u00d6zetle: Is\u0131tma yapmazsan\u0131z, sadece IP\u2019yi riske atmazs\u0131n\u0131z; markan\u0131z\u0131n alan ad\u0131 da uzun vadede \u201c\u015f\u00fcpheli g\u00f6nderici\u201d damgas\u0131 yiyebilir. Bu da ba\u015fka IP\u2019ye ge\u00e7seniz bile sorunlar\u0131n pe\u015finizi b\u0131rakmamas\u0131 demektir.<\/p>\n<h2><span id=\"Isitma_Oncesi_Zorunlu_Teknik_Hazirlik_DNS_ve_Sunucu_Ayarlari\">Is\u0131tma \u00d6ncesi Zorunlu Teknik Haz\u0131rl\u0131k: DNS ve Sunucu Ayarlar\u0131<\/span><\/h2>\n<p>IP \u0131s\u0131tma, sadece g\u00f6nderim hacmini yava\u015f yava\u015f art\u0131rmak de\u011fildir. Is\u0131nma \u00f6ncesinde <strong>temel kimlik do\u011frulama ve g\u00fcvenlik ayarlar\u0131n\u0131n eksiksiz olmas\u0131<\/strong> \u015fart. Aksi halde altyap\u0131 sorunlar\u0131, itibar in\u015fas\u0131n\u0131 daha ba\u015ftan baltalar.<\/p>\n<h3><span id=\"SPF_DKIM_ve_DMARC_Kaynaklari\">SPF, DKIM ve DMARC Kaynaklar\u0131<\/span><\/h3>\n<p>IP \u0131s\u0131nmaya ba\u015flamadan \u00f6nce \u015fu \u00fc\u00e7 kayd\u0131n d\u00fczg\u00fcn tan\u0131mlanm\u0131\u015f olmas\u0131 gerekir:<\/p>\n<ul>\n<li><strong>SPF<\/strong>: Hangi IP\u2019lerin alan ad\u0131n\u0131z ad\u0131na mail g\u00f6ndermeye yetkili oldu\u011funu s\u00f6yler.<\/li>\n<li><strong>DKIM<\/strong>: G\u00f6nderdi\u011finiz mailleri kriptografik olarak imzalayarak i\u00e7eri\u011fin de\u011fi\u015fmedi\u011fini ispatlar.<\/li>\n<li><strong>DMARC<\/strong>: SPF\/DKIM sonu\u00e7lar\u0131na g\u00f6re al\u0131c\u0131n\u0131n ne yapmas\u0131 gerekti\u011fini (kabul, karantina, reddet) tarif eder.<\/li>\n<\/ul>\n<p>Bu kay\u0131tlar\u0131 daha \u00f6nce kurmad\u0131ysan\u0131z, ad\u0131m ad\u0131m ekran g\u00f6r\u00fcnt\u00fcl\u00fc anlat\u0131m i\u00e7in <a href='https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/'>SPF, DKIM ve DMARC do\u011frulama rehberimizi<\/a> mutlaka inceleyin. IP \u0131s\u0131nma s\u00fcrecinde DMARC raporlar\u0131, hangi sa\u011flay\u0131c\u0131larda sorun ya\u015fad\u0131\u011f\u0131n\u0131z\u0131 okumak i\u00e7in alt\u0131n de\u011ferinde olacakt\u0131r.<\/p>\n<h3><span id=\"PTR_Reverse_DNS_ve_HELOEHLO_Uyumu\">PTR (Reverse DNS) ve HELO\/EHLO Uyumu<\/span><\/h3>\n<p>Bir\u00e7ok al\u0131c\u0131, IP\u2019nizin PTR kayd\u0131na ve SMTP oturumunda verdi\u011finiz HELO\/EHLO ismine bakar. Bu ikisinin <strong>tutarl\u0131<\/strong> olmas\u0131 \u00f6nemlidir.<\/p>\n<ul>\n<li>PTR (rDNS) kayd\u0131: <code>ip-1-2-3-4.mail.sizinalanadiniz.com<\/code> gibi anlaml\u0131 bir hostname olsun.<\/li>\n<li>MTA\u2019n\u0131z\u0131n HELO\/EHLO ismi, bu PTR ile uyu\u015fsun.<\/li>\n<\/ul>\n<p>Reverse DNS\u2019in e-posta teslimat\u0131na etkisini detayl\u0131 g\u00f6rmek isterseniz, <a href='https:\/\/www.dchost.com\/blog\/ptr-reverse-dns-kaydi-vps-ipniz-icin-dogru-ayar-ve-e-posta-teslimine-etkisi\/'>PTR (Reverse DNS) kayd\u0131 rehberimiz<\/a> bu konuyu teknik a\u00e7\u0131dan derinlemesine ele al\u0131yor.<\/p>\n<h3><span id=\"Gonderim_Alan_Adi_Stratejisi\">G\u00f6nderim Alan Ad\u0131 Stratejisi<\/span><\/h3>\n<p>Transactional ve pazarlama e-postalar\u0131n\u0131 farkl\u0131 alan adlar\u0131 veya alt alan adlar\u0131 \u00fczerinden g\u00f6ndermek, itibar y\u00f6netimini ciddi \u015fekilde kolayla\u015ft\u0131r\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Web sitesi: <code>www.sizinmarka.com<\/code><\/li>\n<li>Transactional e-posta: <code>mail.sizinmarka.com<\/code> veya <code>notify.sizinmarka.com<\/code><\/li>\n<li>Pazarlama\/duyuru: <code>news.sizinmarka.com<\/code><\/li>\n<\/ul>\n<p>Bu stratejiyi nas\u0131l kurgulayaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m anlatan ayr\u0131 bir yaz\u0131m\u0131z var: <a href='https:\/\/www.dchost.com\/blog\/e-posta-icin-ayri-gonderim-alan-adi-kullanmak-transactional-ve-pazarlama-e-postalari-icin-dogru-domain-ve-dns-stratejisi\/'>e-posta i\u00e7in ayr\u0131 g\u00f6nderim alan ad\u0131 kullanma rehberi<\/a>. Dedicated IP \u0131s\u0131nmadan \u00f6nce bu plan\u0131 netle\u015ftirmek, ileride ya\u015fanacak krizleri \u00f6nl\u00fcyor.<\/p>\n<h3><span id=\"Guvenli_SMTP_MTA-STS_TLS-RPT_DANE\">G\u00fcvenli SMTP: MTA-STS, TLS-RPT, DANE<\/span><\/h3>\n<p>IP \u0131s\u0131nma do\u011frudan bu protokollere ba\u011fl\u0131 olmasa da, uzun vadede <strong>teslim edilebilirlik ve g\u00fcven<\/strong> i\u00e7in \u00f6nemlidir:<\/p>\n<ul>\n<li><strong>MTA-STS<\/strong>: Kar\u015f\u0131 taraf\u0131n sunucusuna m\u00fcmk\u00fcnse TLS ile ba\u011flan\u0131lmas\u0131n\u0131 zorunlu k\u0131lar.<\/li>\n<li><strong>TLS-RPT<\/strong>: TLS sorunlar\u0131 i\u00e7in rapor alman\u0131z\u0131 sa\u011flar.<\/li>\n<li><strong>DANE\/TLSA<\/strong>: DNSSEC ile birlikte \u00e7al\u0131\u015farak SMTP taraf\u0131nda ek sertifika do\u011frulamas\u0131 sunar.<\/li>\n<\/ul>\n<p>Bu teknolojilerin tamam\u0131n\u0131 \u00f6rnek kay\u0131tlarla anlatt\u0131\u011f\u0131m\u0131z <a href='https:\/\/www.dchost.com\/blog\/e%e2%80%91postada-mta%e2%80%91sts-tls%e2%80%91rpt-ve-dane-teslim-edilebilirligi-nasil-tatli-tatli-yukseltirsin\/'>MTA-STS, TLS-RPT ve DANE rehberimizi<\/a> de IP \u0131s\u0131nma \u00f6ncesi yap\u0131lacaklar listenize eklemenizi \u00f6neririz.<\/p>\n<h2><span id=\"Dedicated_IP_Isitma_Stratejisi_Genel_Prensipler\">Dedicated IP Is\u0131tma Stratejisi: Genel Prensipler<\/span><\/h2>\n<p>Art\u0131k altyap\u0131n\u0131z haz\u0131r. S\u0131rada en kritik k\u0131s\u0131m var: <strong>hacmi yava\u015f ve kontroll\u00fc bi\u00e7imde art\u0131rmak<\/strong>. IP \u0131s\u0131nman\u0131n temel prensipleri \u015f\u00f6yle \u00f6zetlenebilir:<\/p>\n<ul>\n<li>\u00d6nce <strong>en aktif ve etkile\u015fimi y\u00fcksek kullan\u0131c\u0131lar\u0131n\u0131za<\/strong> g\u00f6nderin.<\/li>\n<li>Hacmi her g\u00fcn\/hafta belli oranda, <strong>kademeli<\/strong> art\u0131r\u0131n.<\/li>\n<li>Bounce ve \u015fik\u00e2yet oranlar\u0131n\u0131 yak\u0131ndan izleyin; k\u00f6t\u00fc sinyal gelirse art\u0131\u015f\u0131 yava\u015flat\u0131n.<\/li>\n<li>Transactional mailleri, pazarlama maillerinden m\u00fcmk\u00fcn oldu\u011funca <strong>ayr\u0131 tutun<\/strong>.<\/li>\n<\/ul>\n<h3><span id=\"Ornek_4_Haftalik_Dedicated_IP_Isitma_Plani\">\u00d6rnek 4 Haftal\u0131k Dedicated IP Is\u0131tma Plan\u0131<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki tablo, g\u00fcnde ortalama 20\u201330 bin transactional e-posta g\u00f6nderen bir sistem i\u00e7in <strong>\u00f6rnek<\/strong> bir \u0131s\u0131nma plan\u0131d\u0131r. Rakamlar\u0131 kendi hacminize g\u00f6re \u00f6l\u00e7ekleyebilirsiniz.<\/p>\n<table border='1' cellpadding='6' cellspacing='0'>\n<thead>\n<tr>\n<th>G\u00fcn \/ Hafta<\/th>\n<th>G\u00fcnl\u00fck Maks. Mail<\/th>\n<th>Hedef Kitle<\/th>\n<th>Not<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1\u20132. g\u00fcn<\/td>\n<td>50\u2013100<\/td>\n<td>Son 7 g\u00fcnde a\u00e7\u0131l\u0131\u015f yapan kullan\u0131c\u0131lar<\/td>\n<td>En s\u0131cak liste, sadece transactional (\u015fifre, sipari\u015f)<\/td>\n<\/tr>\n<tr>\n<td>3\u20135. g\u00fcn<\/td>\n<td>200\u2013400<\/td>\n<td>Son 14 g\u00fcnde etkile\u015fim alanlar<\/td>\n<td>Hacmi yava\u015f\u00e7a ikiye katlay\u0131n, bounce oran\u0131n\u0131 izleyin<\/td>\n<\/tr>\n<tr>\n<td>6\u20137. g\u00fcn<\/td>\n<td>800\u20131.000<\/td>\n<td>Son 30 g\u00fcn aktif kullan\u0131c\u0131lar<\/td>\n<td>Farkl\u0131 sa\u011flay\u0131c\u0131lardaki (Gmail, Outlook vb.) ba\u015far\u0131 oranlar\u0131n\u0131 ayr\u0131 takip edin<\/td>\n<\/tr>\n<tr>\n<td>2. hafta<\/td>\n<td>2.000\u20135.000<\/td>\n<td>Genel aktif m\u00fc\u015fteri kitlesi<\/td>\n<td>Transactional\u2019lar\u0131 tamamen yeni IP\u2019ye kayd\u0131rmaya yakla\u015f\u0131n<\/td>\n<\/tr>\n<tr>\n<td>3. hafta<\/td>\n<td>10.000\u201315.000<\/td>\n<td>T\u00fcm transactional trafi\u011fin b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc<\/td>\n<td>G\u00fcnl\u00fck hacmi lineer art\u0131r\u0131n, spam \u015fik\u00e2yet oran\u0131n\u0131 kontrol edin<\/td>\n<\/tr>\n<tr>\n<td>4. hafta<\/td>\n<td>Hedef \u00fcretim hacmi<\/td>\n<td>T\u00fcm transactional trafik<\/td>\n<td>Art\u0131k IP b\u00fcy\u00fck oranda \u0131s\u0131nm\u0131\u015f olmal\u0131; yine de log ve rapor takibi \u015fart<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu plan, \u201cbir g\u00fcnde biten\u201d bir s\u00fcre\u00e7 de\u011fil. \u00d6zellikle b\u00fcy\u00fck hacimli g\u00f6nderimlerde 4\u20136 haftal\u0131k bir zaman dilimini g\u00f6ze almak gerekiyor.<\/p>\n<h3><span id=\"Transactional_Maillere_Ozel_Isitma_Taktikleri\">Transactional Maillere \u00d6zel Is\u0131tma Taktikleri<\/span><\/h3>\n<p>Transactional maillerin en b\u00fcy\u00fck avantaj\u0131, <strong>y\u00fcksek etkile\u015fim oranlar\u0131d\u0131r<\/strong>. Kullan\u0131c\u0131lar bu mailleri a\u00e7ar, i\u00e7indeki linklere t\u0131klar, hatta ar\u015fivler. Bu, IP itibar\u0131n\u0131 in\u015fa etmek i\u00e7in m\u00fckemmel bir sinyaldir. Pratik \u00f6neriler:<\/p>\n<ul>\n<li>IP \u0131s\u0131nman\u0131n ilk g\u00fcnlerinde <strong>kampanya veya duyuru maili g\u00f6ndermeyin<\/strong>; sadece transactional ak\u0131\u015flar\u0131 ta\u015f\u0131y\u0131n.<\/li>\n<li>\u00d6zellikle <strong>sipari\u015f onay\u0131, kargo bilgisi, \u015fifre s\u0131f\u0131rlama<\/strong> gibi ger\u00e7ekten beklenen mailleri yeni IP\u2019den verin.<\/li>\n<li>Uygulama taraf\u0131nda <strong>rate limiting<\/strong> kullanarak saniyede\/dakikada en fazla ka\u00e7 mail \u00e7\u0131kaca\u011f\u0131n\u0131 s\u0131n\u0131rland\u0131r\u0131n.<\/li>\n<li>Al\u0131c\u0131 sa\u011flay\u0131c\u0131dan 4xx (ge\u00e7ici hata) geldi\u011finde, <strong>kademeli backoff<\/strong> ile yeniden denemeyi planlay\u0131n (\u00f6rne\u011fin 5 dk, 15 dk, 1 saat).<\/li>\n<\/ul>\n<h3><span id=\"Kuyruk_Retry_ve_SMTP_Hatalarini_Dogru_Yorumlamak\">Kuyruk, Retry ve SMTP Hatalar\u0131n\u0131 Do\u011fru Yorumlamak<\/span><\/h3>\n<p>IP \u0131s\u0131nma d\u00f6neminde MTA log\u2019lar\u0131n\u0131z, en de\u011ferli veri kayna\u011f\u0131n\u0131zd\u0131r. 4xx ve 5xx SMTP hata kodlar\u0131n\u0131 do\u011fru yorumlayamayan ekipler, gereksiz pani\u011fe kap\u0131labiliyor veya tam tersi, kritik uyar\u0131lar\u0131 ka\u00e7\u0131rabiliyor. Konu size biraz kar\u0131\u015f\u0131k geliyorsa, <a href='https:\/\/www.dchost.com\/blog\/smtp-hata-kodlari-ve-bounce-mesajlari-rehberi\/'>SMTP hata kodlar\u0131 ve bounce mesajlar\u0131 rehberimize<\/a> g\u00f6z at\u0131n; en s\u0131k g\u00f6r\u00fclen kodlar\u0131 ve ne anlama geldiklerini detayl\u0131 anlatt\u0131k.<\/p>\n<p>Pratik tavsiyeler:<\/p>\n<ul>\n<li>4xx hatalar\u0131nda <strong>ayn\u0131 adrese \u00e7ok s\u0131k retry yapmay\u0131n<\/strong>; bu, spam benzeri g\u00f6r\u00fcn\u00fcr.<\/li>\n<li>5xx (kal\u0131c\u0131 hata) ald\u0131\u011f\u0131n\u0131z adresleri <strong>liste d\u0131\u015f\u0131na \u00e7\u0131kar\u0131n<\/strong>; bozuk adreslerle IP\u2019yi y\u0131pratmay\u0131n.<\/li>\n<li>Her sa\u011flay\u0131c\u0131 i\u00e7in (Gmail, Outlook vb.) ayr\u0131 istatistik tutun; sorun genellikle hepsinde de\u011fil, birinde ba\u015flar.<\/li>\n<\/ul>\n<h2><span id=\"E-Posta_Itibari_Yonetimi_Surekli_Takip_Gerektiren_Bir_Surec\">E-Posta \u0130tibar\u0131 Y\u00f6netimi: S\u00fcrekli Takip Gerektiren Bir S\u00fcre\u00e7<\/span><\/h2>\n<p>Dedicated IP \u0131s\u0131nd\u0131ktan sonra i\u015f bitmiyor. As\u0131l kritik d\u00f6nem, <strong>g\u00fcnl\u00fck operasyonun kal\u0131c\u0131 hale geldi\u011fi<\/strong> d\u00f6nem. \u0130tibar\u0131 korumak i\u00e7in \u00fc\u00e7 ana eksene odaklanmak gerekiyor:<\/p>\n<ul>\n<li>Teknik sinyaller (SPF\/DKIM\/DMARC ge\u00e7i\u015fleri, TLS durumu, PTR uyumu)<\/li>\n<li>Davran\u0131\u015fsal sinyaller (a\u00e7\u0131lma, t\u0131klama, spam \u015fik\u00e2yeti, unsubscribe oranlar\u0131)<\/li>\n<li>Liste kalitesi (ge\u00e7ersiz adresler, spam tuzaklar\u0131, inaktif kullan\u0131c\u0131lar)<\/li>\n<\/ul>\n<h3><span id=\"DMARC_Raporlari_Postmaster_Araclari_ve_Log_Analizi\">DMARC Raporlar\u0131, Postmaster Ara\u00e7lar\u0131 ve Log Analizi<\/span><\/h3>\n<p>\u0130tibar \u00f6l\u00e7\u00fcm\u00fc tek bir panelden yap\u0131lm\u0131yor; birka\u00e7 kayna\u011f\u0131 bir arada okuman\u0131z gerekiyor:<\/p>\n<ul>\n<li><strong>DMARC RUA\/RUF raporlar\u0131<\/strong>: Hangi IP\u2019lerden g\u00f6nderim geliyor, SPF\/DKIM durumu ne, nerede fail al\u0131yorsunuz?<\/li>\n<li><strong>Postmaster ara\u00e7lar\u0131<\/strong>: B\u00fcy\u00fck sa\u011flay\u0131c\u0131lar\u0131n (Gmail vb.) sundu\u011fu panellerle IP ve domain itibar\u0131n\u0131z\u0131 g\u00f6rebilirsiniz.<\/li>\n<li><strong>MTA log\u2019lar\u0131<\/strong>: Hangi sa\u011flay\u0131c\u0131 ne oranda 4xx\/5xx d\u00f6nd\u00fcr\u00fcyor? Hangi saatlerde sorun yo\u011funla\u015f\u0131yor?<\/li>\n<\/ul>\n<p>Geli\u015fmi\u015f DMARC senaryolar\u0131n\u0131 ve BIMI gibi g\u00f6rsel marka g\u00f6stergelerini merak ediyorsan\u0131z, <a href='https:\/\/www.dchost.com\/blog\/gelismis-dmarc-ve-bimi-rua-ruf-raporlarindan-marka-gostergesine-nasil-yol-alinir\/'>Geli\u015fmi\u015f DMARC ve BIMI rehberimiz<\/a> iyi bir tamamlay\u0131c\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"Icerik_Siklik_ve_Liste_Hijyeni\">\u0130\u00e7erik, S\u0131kl\u0131k ve Liste Hijyeni<\/span><\/h3>\n<p>Transactional maillerin i\u00e7eri\u011fi genelde sadedir ama baz\u0131 hatalar itibar\u0131n\u0131z\u0131 gereksiz yere zedeleyebilir:<\/p>\n<ul>\n<li>Konu sat\u0131r\u0131nda <strong>a\u015f\u0131r\u0131 promosyonel<\/strong> ifadeler kullanmay\u0131n.<\/li>\n<li>Linklerin mutlaka <strong>HTTPS ve alan ad\u0131n\u0131zla uyumlu<\/strong> olmas\u0131na dikkat edin.<\/li>\n<li>Transactional maillerde bile m\u00fcmk\u00fcnse <strong>tek t\u0131kla abonelik y\u00f6netimi<\/strong> veya bildirim tercihleri linki sunun.<\/li>\n<li>Uzun s\u00fcre hi\u00e7 etkile\u015fim almayan adresleri (\u00f6rne\u011fin 12+ ay a\u00e7\u0131lmam\u0131\u015f) yava\u015f yava\u015f listeden \u00e7\u0131kar\u0131n veya d\u00fc\u015f\u00fck frekansl\u0131 segmente al\u0131n.<\/li>\n<\/ul>\n<p>\u201cE-postalar neden spam klas\u00f6r\u00fcne d\u00fc\u015f\u00fcyor?\u201d sorusunun alt\u0131nda \u00e7o\u011fu zaman birden fazla sebep yatar. Bunlar\u0131 sistematik \u015fekilde ele ald\u0131\u011f\u0131m\u0131z <a href='https:\/\/www.dchost.com\/blog\/e-postalar-neden-spam-klasorune-dusuyor-paylasimli-hosting-ve-vps-icin-teslim-edilebilirlik-kontrol-listesi\/'>teslim edilebilirlik kontrol listesi yaz\u0131m\u0131z<\/a>, IP \u0131s\u0131nma sonras\u0131 bak\u0131m a\u015famas\u0131nda epey i\u015finize yarar.<\/p>\n<h2><span id=\"DCHost_Altyapisinda_Dedicated_IP_Isitma_Icin_Onerilen_Mimariler\">DCHost Altyap\u0131s\u0131nda Dedicated IP Is\u0131tma \u0130\u00e7in \u00d6nerilen Mimariler<\/span><\/h2>\n<p>IP \u0131s\u0131nma stratejiniz kadar, \u00fczerinde \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131z altyap\u0131 da \u00f6nemli. DCHost taraf\u0131nda en s\u0131k kurdu\u011fumuz \u00fc\u00e7 \u00f6rnek mimariden bahsedelim:<\/p>\n<h3><span id=\"1_Uygulama_Sunucusuyla_Ayni_VPS_Uzerinde_MTA\">1) Uygulama Sunucusuyla Ayn\u0131 VPS \u00dczerinde MTA<\/span><\/h3>\n<p>K\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli projelerde, web uygulaman\u0131z\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 VPS \u00fczerinde Postfix\/Dovecot gibi bir MTA ko\u015fturmak pratik olabilir. Avantajlar\u0131:<\/p>\n<ul>\n<li>Tek sunucu, tek y\u00f6netim noktas\u0131<\/li>\n<li>D\u00fc\u015f\u00fck maliyet, basit mimari<\/li>\n<\/ul>\n<p>Dezavantaj\u0131 ise, web trafi\u011fi ile e-posta trafi\u011finin ayn\u0131 kaynaklar\u0131 payla\u015fmas\u0131d\u0131r. Bu mimariyi kurarken, <a href='https:\/\/www.dchost.com\/blog\/vpste-e%e2%80%91posta-sunucusu-kurulumu-postfix-dovecot-rspamd-ile-teslim-edilebilirlik-ve-ip-isitma-adim-adim\/'>VPS\u2019te e-posta sunucusu kurulumu ve IP \u0131s\u0131tma rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z ad\u0131mlar\u0131 birebir uygulayabilirsiniz.<\/p>\n<h3><span id=\"2_Ayri_VPS_Uzerinde_Ozel_Mail_Sunucusu\">2) Ayr\u0131 VPS \u00dczerinde \u00d6zel Mail Sunucusu<\/span><\/h3>\n<p>Daha ciddi hacimlerde veya kritik transactional trafi\u011fi olan m\u00fc\u015fterilerimiz i\u00e7in en \u00e7ok \u00f6nerdi\u011fimiz yakla\u015f\u0131m bu:<\/p>\n<ul>\n<li>Web uygulamas\u0131 i\u00e7in bir VPS\/dedicated sunucu<\/li>\n<li>Sadece SMTP\/MTA i\u00e7in ikinci bir VPS<\/li>\n<\/ul>\n<p>B\u00f6ylece e-posta trafi\u011fini izole eder, kaynak kullan\u0131m\u0131n\u0131 ve g\u00fcvenlik politikas\u0131n\u0131 daha s\u0131k\u0131 y\u00f6netirsiniz. Ayr\u0131ca IP \u0131s\u0131nma s\u00fcrecini bu \u00f6zel sunucu \u00fczerinde daha rahat kontrol edebilirsiniz.<\/p>\n<h3><span id=\"3_Yuksek_Trafikli_WooCommerce_SaaS_icin_Gelismis_Transactional_Altyapi\">3) Y\u00fcksek Trafikli WooCommerce \/ SaaS i\u00e7in Geli\u015fmi\u015f Transactional Altyap\u0131<\/span><\/h3>\n<p>WooCommerce, Laravel veya SaaS uygulamalar\u0131 i\u00e7in s\u0131k\u00e7a kurdu\u011fumuz bir senaryo:<\/p>\n<ul>\n<li>Web i\u00e7in \u00f6l\u00e7eklenebilir VPS\/dedicated k\u00fcmesi<\/li>\n<li>Arka plan kuyruk i\u015fleri i\u00e7in ayr\u0131 sunucu (Queue worker\u2019lar)<\/li>\n<li>Transactional e-posta i\u00e7in optimize edilmi\u015f MTA sunucusu<\/li>\n<\/ul>\n<p>Bu tip yap\u0131larda, uygulama ile SMTP aras\u0131nda kuyruk kullanmak (\u00f6rne\u011fin Laravel Queue, Supervisor, systemd services) a\u015f\u0131r\u0131 y\u00fcklenmelerde IP\u2019nizi korur. Arka plan i\u015fler ve kuyruk y\u00f6netimi konusunda, <a href='https:\/\/www.dchost.com\/blog\/vps-uzerinde-arka-plan-isleri-ve-kuyruk-yonetimi-laravel-queue-supervisor-systemd-ve-pm2\/'>VPS \u00fczerinde arka plan i\u015fleri ve kuyruk y\u00f6netimi rehberimiz<\/a> size iyi bir yol haritas\u0131 \u00e7izebilir. WooCommerce taraf\u0131nda ise <a href='https:\/\/www.dchost.com\/blog\/wordpress-ve-woocommerce-icin-transactional-e%e2%80%91posta-altyapisi\/'>WooCommerce i\u00e7in transactional e-posta altyap\u0131s\u0131 yaz\u0131m\u0131zda<\/a> daha somut \u00f6rnek mimariler bulabilirsiniz.<\/p>\n<h2><span id=\"Ornek_Senaryo_E-Ticaret_Sitesi_Icin_Transactional_IP_Warmup_Plani\">\u00d6rnek Senaryo: E-Ticaret Sitesi \u0130\u00e7in Transactional IP Warmup Plan\u0131<\/span><\/h2>\n<p>Ger\u00e7ek bir sahne \u00fczerinden gidelim. Orta \u00f6l\u00e7ekli bir e-ticaret m\u00fc\u015fterimiz, kampanya d\u00f6nemleri hari\u00e7 g\u00fcnde yakla\u015f\u0131k 15\u201320 bin transactional mail (sipari\u015f onay\u0131, kargo g\u00fcncellemesi, \u015fifre s\u0131f\u0131rlama, sepet hat\u0131rlatma) g\u00f6nderiyor. Pazarlama maillerini d\u0131\u015f bir servisle y\u00f6netiyor, fakat transactional taraf\u0131 DCHost \u00fczerindeki kendi MTA\u2019s\u0131na ta\u015f\u0131mak istiyor.<\/p>\n<p>Proje planlama toplant\u0131s\u0131nda \u015fu kararlar\u0131 ald\u0131k:<\/p>\n<ul>\n<li>Transactional i\u00e7in <strong>ayr\u0131 bir alt alan ad\u0131<\/strong> tan\u0131mlanacak (<code>notify.marka.com<\/code>).<\/li>\n<li>Bu alan ad\u0131 i\u00e7in SPF\/DKIM\/DMARC, PTR ve MTA-STS kay\u0131tlar\u0131 eksiksiz kurulacak.<\/li>\n<li>Yeni bir VPS \u00fczerinde, sadece MTA ve ilgili servisler \u00e7al\u0131\u015facak.<\/li>\n<li>\u0130lk 2 hafta boyunca, sipari\u015f onay\u0131 ve \u015fifre s\u0131f\u0131rlama mailleri kademeli olarak yeni IP\u2019ye kayd\u0131r\u0131lacak.<\/li>\n<\/ul>\n<p>Uygulama taraf\u0131nda ise:<\/p>\n<ul>\n<li>SMTP ba\u011flant\u0131lar\u0131 i\u00e7in connection pool ve rate limit eklendi.<\/li>\n<li>Greylist ve 4xx hatalar i\u00e7in exponential backoff ile kuyruklama yap\u0131ld\u0131.<\/li>\n<li>G\u00fcnl\u00fck bazda IP\/alan ad\u0131 itibar\u0131 ve bounce oranlar\u0131 raporland\u0131.<\/li>\n<\/ul>\n<p>Sonu\u00e7: Yakla\u015f\u0131k 4 haftan\u0131n sonunda transactional trafi\u011fin tamam\u0131 yeni dedicated IP \u00fczerinde sorunsuz \u00e7al\u0131\u015fmaya ba\u015flad\u0131. En kritik metriklerden olan <strong>\u015fifre s\u0131f\u0131rlama mailinin ilk 5 dakika i\u00e7inde ula\u015fma oran\u0131<\/strong> %96\u2019dan %99+ seviyesine \u00e7\u0131kt\u0131. Ayn\u0131 d\u00f6nemde, spam \u015fik\u00e2yet oran\u0131 %0,05\u2019in alt\u0131nda kald\u0131; bu da IP\u2019nin sa\u011fl\u0131kl\u0131 \u0131s\u0131nd\u0131\u011f\u0131n\u0131 g\u00f6sterdi.<\/p>\n<h2><span id=\"Sik_Yapilan_Hatalar_ve_Kurtarma_Adimlari\">S\u0131k Yap\u0131lan Hatalar ve Kurtarma Ad\u0131mlar\u0131<\/span><\/h2>\n<p>Dedicated IP \u0131s\u0131nma ve e-posta itibar\u0131 y\u00f6netiminde sahada en \u00e7ok g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar\u0131 ve \u00e7\u00f6z\u00fcmlerini madde madde toparlayal\u0131m:<\/p>\n<ul>\n<li><strong>Hata 1: Is\u0131nmam\u0131\u015f IP ile bir anda full hacim g\u00f6nderimi<\/strong><br \/>\u00c7\u00f6z\u00fcm: Kademeli \u0131s\u0131nma plan\u0131na geri d\u00f6n\u00fcn; hacmi d\u00fc\u015f\u00fcr\u00fcn, sadece en s\u0131cak listeye g\u00f6nderin.<\/li>\n<li><strong>Hata 2: Transactional ve pazarlama maillerini ayn\u0131 IP\u2019de kar\u0131\u015ft\u0131rmak<\/strong><br \/>\u00c7\u00f6z\u00fcm: Ayr\u0131 IP veya en az\u0131ndan ayr\u0131 alan ad\u0131\/alt alan ad\u0131 ile segmentasyon yap\u0131n.<\/li>\n<li><strong>Hata 3: Bounce ve \u015fik\u00e2yet oranlar\u0131n\u0131 takip etmemek<\/strong><br \/>\u00c7\u00f6z\u00fcm: MTA log analizi, DMARC raporlar\u0131 ve postmaster panelleriyle d\u00fczenli takip mekanizmas\u0131 kurun.<\/li>\n<li><strong>Hata 4: Blacklist\u2019e girince IP de\u011fi\u015ftirmek ve hi\u00e7bir \u015fey olmam\u0131\u015f gibi devam etmek<\/strong><br \/>\u00c7\u00f6z\u00fcm: \u00d6nce sebebi bulun, liste sa\u011fl\u0131\u011f\u0131n\u0131 d\u00fczeltin, sonra yeni IP\u2019yi <strong>d\u00fczg\u00fcn \u0131s\u0131tarak<\/strong> devreye al\u0131n. Bu a\u015famada <a href='https:\/\/www.dchost.com\/blog\/e-posta-itibarini-kurtarma-rehberi-blacklist-delisting-postmaster-araclari-ve-guvenli-ip-isitma-nasil-kurtarici-olur\/'>e-posta itibar\u0131n\u0131 kurtarma rehberimiz<\/a> ad\u0131m ad\u0131m yol g\u00f6sterir.<\/li>\n<li><strong>Hata 5: DNS, PTR veya SPF\/DKIM hatalar\u0131yla \u0131s\u0131nma denemek<\/strong><br \/>\u00c7\u00f6z\u00fcm: \u00d6nce t\u00fcm DNS ve kimlik do\u011frulama ayarlar\u0131n\u0131 hatas\u0131z hale getirin, sonra \u0131s\u0131tma s\u00fcrecine ba\u015flay\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_Transactional_Mailleriniz_Icin_Saglam_Bir_Temel_Kurun\">Sonu\u00e7: Transactional Mailleriniz \u0130\u00e7in Sa\u011flam Bir Temel Kurun<\/span><\/h2>\n<p>Dedicated IP \u0131s\u0131tma s\u00fcreci; sab\u0131r, tutarl\u0131l\u0131k ve iyi bir g\u00f6zlem gerektiriyor. SPF\/DKIM\/DMARC, PTR, MTA-STS gibi temel ta\u015flar yerinde de\u011filse, en iyi \u0131s\u0131nma plan\u0131 bile istedi\u011finiz sonucu vermez. Buna kar\u015f\u0131l\u0131k, teknik temeli sa\u011flam at\u0131lm\u0131\u015f ve hacmi kademeli art\u0131r\u0131lm\u0131\u015f bir IP ile, transactional mailleriniz y\u0131llarca y\u00fcksek teslim edilebilirlik oranlar\u0131yla \u00e7al\u0131\u015fabilir.<\/p>\n<p>DCHost olarak, ister tek VPS \u00fczerinde basit bir MTA kurmak isteyin, ister yo\u011fun trafi\u011fi kald\u0131racak \u00e7ok katmanl\u0131 bir e-posta mimarisi tasarlay\u0131n, <strong>IP \u0131s\u0131nma ve itibar y\u00f6netimi<\/strong> s\u00fcre\u00e7lerini saha deneyimlerimizle birlikte planlaman\u0131za yard\u0131mc\u0131 oluyoruz. Var olan bir sunucunuzu e-posta i\u00e7in optimize etmek, yeni bir dedicated IP blo\u011fu tahsis etmek veya tamamen yeni bir transactional altyap\u0131 kurmak istiyorsan\u0131z, ekibimizle birlikte; DNS, MTA konfig\u00fcrasyonu, kuyruk y\u00f6netimi ve izleme taraf\u0131n\u0131 u\u00e7tan uca ele alabiliriz.<\/p>\n<p>Transactional e-postalar\u0131n\u0131z\u0131 \u015fansa b\u0131rakmay\u0131n. Dedicated IP \u0131s\u0131s\u0131n\u0131 bilin\u00e7li \u015fekilde art\u0131r\u0131n, e-posta itibar\u0131n\u0131z\u0131 \u00f6l\u00e7\u00fclebilir metriklerle y\u00f6netin ve kullan\u0131c\u0131lar\u0131n\u0131za her zaman zaman\u0131nda ula\u015fan, g\u00fcvenilir bildirimler sunun.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Dedicated IP Is\u0131tma ve E-Posta \u0130tibar\u0131 Neden Bu Kadar Kritik?2 Dedicated IP, Shared IP ve \u0130tibar Mant\u0131\u011f\u01313 Ne Zaman Dedicated IP Is\u0131tmaya \u0130htiyac\u0131n\u0131z Var?4 Is\u0131nmam\u0131\u015f Dedicated IP ile G\u00f6nderim Yapman\u0131n Riskleri5 Is\u0131tma \u00d6ncesi Zorunlu Teknik Haz\u0131rl\u0131k: DNS ve Sunucu Ayarlar\u01315.1 SPF, DKIM ve DMARC Kaynaklar\u01315.2 PTR (Reverse DNS) ve HELO\/EHLO Uyumu5.3 G\u00f6nderim Alan Ad\u0131 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3660,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3659","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3659","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3659"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3659\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3660"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3659"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3659"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3659"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}