{"id":2803,"date":"2025-12-03T19:31:12","date_gmt":"2025-12-03T16:31:12","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/e-posta-altyapisinda-yedeklilik-birden-fazla-mx-kaydi-backup-mx-ve-split-delivery-kurulumu\/"},"modified":"2025-12-03T19:31:12","modified_gmt":"2025-12-03T16:31:12","slug":"e-posta-altyapisinda-yedeklilik-birden-fazla-mx-kaydi-backup-mx-ve-split-delivery-kurulumu","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/e-posta-altyapisinda-yedeklilik-birden-fazla-mx-kaydi-backup-mx-ve-split-delivery-kurulumu\/","title":{"rendered":"E\u2011Posta Altyap\u0131s\u0131nda Yedeklilik: Birden Fazla MX Kayd\u0131, Backup MX ve Split Delivery Kurulumu"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>E\u2011posta altyap\u0131n\u0131z, \u015firket i\u00e7i ileti\u015fimden faturalara, destek taleplerinden kritik g\u00fcvenlik uyar\u0131lar\u0131na kadar neredeyse her s\u00fcrecin omurgas\u0131. Web sitesinin bir s\u00fcre yava\u015flamas\u0131 genelde tolere edilebilir; ancak e\u2011postan\u0131n birka\u00e7 saat bile tamamen gitmemesi \u00e7o\u011fu i\u015fletme i\u00e7in operasyonel kriz demek. Bu y\u00fczden mimari tasar\u0131m, kapasite planlama ve g\u00fcvenlik denetimi yaparken, e\u2011posta taraf\u0131ndaki <strong>yedeklilik stratejisini<\/strong> ayr\u0131 bir ba\u015fl\u0131k olarak ele almak \u015fart.<\/p>\n<p>Bu yaz\u0131da, sahada s\u0131k kulland\u0131\u011f\u0131m\u0131z \u00fc\u00e7 temel mekanizmaya odaklanaca\u011f\u0131z: <strong>birden fazla MX kayd\u0131<\/strong>, <strong>backup MX<\/strong> ve <strong>split delivery<\/strong>. DNS\u2019te MX \u00f6nceliklendirmesi nas\u0131l \u00e7al\u0131\u015f\u0131r, neleri yanl\u0131\u015f yaparsan\u0131z mail\u2019leriniz kaybolmasa bile g\u00fcnlerce gecikebilir, backup MX\u2019i neden herkes \u00f6nermiyor, split delivery ile kademeli ge\u00e7i\u015fi nas\u0131l kurars\u0131n\u0131z; hepsini pratik ad\u0131mlarla anlataca\u011f\u0131m. Amac\u0131m\u0131z; ister <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, ister kendi <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\/dedicated altyap\u0131n\u0131z\u0131 kullan\u0131n, <strong>DCHost \u00fczerinde \u00e7al\u0131\u015fan e\u2011posta mimarinizi<\/strong> kesintilere kar\u015f\u0131 daha dayan\u0131kl\u0131 hale getirmek ve bunu yaparken karma\u015f\u0131k kurallara bo\u011fulmadan ilerleyebilmenizi sa\u011flamak.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Eposta_Altyapisinda_Yedeklilik_Neden_Kritik\"><span class=\"toc_number toc_depth_1\">1<\/span> E\u2011posta Altyap\u0131s\u0131nda Yedeklilik Neden Kritik?<\/a><\/li><li><a href=\"#MX_Kayitlarinin_Mantigi_Oncelik_TTL_ve_Teslimat_Akisi\"><span class=\"toc_number toc_depth_1\">2<\/span> MX Kay\u0131tlar\u0131n\u0131n Mant\u0131\u011f\u0131: \u00d6ncelik, TTL ve Teslimat Ak\u0131\u015f\u0131<\/a><ul><li><a href=\"#MX_kaydi_nedir_nasil_calisir\"><span class=\"toc_number toc_depth_2\">2.1<\/span> MX kayd\u0131 nedir, nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/a><\/li><li><a href=\"#MX_onceligi_ve_yedeklilik_senaryosu\"><span class=\"toc_number toc_depth_2\">2.2<\/span> MX \u00f6nceli\u011fi ve yedeklilik senaryosu<\/a><\/li><li><a href=\"#Birden_fazla_MX_kaydi_yuk_dengeleme_yapar_mi\"><span class=\"toc_number toc_depth_2\">2.3<\/span> Birden fazla MX kayd\u0131 \u201cy\u00fck dengeleme\u201d yapar m\u0131?<\/a><\/li><\/ul><\/li><li><a href=\"#Birden_Fazla_MX_Kaydi_ile_Yedekli_Kurulum_Adimlari\"><span class=\"toc_number toc_depth_1\">3<\/span> Birden Fazla MX Kayd\u0131 ile Yedekli Kurulum Ad\u0131mlar\u0131<\/a><ul><li><a href=\"#1_Mimariyi_planlayin_Ayni_veri_merkezi_mi_farkli_bolgeler_mi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. Mimariyi planlay\u0131n: Ayn\u0131 veri merkezi mi, farkl\u0131 b\u00f6lgeler mi?<\/a><\/li><li><a href=\"#2_DNS_tarafinda_MX_kayitlarini_ekleyin\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. DNS taraf\u0131nda MX kay\u0131tlar\u0131n\u0131 ekleyin<\/a><\/li><li><a href=\"#3_Sunucu_tarafinda_ayni_domain_ve_kullanicilari_tanimlayin\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. Sunucu taraf\u0131nda ayn\u0131 domain ve kullan\u0131c\u0131lar\u0131 tan\u0131mlay\u0131n<\/a><\/li><li><a href=\"#4_Test_senaryolari_MX_yedekliligi_gercekten_calisiyor_mu\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 4. Test senaryolar\u0131: MX yedeklili\u011fi ger\u00e7ekten \u00e7al\u0131\u015f\u0131yor mu?<\/a><\/li><\/ul><\/li><li><a href=\"#Backup_MX_Sunucusu_Avantajlar_Riskler_ve_Dogru_Kurulum\"><span class=\"toc_number toc_depth_1\">4<\/span> Backup MX Sunucusu: Avantajlar, Riskler ve Do\u011fru Kurulum<\/a><ul><li><a href=\"#Backup_MX_nedir_ne_ise_yarar\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Backup MX nedir, ne i\u015fe yarar?<\/a><\/li><li><a href=\"#Neden_herkes_backup_MX_kullanmiyor_Spam_riski\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Neden herkes backup MX kullanm\u0131yor? Spam riski<\/a><\/li><li><a href=\"#Basit_bir_backup_MX_senaryosu_yuksek_seviye\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Basit bir backup MX senaryosu (y\u00fcksek seviye)<\/a><\/li><\/ul><\/li><li><a href=\"#Split_Delivery_Hibrit_Eposta_Mimarilerinde_Trafigi_Bolmek\"><span class=\"toc_number toc_depth_1\">5<\/span> Split Delivery: Hibrit E\u2011posta Mimarilerinde Trafi\u011fi B\u00f6lmek<\/a><ul><li><a href=\"#Split_delivery_nedir\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Split delivery nedir?<\/a><\/li><li><a href=\"#Split_delivery_nasil_uygulanir_Yuksek_seviye_mantik\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Split delivery nas\u0131l uygulan\u0131r? (Y\u00fcksek seviye mant\u0131k)<\/a><\/li><li><a href=\"#Split_deliveryde_dikkat_edilmesi_gerekenler\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Split delivery\u2019de dikkat edilmesi gerekenler<\/a><\/li><\/ul><\/li><li><a href=\"#Yedekli_Eposta_Icin_Altyapi_Secenekleri_DCHost_Perspektifi\"><span class=\"toc_number toc_depth_1\">6<\/span> Yedekli E\u2011posta \u0130\u00e7in Altyap\u0131 Se\u00e7enekleri (DCHost Perspektifi)<\/a><ul><li><a href=\"#Paylasimli_hosting_harici_backup_MX\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Payla\u015f\u0131ml\u0131 hosting + harici backup MX<\/a><\/li><li><a href=\"#Yedekli_VPSdedicated_mimarisi\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Yedekli VPS\/dedicated mimarisi<\/a><\/li><li><a href=\"#Izleme_loglama_ve_felaket_provalari\"><span class=\"toc_number toc_depth_2\">6.3<\/span> \u0130zleme, loglama ve felaket provalar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Ornek_Uygulama_Kucuk_Bir_Sirket_Icin_Adim_Adim_Yol_Haritasi\"><span class=\"toc_number toc_depth_1\">7<\/span> \u00d6rnek Uygulama: K\u00fc\u00e7\u00fck Bir \u015eirket \u0130\u00e7in Ad\u0131m Ad\u0131m Yol Haritas\u0131<\/a><\/li><li><a href=\"#Sonuc_Eposta_Yedekliligini_Luks_Degil_Temel_Ihtiyac_Gibi_Gormek\"><span class=\"toc_number toc_depth_1\">8<\/span> Sonu\u00e7: E\u2011posta Yedeklili\u011fini \u201cL\u00fcks\u201d De\u011fil, Temel \u0130htiya\u00e7 Gibi G\u00f6rmek<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Eposta_Altyapisinda_Yedeklilik_Neden_Kritik\">E\u2011posta Altyap\u0131s\u0131nda Yedeklilik Neden Kritik?<\/span><\/h2>\n<p>Bir\u00e7ok \u015firkette e\u2011posta, fiilen i\u015f ak\u0131\u015f\u0131n\u0131n kay\u0131t sistemi gibi \u00e7al\u0131\u015f\u0131r. Tek bir MX kayd\u0131na, tek bir sunucuya ve tek bir veri merkezine ba\u011fl\u0131 kald\u0131\u011f\u0131n\u0131zda:<\/p>\n<ul>\n<li>Planl\u0131 bak\u0131m s\u0131ras\u0131nda,<\/li>\n<li>Beklenmedik disk ar\u0131zalar\u0131nda,<\/li>\n<li>Veri merkezinde a\u011f veya elektrik sorunu ya\u015fand\u0131\u011f\u0131nda,<\/li>\n<li>Firewall ya da anti\u2011spam taraf\u0131nda yanl\u0131\u015f bir kural devreye girdi\u011finde,<\/li>\n<\/ul>\n<p>t\u00fcm mail trafi\u011finiz an\u0131nda durur. \u00dcstelik SMTP protokol\u00fc gere\u011fi g\u00f6nderen taraf \u00e7o\u011fu zaman mailleri bir s\u00fcre <em>queue<\/em>\u2019da tutar; bu y\u00fczden sorun fark edilene kadar kay\u0131p yerine <strong>gecikme<\/strong> ya\u015fars\u0131n\u0131z. Bazen bu gecikme, m\u00fc\u015fteriye zaman\u0131nda gitmesi gereken kritik bir onay\u0131n ka\u00e7\u0131r\u0131lmas\u0131 demektir.<\/p>\n<p>DCHost\u2019ta altyap\u0131 tasarlarken, t\u0131pk\u0131 web trafi\u011finde yapt\u0131\u011f\u0131m\u0131z gibi e\u2011posta taraf\u0131nda da <strong>tek hata noktas\u0131n\u0131 ortadan kald\u0131rmay\u0131<\/strong> hedefliyoruz. Yedekli MX kay\u0131tlar\u0131, backup MX sunucular\u0131 ve split delivery mimarileri; y\u00fcksek kullan\u0131labilirlik (HA) mimarisi kuracak kadar b\u00fct\u00e7esi olmayan k\u00fc\u00e7\u00fck ekipler i\u00e7in bile olduk\u00e7a makul maliyetlerle uygulanabiliyor. DNS\u2019in nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 daha temelden hat\u0131rlamak isterseniz, \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/\">DNS kay\u0131tlar\u0131 A\u2019dan Z\u2019ye rehberimizi<\/a> g\u00f6zden ge\u00e7irmenizi \u00f6neririm.<\/p>\n<h2><span id=\"MX_Kayitlarinin_Mantigi_Oncelik_TTL_ve_Teslimat_Akisi\">MX Kay\u0131tlar\u0131n\u0131n Mant\u0131\u011f\u0131: \u00d6ncelik, TTL ve Teslimat Ak\u0131\u015f\u0131<\/span><\/h2>\n<h3><span id=\"MX_kaydi_nedir_nasil_calisir\">MX kayd\u0131 nedir, nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/span><\/h3>\n<p>MX (Mail Exchanger) kayd\u0131, bir alan ad\u0131 i\u00e7in <strong>e\u2011posta kabul etmekle sorumlu sunucular\u0131<\/strong> DNS d\u00fczeyinde tan\u0131mlar. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">example.com.   3600   IN   MX   10 mail1.example.com.\nexample.com.   3600   IN   MX   20 mail2.example.com.\n<\/code><\/pre>\n<p>Bu yap\u0131, <code>@example.com<\/code> adresine gelen t\u00fcm maillerin \u00f6nce <code>mail1<\/code> sunucusuna, bu sunucu yan\u0131t vermiyorsa <code>mail2<\/code> sunucusuna g\u00f6nderilmesini s\u00f6yler. Buradaki <strong>\u00f6ncelik de\u011feri<\/strong> (10, 20 vs.), say\u0131sal olarak ne kadar k\u00fc\u00e7\u00fckse o kadar \u00f6nceliklidir.<\/p>\n<h3><span id=\"MX_onceligi_ve_yedeklilik_senaryosu\">MX \u00f6nceli\u011fi ve yedeklilik senaryosu<\/span><\/h3>\n<p>Bir g\u00f6nderen sunucu, sizin alan ad\u0131n\u0131za mail atarken DNS\u2019ten MX kay\u0131tlar\u0131n\u0131z\u0131 \u00e7eker; ard\u0131ndan:<\/p>\n<ol>\n<li>\u00d6nceli\u011fi en d\u00fc\u015f\u00fck (\u00f6r. 10) MX sunucusuna ba\u011flanmaya \u00e7al\u0131\u015f\u0131r.<\/li>\n<li>TCP ba\u011flant\u0131s\u0131 kurulamazsa veya sunucu 4xx\/5xx hatalar\u0131 d\u00f6nerse, bir sonraki MX kayd\u0131na (\u00f6r. 20) ge\u00e7er.<\/li>\n<li>Hi\u00e7bir MX\u2019e ba\u011flanamazsa, maili kuyrukta bekletir ve belirli aral\u0131klarla tekrar dener.<\/li>\n<\/ol>\n<p>\u0130\u015fte bu ak\u0131\u015f, bize <strong>\u201cpasif yedeklilik\u201d<\/strong> sa\u011flar. Birincil MX sunucunuz kapal\u0131yken, ikincil MX devreye girer. Bu tasar\u0131m\u0131n sa\u011fl\u0131kl\u0131 \u00e7al\u0131\u015fabilmesi i\u00e7in:<\/p>\n<ul>\n<li>Her MX kayd\u0131n\u0131n i\u015faret etti\u011fi A\/AAAA kay\u0131tlar\u0131n\u0131n do\u011fru olmas\u0131,<\/li>\n<li>Her MX sunucusunda ayn\u0131 alan adlar\u0131 ve posta kutular\u0131n\u0131n tan\u0131ml\u0131 olmas\u0131 (veya do\u011fru relay kurallar\u0131n\u0131n yap\u0131lmas\u0131),<\/li>\n<li>MX kay\u0131tlar\u0131nda \u00e7ok d\u00fc\u015f\u00fck TTL kullanarak s\u00fcrekli DNS g\u00fcncellemesine g\u00fcvenmemek,<\/li>\n<\/ul>\n<p>gerekir. TTL stratejileriyle ilgili daha derin bir bak\u0131\u015f i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">zero\u2011downtime ta\u015f\u0131ma i\u00e7in TTL stratejileri rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h3><span id=\"Birden_fazla_MX_kaydi_yuk_dengeleme_yapar_mi\">Birden fazla MX kayd\u0131 \u201cy\u00fck dengeleme\u201d yapar m\u0131?<\/span><\/h3>\n<p>\u00c7ok yayg\u0131n bir yanl\u0131\u015f anlama var: \u201c\u0130ki MX kayd\u0131 ekleyeyim, biri 10, di\u011feri 20 olsun; b\u00f6ylece y\u00fck dengelenir.\u201d Hay\u0131r; SMTP taraf\u0131nda <strong>\u00f6ncelik tabanl\u0131 bir fallback<\/strong> vard\u0131r, ger\u00e7ek anlamda a\u011f\u0131rl\u0131kl\u0131 y\u00fck dengeleme yoktur. Baz\u0131 g\u00f6nderici sunucu implementasyonlar\u0131, e\u015fit \u00f6ncelikli MX kay\u0131tlar\u0131 aras\u0131nda rastgele se\u00e7im yapabilir; ama bu davran\u0131\u015fa g\u00fcvenerek <strong>load balancing<\/strong> stratejisi kurmak sa\u011fl\u0131kl\u0131 de\u011fildir.<\/p>\n<p>E\u011fer ger\u00e7ekten y\u00fck da\u011f\u0131tmak istiyorsan\u0131z, genelde tek bir MX kayd\u0131 arkas\u0131nda \u00e7al\u0131\u015fan yedekli MTA k\u00fcmesi (\u00f6rne\u011fin birden fazla VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>nun ortak IP\/Anycast\/Load Balancer arkas\u0131na al\u0131nmas\u0131) tasarlamak daha do\u011fru bir yakla\u015f\u0131md\u0131r. Bu da DCHost\u2019ta VPS ya da dedicated sunucu \u00e7\u00f6z\u00fcmleri ile kurulan ayr\u0131 bir mimari konusudur.<\/p>\n<h2><span id=\"Birden_Fazla_MX_Kaydi_ile_Yedekli_Kurulum_Adimlari\">Birden Fazla MX Kayd\u0131 ile Yedekli Kurulum Ad\u0131mlar\u0131<\/span><\/h2>\n<h3><span id=\"1_Mimariyi_planlayin_Ayni_veri_merkezi_mi_farkli_bolgeler_mi\">1. Mimariyi planlay\u0131n: Ayn\u0131 veri merkezi mi, farkl\u0131 b\u00f6lgeler mi?<\/span><\/h3>\n<p>\u0130lk soru \u015fu: Yedeklili\u011fi <strong>hangi seviyede<\/strong> istiyorsunuz?<\/p>\n<ul>\n<li><strong>Ayn\u0131 veri merkezinde iki farkl\u0131 sunucu:<\/strong> Donan\u0131m ar\u0131zalar\u0131na kar\u015f\u0131 korur; ancak veri merkezi genelinde ya\u015fanacak elektrik\/a\u011f sorunlar\u0131na kar\u015f\u0131 savunmas\u0131zd\u0131r.<\/li>\n<li><strong>Farkl\u0131 veri merkezlerinde iki sunucu:<\/strong> Hem donan\u0131m hem de tesis seviyesinde yedeklilik sa\u011flar; fakat replikasyon, latency ve maliyet a\u00e7\u0131s\u0131ndan daha karma\u015f\u0131kt\u0131r.<\/li>\n<li><strong>Farkl\u0131 tip altyap\u0131:<\/strong> \u00d6rne\u011fin, birincil sunucu DCHost \u00fczerinde y\u00f6netilen bir VPS, ikincil ise ba\u015fka lokasyonda daha minimal bir relay node olabilir.<\/li>\n<\/ul>\n<p>K\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli \u015firketlerin \u00e7o\u011fu i\u00e7in, <strong>DCHost \u00fczerinde iki farkl\u0131 fiziksel host\u2019ta \u00e7al\u0131\u015fan yedekli VPS<\/strong> ile ba\u015flamak genelde optimum \u00e7\u00f6z\u00fcmd\u00fcr. Daha b\u00fcy\u00fck yap\u0131larda dedicated + colocation kombinasyonlar\u0131yla da \u00e7ok b\u00f6lgeli HA mimarileri kurabiliyoruz.<\/p>\n<h3><span id=\"2_DNS_tarafinda_MX_kayitlarini_ekleyin\">2. DNS taraf\u0131nda MX kay\u0131tlar\u0131n\u0131 ekleyin<\/span><\/h3>\n<p>\u00d6rnek bir senaryoyu ele alal\u0131m. Alan ad\u0131n\u0131z: <code>firma.com<\/code>. \u0130ki mail sunucunuz var:<\/p>\n<ul>\n<li><code>mx1.firma.com<\/code> \u2013 Birincil sunucu<\/li>\n<li><code>mx2.firma.com<\/code> \u2013 \u0130kincil (yedek) sunucu<\/li>\n<\/ul>\n<p>DNS kay\u0131tlar\u0131n\u0131z kabaca \u015f\u00f6yle olabilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">firma.com.     3600   IN   MX   10 mx1.firma.com.\nfirma.com.     3600   IN   MX   20 mx2.firma.com.\n\nmx1.firma.com. 3600   IN   A    192.0.2.10\nmx2.firma.com. 3600   IN   A    192.0.2.20\n<\/code><\/pre>\n<p>Burada kritik noktalar:<\/p>\n<ul>\n<li><strong>mx1 ve mx2 i\u00e7in A\/AAAA kay\u0131tlar\u0131<\/strong> mutlaka tan\u0131ml\u0131 olmal\u0131.<\/li>\n<li>Her iki IP i\u00e7in de <strong>rDNS (PTR) kay\u0131tlar\u0131<\/strong> do\u011fru \u015fekilde ayarl\u0131 olmal\u0131 ve HELO\/EHLO host ad\u0131 ile <strong>tutarl\u0131<\/strong> olmal\u0131 (\u00f6rnek: <code>mx1.firma.com<\/code>).<\/li>\n<li>SPF, DKIM ve DMARC kay\u0131tlar\u0131n\u0131zda hangi IP\u2019lerden mail \u00e7\u0131kaca\u011f\u0131n\u0131 a\u00e7\u0131k\u00e7a tan\u0131mlamal\u0131s\u0131n\u0131z. Bunun i\u00e7in detayl\u0131 bir rehbere ihtiyac\u0131n\u0131z varsa <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/\">SPF, DKIM, DMARC ve rDNS ile e\u2011posta teslim edilebilirli\u011fini art\u0131rma rehberimizi<\/a> mutlaka okuyun.<\/li>\n<\/ul>\n<h3><span id=\"3_Sunucu_tarafinda_ayni_domain_ve_kullanicilari_tanimlayin\">3. Sunucu taraf\u0131nda ayn\u0131 domain ve kullan\u0131c\u0131lar\u0131 tan\u0131mlay\u0131n<\/span><\/h3>\n<p>MX yedeklili\u011finin en \u00e7ok atlanan k\u0131sm\u0131 buras\u0131d\u0131r. DNS\u2019te iki MX kayd\u0131 olmas\u0131 yetmez; <strong>her iki MTA\u2019da da ayn\u0131 alan adlar\u0131 ve posta kutular\u0131<\/strong> tan\u0131ml\u0131 olmal\u0131d\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Her iki sunucuda da <code>firma.com<\/code> local domain olarak ekli olmal\u0131,<\/li>\n<li><code>info@firma.com<\/code>, <code>destek@firma.com<\/code> gibi kullan\u0131c\u0131lar her iki tarafta da olu\u015fturulmal\u0131 (veya merkezi bir IMAP\/Storage altyap\u0131s\u0131na ba\u011fl\u0131 olmal\u0131),<\/li>\n<li>Mailbox senkronizasyonu (DRBD\/ZFS replication, IMAP sync gibi) i\u00e7in bir stratejiniz olmal\u0131.<\/li>\n<\/ul>\n<p>E\u011fer sadece <strong>kabul taraf\u0131n\u0131<\/strong> yedeklemek, as\u0131l posta kutular\u0131n\u0131 tek bir IMAP sunucusunda tutmak istiyorsan\u0131z; ikincil MX\u2019te local mailbox a\u00e7mak yerine, mailleri birincil sunucuya <strong>relay eden<\/strong> bir yap\u0131 da kurabilirsiniz. Bu senaryo backup MX b\u00f6l\u00fcm\u00fcnde daha detayl\u0131 ele al\u0131nacak.<\/p>\n<h3><span id=\"4_Test_senaryolari_MX_yedekliligi_gercekten_calisiyor_mu\">4. Test senaryolar\u0131: MX yedeklili\u011fi ger\u00e7ekten \u00e7al\u0131\u015f\u0131yor mu?<\/span><\/h3>\n<p>Yap\u0131land\u0131rma bitti\u011finde mutlaka \u015fu testleri yap\u0131n:<\/p>\n<ul>\n<li>Bir istemciden (\u00f6rne\u011fin kendi test mail sunucunuzdan) <code>@firma.com<\/code> adreslerine mail at\u0131n, normal durumda maillerin <code>mx1<\/code> \u00fczerinden al\u0131nd\u0131\u011f\u0131n\u0131 log\u2019lardan do\u011frulay\u0131n.<\/li>\n<li><code>mx1<\/code> sunucusunun SMTP portunu (25) firewall ile ge\u00e7ici olarak kapat\u0131n veya servisi durdurun.<\/li>\n<li>Tekrar mail g\u00f6nderip, bu kez g\u00f6nderen sunucunun log\u2019lar\u0131nda <code>mx2<\/code>\u2019ye ba\u011fland\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcn.<\/li>\n<li>\u0130stemci taraf\u0131nda gecikmenin makul seviyede (genelde saniyeler mertebesinde) oldu\u011fundan emin olun.<\/li>\n<\/ul>\n<p>Bu testleri m\u00fcmk\u00fcnse periyodik olarak tekrarlay\u0131p, dok\u00fcmante edin. DCHost\u2019ta e\u2011posta ta\u015f\u0131ma s\u00fcre\u00e7lerinde benzer <strong>failover provalar\u0131n\u0131<\/strong> standart bir ad\u0131m olarak uygulat\u0131yoruz. Ta\u015f\u0131ma a\u015famalar\u0131n\u0131n detayl\u0131 bir \u00f6rne\u011fini <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/\">e\u2011posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken kesinti ya\u015famamak rehberinde<\/a> bulabilirsiniz.<\/p>\n<h2><span id=\"Backup_MX_Sunucusu_Avantajlar_Riskler_ve_Dogru_Kurulum\">Backup MX Sunucusu: Avantajlar, Riskler ve Do\u011fru Kurulum<\/span><\/h2>\n<h3><span id=\"Backup_MX_nedir_ne_ise_yarar\">Backup MX nedir, ne i\u015fe yarar?<\/span><\/h3>\n<p>Backup MX, alan ad\u0131n\u0131z i\u00e7in <strong>ikinci (veya \u00fc\u00e7\u00fcnc\u00fc) s\u0131rada tan\u0131ml\u0131<\/strong>, g\u00f6revi normalde mail teslim etmek de\u011fil, sadece:<\/p>\n<ul>\n<li>Birincil MX eri\u015filemezken mailleri <strong>ge\u00e7ici olarak kuyru\u011fa almak<\/strong>,<\/li>\n<li>Birincil MX tekrar aya\u011fa kalkt\u0131\u011f\u0131nda bu mailleri ona iletmek,<\/li>\n<\/ul>\n<p>olan bir SMTP sunucusudur. Yani <strong>\u201cpark yeri\u201d<\/strong> gibi d\u00fc\u015f\u00fcnebilirsiniz. G\u00f6nderen sunucu sizin birincil MX\u2019inize ula\u015famay\u0131nca, backup MX\u2019e d\u00fc\u015fer; backup MX mailleri kendi kuyru\u011funda tutar ve siz d\u00f6nd\u00fc\u011f\u00fcn\u00fczde teslim eder.<\/p>\n<h3><span id=\"Neden_herkes_backup_MX_kullanmiyor_Spam_riski\">Neden herkes backup MX kullanm\u0131yor? Spam riski<\/span><\/h3>\n<p>Backup MX, yanl\u0131\u015f kuruldu\u011funda <strong>spam m\u0131knat\u0131s\u0131<\/strong> haline gelebilir. Baz\u0131 spam g\u00f6ndericiler, do\u011frudan birincil MX yerine backup MX\u2019e mail atarak:<\/p>\n<ul>\n<li>Anti\u2011spam kontrolleri daha zay\u0131f olan bir sunucu bulmaya \u00e7al\u0131\u015f\u0131r,<\/li>\n<li>Relay kurallar\u0131n\u0131 hatal\u0131 yap\u0131land\u0131rm\u0131\u015f misconfig\u2019li backup MX\u2019leri istismar eder,<\/li>\n<li>Ge\u00e7ici hatalar (4xx) yerine kal\u0131c\u0131 hatalar (5xx) almamak i\u00e7in yedek MX\u2019ten medet umar.<\/li>\n<\/ul>\n<p>Bu y\u00fczden backup MX kurarken dikkat edilmesi gerekenler:<\/p>\n<ul>\n<li>Backup MX \u00fczerinde de g\u00fc\u00e7l\u00fc anti\u2011spam kontrolleri (RBL, greylisting, SPF\/DMARC do\u011frulama vb.) \u00e7al\u0131\u015fmal\u0131.<\/li>\n<li>Backup MX <strong>a\u00e7\u0131k relay<\/strong> olmamal\u0131; sadece belirli domain\u2019ler ve belirli hedef sunucular i\u00e7in relay izni verilmeli.<\/li>\n<li>Mailleri s\u00fcresiz bekletmemeli; makul bir maksimum kuyruk s\u00fcresi (\u00f6r. 3\u20135 g\u00fcn) tan\u0131mlanmal\u0131.<\/li>\n<\/ul>\n<p>Anti\u2011spam taraf\u0131nda neler yapabilece\u011finizi daha pratik g\u00f6rmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/cpanelde-e%e2%80%91posta-spam-filtreleme-spamassassin-rbl-kara-liste-ve-karantina-yonetimi\/\">cPanel\u2019de e\u2011posta spam filtreleme rehberimizi<\/a> incelemeniz faydal\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"Basit_bir_backup_MX_senaryosu_yuksek_seviye\">Basit bir backup MX senaryosu (y\u00fcksek seviye)<\/span><\/h3>\n<p>Diyelim ki:<\/p>\n<ul>\n<li>Birincil MTA: <code>mx1.firma.com<\/code> (Postfix),<\/li>\n<li>Backup MTA: <code>mx-backup.dchost-mail.net<\/code> (DCHost \u00fczerinde ayr\u0131 bir VPS),<\/li>\n<\/ul>\n<p>olsun. DNS taraf\u0131:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">firma.com.   3600   IN   MX   10 mx1.firma.com.\nfirma.com.   3600   IN   MX   20 mx-backup.dchost-mail.net.\n<\/code><\/pre>\n<p>Backup MX \u00fczerindeki y\u00fcksek seviye mant\u0131k ise \u015fu \u015fekilde olur:<\/p>\n<ul>\n<li><code>relay_domains<\/code> i\u00e7ine sadece <code>firma.com<\/code> eklenir.<\/li>\n<li>Destination olarak <code>mx1.firma.com<\/code> tan\u0131mlan\u0131r.<\/li>\n<li>Birincil MTA eri\u015filemiyorsa, mailler kuyru\u011fa al\u0131n\u0131r ve d\u00fczenli aral\u0131klarla tekrar teslim denenir.<\/li>\n<\/ul>\n<p>Burada backup MX, asla kullan\u0131c\u0131 posta kutusu bar\u0131nd\u0131rmaz; sadece <strong>ak\u0131ll\u0131 bir kuyruk<\/strong> g\u00f6revi g\u00f6r\u00fcr. DCHost ekibi olarak m\u00fc\u015fterilerimiz i\u00e7in kurdu\u011fumuz yedekli e\u2011posta ortamlar\u0131nda \u00e7o\u011funlukla bu yakla\u015f\u0131m\u0131 kullan\u0131yoruz; bu sayede hem altyap\u0131 sade kal\u0131yor hem de senkronizasyon karma\u015fas\u0131 azalm\u0131\u015f oluyor.<\/p>\n<h2><span id=\"Split_Delivery_Hibrit_Eposta_Mimarilerinde_Trafigi_Bolmek\">Split Delivery: Hibrit E\u2011posta Mimarilerinde Trafi\u011fi B\u00f6lmek<\/span><\/h2>\n<h3><span id=\"Split_delivery_nedir\">Split delivery nedir?<\/span><\/h3>\n<p>Split delivery, ayn\u0131 alan ad\u0131ndaki farkl\u0131 kullan\u0131c\u0131lar\u0131n maillerini <strong>farkl\u0131 hedef sistemlere y\u00f6nlendirmek<\/strong> anlam\u0131na gelir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li><code>ad.soyad@firma.com<\/code> adreslerinin bir k\u0131sm\u0131 DCHost \u00fczerindeki kendi mail sunucunuzda,<\/li>\n<li>Di\u011fer k\u0131sm\u0131 harici bir SaaS e\u2011posta platformunda,<\/li>\n<\/ul>\n<p>bar\u0131n\u0131yor olabilir. Bu durumda gelen mail trafi\u011fini, SMTP taraf\u0131nda kullan\u0131c\u0131ya g\u00f6re b\u00f6lmeniz gerekir.<\/p>\n<p>Tipik kullan\u0131m senaryolar\u0131:<\/p>\n<ul>\n<li>Mevcut on\u2011premise veya VPS mail sunucusundan bulut tabanl\u0131 bir servise <strong>kademeli ge\u00e7i\u015f<\/strong>,<\/li>\n<li>Farkl\u0131 departmanlar\u0131n (\u00f6rne\u011fin \u00e7a\u011fr\u0131 merkezi vs. y\u00f6netim) farkl\u0131 mail altyap\u0131lar\u0131 kullanmas\u0131,<\/li>\n<li>Grup \u015firketlerinde, baz\u0131 markalar\u0131n merkezi mail sistemi, baz\u0131lar\u0131n\u0131n lokal sistemler kullanmas\u0131.<\/li>\n<\/ul>\n<h3><span id=\"Split_delivery_nasil_uygulanir_Yuksek_seviye_mantik\">Split delivery nas\u0131l uygulan\u0131r? (Y\u00fcksek seviye mant\u0131k)<\/span><\/h3>\n<p>Split delivery genelde \u00fc\u00e7 ana yakla\u015f\u0131mla kurulur:<\/p>\n<ol>\n<li><strong>Directory tabanl\u0131 y\u00f6nlendirme:<\/strong> Kullan\u0131c\u0131 listesi (LDAP\/AD vb.) hangi kullan\u0131c\u0131n\u0131n hangi platformda oldu\u011funu bilir; MTA bu bilgiye g\u00f6re mailleri i\u00e7eri veya d\u0131\u015far\u0131 relay eder.<\/li>\n<li><strong>Adres tabanl\u0131 statik y\u00f6nlendirme:<\/strong> Belirli adres veya domain pattern\u2019leri i\u00e7in farkl\u0131 hedef sunucu tan\u0131mlan\u0131r (\u00f6rne\u011fin Postfix <code>transport_maps<\/code> ile).<\/li>\n<li><strong>Catch\u2011all + forward:<\/strong> T\u00fcm mailler \u00f6nce birincil sisteme gelir; burada var olmayan kullan\u0131c\u0131lar i\u00e7in harici bir hedefe y\u00f6nlendirme yap\u0131l\u0131r.<\/li>\n<\/ol>\n<p>K\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli yap\u0131larda genelde ikinci y\u00f6ntem (adres tabanl\u0131 statik y\u00f6nlendirme) daha pratik olur. \u00d6rne\u011fin Postfix\u2019te:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">transport_maps = hash:\/etc\/postfix\/transport\n<\/code><\/pre>\n<p>dosyas\u0131na:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">kullanici1@firma.com   smtp:[harici-mail-sunucusu]\n@altdepartman.firma.com  smtp:[diger-sunucu]\n<\/code><\/pre>\n<p>gibi kurallar eklenerek belirli kullan\u0131c\u0131lara gelen mailler farkl\u0131 hedeflere ta\u015f\u0131nabilir.<\/p>\n<h3><span id=\"Split_deliveryde_dikkat_edilmesi_gerekenler\">Split delivery\u2019de dikkat edilmesi gerekenler<\/span><\/h3>\n<p>Split delivery kurarken:<\/p>\n<ul>\n<li>Hangi kullan\u0131c\u0131n\u0131n hangi platformda oldu\u011funu tek bir yerde (\u00f6rne\u011fin bir YAML\/CSV dosyas\u0131 veya merkezi directory) takip etti\u011finizden emin olun.<\/li>\n<li>Yanl\u0131\u015fl\u0131kla <strong>loop (d\u00f6ng\u00fc)<\/strong> olu\u015fmamas\u0131 i\u00e7in her iki u\u00e7ta da relay kurallar\u0131n\u0131 dikkatle tasarlay\u0131n.<\/li>\n<li>SPF\/DKIM\/DMARC politikalar\u0131n\u0131z\u0131n, maillerin \u00e7\u0131kt\u0131\u011f\u0131 t\u00fcm sistemleri kapsad\u0131\u011f\u0131ndan emin olun.<\/li>\n<li>Ge\u00e7i\u015f s\u00fcrecinde, eski sistemde kalan maillerin imap\/POP \u00fczerinden ta\u015f\u0131nmas\u0131 i\u00e7in ek bir plan yap\u0131n.<\/li>\n<\/ul>\n<p>Alan ad\u0131n\u0131 veya mail altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken kesintiyi en aza indirmek i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-tasirken-e%e2%80%91posta-kesintisini-onlemek\/\">alan ad\u0131 ta\u015f\u0131rken e\u2011posta kesintisini \u00f6nleme rehberi<\/a>, split delivery senaryolar\u0131 planlarken de i\u015finize yarayacakt\u0131r.<\/p>\n<h2><span id=\"Yedekli_Eposta_Icin_Altyapi_Secenekleri_DCHost_Perspektifi\">Yedekli E\u2011posta \u0130\u00e7in Altyap\u0131 Se\u00e7enekleri (DCHost Perspektifi)<\/span><\/h2>\n<h3><span id=\"Paylasimli_hosting_harici_backup_MX\">Payla\u015f\u0131ml\u0131 hosting + harici backup MX<\/span><\/h3>\n<p>Bir\u00e7ok k\u00fc\u00e7\u00fck i\u015fletme i\u00e7in klasik senaryo \u015fu:<\/p>\n<ul>\n<li>Web sitesi ve mail ayn\u0131 payla\u015f\u0131ml\u0131 hosting hesab\u0131nda,<\/li>\n<li>MX, hosting sunucusunu g\u00f6steriyor,<\/li>\n<li>Ba\u015fka hi\u00e7bir yedeklilik yok.<\/li>\n<\/ul>\n<p>Bu durumda bile en az\u0131ndan <strong>harici bir backup MX<\/strong> ekleyerek ciddi kazan\u0131mlar elde edebilirsiniz. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Birincil MX: Payla\u015f\u0131ml\u0131 hosting IP\u2019si,<\/li>\n<li>Backup MX: DCHost\u2019ta basit bir VPS \u00fczerinde kurulu Postfix relay node\u2019u.<\/li>\n<\/ul>\n<p>B\u00f6ylece hosting taraf\u0131nda ya\u015fanacak bir kesinti s\u0131ras\u0131nda mailleriniz hala backup MX kuyruklar\u0131na kabul edilir; siz d\u00f6nd\u00fc\u011f\u00fcn\u00fczde teslim edilir. Bu senaryoda VPS \u00fczerinde kuraca\u011f\u0131n\u0131z mail sunucusunun detaylar\u0131n\u0131 merak ediyorsan\u0131z, <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\u2011posta sunucusu kurulumu rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h3><span id=\"Yedekli_VPSdedicated_mimarisi\">Yedekli VPS\/dedicated mimarisi<\/span><\/h3>\n<p>Daha y\u00fcksek hacimli e\u2011posta trafi\u011fi olan, kendi MTA\u2019s\u0131n\u0131 ve anti\u2011spam altyap\u0131s\u0131n\u0131 y\u00f6neten \u015firketler i\u00e7in \u00f6nerdi\u011fimiz tipik kurgu:<\/p>\n<ul>\n<li>\u0130ki ayr\u0131 fiziksel host \u00fczerinde \u00e7al\u0131\u015fan yedekli VPS\u2019ler veya dedicated sunucular,<\/li>\n<li>Her iki sunucuda da ayn\u0131 domain ve kullan\u0131c\u0131lar\u0131n tan\u0131ml\u0131 olmas\u0131,<\/li>\n<li>Veri katman\u0131nda (mailbox\u2019larda) replikasyon veya d\u00fczenli IMAP sync,<\/li>\n<li>MX kay\u0131tlar\u0131nda birincil\/ikincil \u00f6nceliklendirme,<\/li>\n<li>Harici bir izleme sistemiyle SMTP health\u2011check\u2019leri.<\/li>\n<\/ul>\n<p>Bu t\u00fcr yap\u0131larda genelde e\u2011posta altyap\u0131s\u0131n\u0131 da genel felaket kurtarma plan\u0131n\u0131z\u0131n bir par\u00e7as\u0131 yap\u0131yoruz. Bu konuya daha geni\u015f a\u00e7\u0131dan bakmak isterseniz, genel felaket senaryolar\u0131 ve yedekleme stratejileri i\u00e7in blogumuzdaki di\u011fer yaz\u0131lara da g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"Izleme_loglama_ve_felaket_provalari\">\u0130zleme, loglama ve felaket provalar\u0131<\/span><\/h3>\n<p>MX yedeklili\u011fi ve backup MX\/split delivery kurulumunu tamamlad\u0131ktan sonra i\u015f bitmiyor; en az kurulum kadar \u00f6nemli \u00fc\u00e7 ba\u015fl\u0131k var:<\/p>\n<ul>\n<li><strong>\u0130zleme:<\/strong> SMTP portlar\u0131n\u0131n (25, submission i\u00e7in 587) d\u0131\u015far\u0131dan eri\u015filebilirli\u011fini, gecikmeleri ve hata kodlar\u0131n\u0131 d\u00fczenli izleyin.<\/li>\n<li><strong>Loglama:<\/strong> MTA log\u2019lar\u0131n\u0131 merkezi bir sistemde toplay\u0131p (\u00f6rne\u011fin syslog + log analiz arac\u0131), bounces, gecikmeler ve RBL sorunlar\u0131n\u0131 erken yakalay\u0131n.<\/li>\n<li><strong>Prova:<\/strong> Belirli periyotlarla, birincil MX\u2019i kas\u0131tl\u0131 olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131p backup MX ve split delivery kurallar\u0131n\u0131z\u0131n ger\u00e7ekten beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 test edin.<\/li>\n<\/ul>\n<p>DCHost olarak, \u00f6zellikle yo\u011fun mail trafi\u011fi olan m\u00fc\u015fteriler i\u00e7in bu testleri de\u011fi\u015fik senaryolarla birlikte (DNS kesintisi, IP de\u011fi\u015fimi, antrepo dolulu\u011fu vb.) planl\u0131yoruz. E\u2011posta ta\u015f\u0131ma ve yeni altyap\u0131ya ge\u00e7i\u015f s\u00fcre\u00e7lerinde, <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/\">kesintisiz ge\u00e7i\u015f rehberinde<\/a> anlatt\u0131\u011f\u0131m\u0131z DNS cutover teknikleriyle bu testleri birle\u015ftirmek olduk\u00e7a verimli sonu\u00e7 veriyor.<\/p>\n<h2><span id=\"Ornek_Uygulama_Kucuk_Bir_Sirket_Icin_Adim_Adim_Yol_Haritasi\">\u00d6rnek Uygulama: K\u00fc\u00e7\u00fck Bir \u015eirket \u0130\u00e7in Ad\u0131m Ad\u0131m Yol Haritas\u0131<\/span><\/h2>\n<p>Diyelim ki 30 ki\u015filik bir ekibiniz var, e\u2011postalar\u0131n\u0131z \u015fu an tek bir payla\u015f\u0131ml\u0131 hosting hesab\u0131nda ve bir s\u00fcredir ara ara k\u0131sa kesintiler ya\u015f\u0131yorsunuz. Hedefiniz:<\/p>\n<ul>\n<li>Mail kesintilerini minimuma indirmek,<\/li>\n<li>Altyap\u0131n\u0131z\u0131 orta vadede kendi VPS veya dedicated sunucunuza ta\u015f\u0131mak,<\/li>\n<li>Bu ge\u00e7i\u015fi ad\u0131m ad\u0131m, risksiz \u015fekilde yapmak.<\/li>\n<\/ul>\n<p>\u0130zleyebilece\u011finiz pratik yol haritas\u0131:<\/p>\n<ol>\n<li><strong>Alan ad\u0131 ve DNS envanterini \u00e7\u0131kar\u0131n:<\/strong> Hangi nameserver\u2019leri kullan\u0131yorsunuz, mevcut MX ve A\/AAAA kay\u0131tlar\u0131n\u0131z neler? Bu a\u015famada <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/\">DNS kay\u0131tlar\u0131 rehberine<\/a> bir g\u00f6z atmak iyi olur.<\/li>\n<li><strong>DCHost\u2019ta k\u00fc\u00e7\u00fck bir VPS ay\u0131r\u0131n:<\/strong> Bu VPS, \u00f6nce backup MX ve ge\u00e7i\u015f s\u00fcrecinde split delivery i\u00e7in gateway g\u00f6revi g\u00f6rebilir.<\/li>\n<li><strong>VPS \u00fczerine MTA kurun:<\/strong> Postfix + Dovecot + rspamd gibi bir kurulumla ba\u015flayabilir, yap\u0131land\u0131rma i\u00e7in ad\u0131m ad\u0131m anlat\u0131lan <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\u2011posta sunucusu rehberinden<\/a> yararlanabilirsiniz.<\/li>\n<li><strong>Backup MX olarak devreye al\u0131n:<\/strong> Alan ad\u0131n\u0131z\u0131n MX kay\u0131tlar\u0131na VPS\u2019i ikincil MX olarak ekleyin. B\u00f6ylece en az\u0131ndan kesinti anlar\u0131nda mailler kuyruklara kabul edilmeye ba\u015flar.<\/li>\n<li><strong>Kademeli split delivery planlay\u0131n:<\/strong> \u00d6nce IT ekibi gibi k\u00fc\u00e7\u00fck bir kullan\u0131c\u0131 grubunu yeni VPS MTA\u2019ya ta\u015f\u0131y\u0131n. Split delivery veya adres y\u00f6nlendirme ile sadece bu ki\u015filerin maillerini yeni altyap\u0131ya y\u00f6nlendirin.<\/li>\n<li><strong>G\u00f6zlem ve optimizasyon:<\/strong> Bir s\u00fcre izleyin, anti\u2011spam ayarlar\u0131n\u0131, SPF\/DKIM\/DMARC yap\u0131land\u0131rmas\u0131n\u0131 optimize edin. Teslim edilebilirlik taraf\u0131nda sorun kalmad\u0131\u011f\u0131ndan emin olun.<\/li>\n<li><strong>T\u00fcm kullan\u0131c\u0131lar\u0131 ta\u015f\u0131y\u0131n ve MX\u2019i de\u011fi\u015ftirin:<\/strong> Her \u015fey yolundaysa, t\u00fcm kullan\u0131c\u0131lar\u0131n mailbox\u2019lar\u0131n\u0131 yeni sunucuya ta\u015f\u0131y\u0131p MX \u00f6nceli\u011fini tamamen yeni altyap\u0131ya verebilirsiniz.<\/li>\n<\/ol>\n<p>Bu s\u00fcreci do\u011fru planlarsan\u0131z, neredeyse s\u0131f\u0131ra yak\u0131n kesintiyle ve kullan\u0131c\u0131lar\u0131n \u00e7ok az fark edece\u011fi bir deneyimle e\u2011posta altyap\u0131n\u0131z\u0131 bir \u00fcst seviyeye ta\u015f\u0131m\u0131\u015f olursunuz.<\/p>\n<h2><span id=\"Sonuc_Eposta_Yedekliligini_Luks_Degil_Temel_Ihtiyac_Gibi_Gormek\">Sonu\u00e7: E\u2011posta Yedeklili\u011fini \u201cL\u00fcks\u201d De\u011fil, Temel \u0130htiya\u00e7 Gibi G\u00f6rmek<\/span><\/h2>\n<p>E\u2011posta altyap\u0131s\u0131nda yedeklilik \u00e7o\u011fu zaman, kriz ya\u015fanana kadar g\u00f6z ard\u0131 edilen bir ba\u015fl\u0131k. Oysa bir alan ad\u0131 i\u00e7in birka\u00e7 basit MX kayd\u0131 eklemek, k\u00fc\u00e7\u00fck bir VPS ile backup MX kurgulamak veya split delivery ile kademeli ge\u00e7i\u015f planlamak; b\u00fct\u00e7enizi zorlamadan <strong>i\u015f s\u00fcreklili\u011finizi ciddi bi\u00e7imde g\u00fc\u00e7lendiriyor<\/strong>. \u00d6zellikle finans, hukuk, sa\u011fl\u0131k, e\u2011ticaret gibi sekt\u00f6rlerde, birka\u00e7 saatlik mail kesintisinin bile do\u011frudan para ve itibar kayb\u0131 anlam\u0131na geldi\u011fini sahada defalarca g\u00f6r\u00fcyoruz.<\/p>\n<p>DCHost olarak biz, e\u2011posta mimarisini sadece \u201chosting paketinin yan\u0131nda gelen \u00f6zellik\u201d olarak de\u011fil, <strong>ba\u015fl\u0131 ba\u015f\u0131na tasarlanmas\u0131 gereken bir altyap\u0131 bile\u015feni<\/strong> olarak ele al\u0131yoruz. MX yedeklili\u011fi, backup MX ve split delivery gibi mekanizmalar\u0131 do\u011fru kurdu\u011funuzda; SPF, DKIM, DMARC, MTA\u2011STS gibi ek g\u00fcvenlik katmanlar\u0131yla birle\u015ftirdi\u011finizde, hem teslim edilebilirli\u011fi hem de kesintilere kar\u015f\u0131 dayan\u0131kl\u0131l\u0131\u011f\u0131 ayn\u0131 anda art\u0131rm\u0131\u015f olursunuz.<\/p>\n<p>E\u2011posta altyap\u0131n\u0131z\u0131 DCHost \u00fczerinde yeniden tasarlamak, mevcut yap\u0131n\u0131z\u0131 yedekli hale getirmek veya yeni bir domain i\u00e7in s\u0131f\u0131rdan temiz bir kurulum yapmak istiyorsan\u0131z; ekibimizle beraber ad\u0131m ad\u0131m planlayabiliriz. \u00d6nce mevcut DNS ve MX yap\u0131n\u0131z\u0131 g\u00f6zden ge\u00e7irip, sonra i\u015finize ve b\u00fct\u00e7enize uygun bir yol haritas\u0131 \u00e7\u0131karal\u0131m; siz i\u015finize odaklan\u0131rken, biz e\u2011postalar\u0131n\u0131z\u0131n her ko\u015fulda sorunsuz akmas\u0131n\u0131 sa\u011flayal\u0131m.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>E\u2011posta altyap\u0131n\u0131z, \u015firket i\u00e7i ileti\u015fimden faturalara, destek taleplerinden kritik g\u00fcvenlik uyar\u0131lar\u0131na kadar neredeyse her s\u00fcrecin omurgas\u0131. Web sitesinin bir s\u00fcre yava\u015flamas\u0131 genelde tolere edilebilir; ancak e\u2011postan\u0131n birka\u00e7 saat bile tamamen gitmemesi \u00e7o\u011fu i\u015fletme i\u00e7in operasyonel kriz demek. Bu y\u00fczden mimari tasar\u0131m, kapasite planlama ve g\u00fcvenlik denetimi yaparken, e\u2011posta taraf\u0131ndaki yedeklilik stratejisini ayr\u0131 bir ba\u015fl\u0131k olarak [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2804,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2803","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\/2803","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=2803"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2803\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2804"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}