{"id":2754,"date":"2025-12-03T15:19:02","date_gmt":"2025-12-03T12:19:02","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/"},"modified":"2025-12-03T15:19:02","modified_gmt":"2025-12-03T12:19:02","slug":"e-posta-altyapisini-tasirken-kesinti-yasamamak","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/","title":{"rendered":"E-Posta Altyap\u0131s\u0131n\u0131 Ta\u015f\u0131rken Kesinti Ya\u015famamak"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>E-posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131mak, bir \u015firket i\u00e7in sadece teknik bir operasyon de\u011fil, i\u015f s\u00fcreklili\u011fini do\u011frudan etkileyen kritik bir ad\u0131md\u0131r. Sat\u0131\u015f ekibiniz m\u00fc\u015fteri tekliflerini, hukuk ekibiniz s\u00f6zle\u015fmeleri, operasyon ekibiniz g\u00fcnl\u00fck i\u015f ak\u0131\u015f\u0131n\u0131 e-posta \u00fczerinden y\u00fcr\u00fct\u00fcyor. Dolay\u0131s\u0131yla Google Workspace, Microsoft 365 veya cPanel tabanl\u0131 bir e-posta altyap\u0131s\u0131ndan di\u011ferine ge\u00e7erken ya\u015fanacak birka\u00e7 saatlik kesinti bile hem itibar hem de gelir kayb\u0131 anlam\u0131na gelebilir. Bu yaz\u0131da, DCHost ekibinde s\u0131k s\u0131k planlad\u0131\u011f\u0131m\u0131z ve y\u00f6netti\u011fimiz e-posta ge\u00e7i\u015f operasyonlar\u0131ndan edindi\u011fimiz tecr\u00fcbeleri payla\u015farak; Google Workspace, Microsoft 365 ve cPanel aras\u0131nda <strong>neredeyse s\u0131f\u0131r kesintiyle<\/strong> e-posta ta\u015f\u0131man\u0131n pratik bir yol haritas\u0131n\u0131 anlataca\u011f\u0131z.<\/p>\n<p>Odak noktam\u0131z \u015fu olacak: DNS taraf\u0131nda MX ve SPF\/DKIM\/DMARC kay\u0131tlar\u0131n\u0131 do\u011fru s\u0131rada de\u011fi\u015ftirmek, kutulardaki (mailbox) verileri \u00f6nceden senkronize etmek, ge\u00e7i\u015ften sonra eski altyap\u0131y\u0131 bir s\u00fcre daha aktif tutmak ve kullan\u0131c\u0131 taraf\u0131ndaki deneyimi minimum seviyede etkilemek. Yaz\u0131y\u0131, hem k\u00fc\u00e7\u00fck \u00f6l\u00e7ekli i\u015fletmelerin hem de \u00e7oklu domain ve y\u00fczlerce hesap y\u00f6neten IT ekiplerinin sahada ger\u00e7ekten uygulayabilece\u011fi net ad\u0131mlar \u015feklinde yap\u0131land\u0131rd\u0131k.<\/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=\"#E-Posta_Altyapisini_Tasimak_Neden_Riskli\"><span class=\"toc_number toc_depth_1\">1<\/span> E-Posta Altyap\u0131s\u0131n\u0131 Ta\u015f\u0131mak Neden Riskli?<\/a><\/li><li><a href=\"#Temel_Kavramlar_MX_TTL_SPFDKIMDMARC_ve_IMAP_Senkronizasyonu\"><span class=\"toc_number toc_depth_1\">2<\/span> Temel Kavramlar: MX, TTL, SPF\/DKIM\/DMARC ve IMAP Senkronizasyonu<\/a><ul><li><a href=\"#MX_kayitlari_ve_TTL\"><span class=\"toc_number toc_depth_2\">2.1<\/span> MX kay\u0131tlar\u0131 ve TTL<\/a><\/li><li><a href=\"#SPF_DKIM_ve_DMARC\"><span class=\"toc_number toc_depth_2\">2.2<\/span> SPF, DKIM ve DMARC<\/a><\/li><li><a href=\"#IMAP_senkronizasyonu_ve_veri_tasima\"><span class=\"toc_number toc_depth_2\">2.3<\/span> IMAP senkronizasyonu ve veri ta\u015f\u0131ma<\/a><\/li><\/ul><\/li><li><a href=\"#Genel_Sifir_Kesinti_Stratejisi_Cati_Plan\"><span class=\"toc_number toc_depth_1\">3<\/span> Genel S\u0131f\u0131r Kesinti Stratejisi: \u00c7at\u0131 Plan<\/a><\/li><li><a href=\"#Senaryo_1_cPanel8217den_Google_Workspace8217e_Gecis\"><span class=\"toc_number toc_depth_1\">4<\/span> Senaryo 1: cPanel&#8217;den Google Workspace&#8217;e Ge\u00e7i\u015f<\/a><ul><li><a href=\"#1_Planlama_ve_hazirlik\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1. Planlama ve haz\u0131rl\u0131k<\/a><\/li><li><a href=\"#2_Google_Workspace_uzerinde_domain_ve_kullanicilari_olusturma\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2. Google Workspace \u00fczerinde domain ve kullan\u0131c\u0131lar\u0131 olu\u015fturma<\/a><\/li><li><a href=\"#3_IMAP_Migration_ile_veri_senkronizasyonu\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3. IMAP Migration ile veri senkronizasyonu<\/a><\/li><li><a href=\"#4_MX_cutover_MX_kayitlarini_Google_Workspace8217e_yonlendirme\"><span class=\"toc_number toc_depth_2\">4.4<\/span> 4. MX cutover: MX kay\u0131tlar\u0131n\u0131 Google Workspace&#8217;e y\u00f6nlendirme<\/a><\/li><li><a href=\"#5_SPF_DKIM_ve_DMARC_guncellemeleri\"><span class=\"toc_number toc_depth_2\">4.5<\/span> 5. SPF, DKIM ve DMARC g\u00fcncellemeleri<\/a><\/li><li><a href=\"#6_Eski_cPanel_altyapisini_ne_zaman_kapatmali\"><span class=\"toc_number toc_depth_2\">4.6<\/span> 6. Eski cPanel altyap\u0131s\u0131n\u0131 ne zaman kapatmal\u0131?<\/a><\/li><\/ul><\/li><li><a href=\"#Senaryo_2_cPanel8217den_Microsoft_3658217e_Gecis\"><span class=\"toc_number toc_depth_1\">5<\/span> Senaryo 2: cPanel&#8217;den Microsoft 365&#8217;e Ge\u00e7i\u015f<\/a><ul><li><a href=\"#1_Microsoft_365_uzerinde_domain_ve_kullanicilari_kurma\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. Microsoft 365 \u00fczerinde domain ve kullan\u0131c\u0131lar\u0131 kurma<\/a><\/li><li><a href=\"#2_Migration_endpoint_ve_batch_migration\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. Migration endpoint ve batch migration<\/a><\/li><li><a href=\"#3_MX_degisimi_ve_SPFDKIM_ayarlari\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. MX de\u011fi\u015fimi ve SPF\/DKIM ayarlar\u0131<\/a><\/li><li><a href=\"#4_Outlook_ve_mobil_istemcilerin_yeniden_yapilandirilmasi\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. Outlook ve mobil istemcilerin yeniden yap\u0131land\u0131r\u0131lmas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Senaryo_3_Google_Workspace_Microsoft_365_Arasi_Gecis\"><span class=\"toc_number toc_depth_1\">6<\/span> Senaryo 3: Google Workspace \u2194 Microsoft 365 Aras\u0131 Ge\u00e7i\u015f<\/a><ul><li><a href=\"#1_Gecis_modelini_belirleyin_Big_bang_mi_kademeli_mi\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Ge\u00e7i\u015f modelini belirleyin: Big bang mi, kademeli mi?<\/a><\/li><li><a href=\"#2_Veri_migrasyonu_API_tabanli_veya_IMAP_tabanli\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. Veri migrasyonu: API tabanl\u0131 veya IMAP tabanl\u0131<\/a><\/li><li><a href=\"#3_Mail_flow_kurallari_ve_gecici_yonlendirmeler\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3. Mail flow kurallar\u0131 ve ge\u00e7ici y\u00f6nlendirmeler<\/a><\/li><li><a href=\"#4_Takvim_kisi_ve_paylasimli_kutular\"><span class=\"toc_number toc_depth_2\">6.4<\/span> 4. Takvim, ki\u015fi ve payla\u015f\u0131ml\u0131 kutular<\/a><\/li><\/ul><\/li><li><a href=\"#Senaryo_4_Google_Workspace_Microsoft_3658217ten_cPanel_veya_Kendi_Sunucunuza_Donus\"><span class=\"toc_number toc_depth_1\">7<\/span> Senaryo 4: Google Workspace \/ Microsoft 365&#8217;ten cPanel veya Kendi Sunucunuza D\u00f6n\u00fc\u015f<\/a><ul><li><a href=\"#1_Hedef_mimariyi_netlestirin\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1. Hedef mimariyi netle\u015ftirin<\/a><\/li><li><a href=\"#2_Kullanici_ve_veri_tasima\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2. Kullan\u0131c\u0131 ve veri ta\u015f\u0131ma<\/a><\/li><li><a href=\"#3_MX_ve_SPFin_kontrollu_degisimi\"><span class=\"toc_number toc_depth_2\">7.3<\/span> 3. MX ve SPF\u2019in kontroll\u00fc de\u011fi\u015fimi<\/a><\/li><\/ul><\/li><li><a href=\"#Kontrol_Listesi_Sifir_Kesinti_E-Posta_Tasima_Adimlari\"><span class=\"toc_number toc_depth_1\">8<\/span> Kontrol Listesi: S\u0131f\u0131r Kesinti E-Posta Ta\u015f\u0131ma Ad\u0131mlar\u0131<\/a><\/li><li><a href=\"#DCHost_ile_E-Posta_Gecisini_Daha_Guvenli_Yurutmek\"><span class=\"toc_number toc_depth_1\">9<\/span> DCHost ile E-Posta Ge\u00e7i\u015fini Daha G\u00fcvenli Y\u00fcr\u00fctmek<\/a><\/li><\/ul><\/div>\n<h2><span id=\"E-Posta_Altyapisini_Tasimak_Neden_Riskli\">E-Posta Altyap\u0131s\u0131n\u0131 Ta\u015f\u0131mak Neden Riskli?<\/span><\/h2>\n<p>\u00d6nce riskleri netle\u015ftirelim ki, ge\u00e7i\u015f plan\u0131n\u0131 buna g\u00f6re sa\u011flam kurabilelim. E-posta altyap\u0131s\u0131 ta\u015f\u0131ma s\u00fcrecinde genellikle \u015fu \u00fc\u00e7 ba\u015fl\u0131k ba\u015f\u0131n\u0131z\u0131 a\u011fr\u0131t\u0131r:<\/p>\n<ul>\n<li><strong>Kesinti ve kay\u0131p e-postalar:<\/strong> MX kay\u0131tlar\u0131 tam oturmadan yap\u0131lan ge\u00e7i\u015flerde, baz\u0131 e-postalar eski sisteme, baz\u0131lar\u0131 yeni sisteme, baz\u0131lar\u0131 ise hi\u00e7 ula\u015fmaz.<\/li>\n<li><strong>\u0130tibar ve teslim edilebilirlik:<\/strong> SPF, DKIM, DMARC ve rDNS yanl\u0131\u015f kurgulan\u0131rsa, yeni altyap\u0131n\u0131zdan g\u00f6nderilen e-postalar spam klas\u00f6r\u00fcne d\u00fc\u015fmeye ba\u015flar.<\/li>\n<li><strong>Kullan\u0131c\u0131 deneyimi:<\/strong> Outlook, mobil istemciler, \u015fifreler ve klas\u00f6r yap\u0131lar\u0131 d\u00fczg\u00fcn ta\u015f\u0131nmazsa, ofiste herkesin ayn\u0131 anda size soru sordu\u011fu stresli bir g\u00fcne d\u00f6n\u00fc\u015f\u00fcr.<\/li>\n<\/ul>\n<p>Bunlar\u0131n tamam\u0131 teknik olarak \u00e7\u00f6z\u00fclebilir problemler. Konu, <strong>do\u011fru s\u0131ray\u0131<\/strong> ve <strong>do\u011fru zamanlamay\u0131<\/strong> tutturmak. DNS taraf\u0131ndaki kritiklerin bir \u00f6zetini isterseniz, daha \u00f6nce yazd\u0131\u011f\u0131m\u0131z <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 rehberine<\/a> de mutlaka g\u00f6z at\u0131n.<\/p>\n<h2><span id=\"Temel_Kavramlar_MX_TTL_SPFDKIMDMARC_ve_IMAP_Senkronizasyonu\">Temel Kavramlar: MX, TTL, SPF\/DKIM\/DMARC ve IMAP Senkronizasyonu<\/span><\/h2>\n<p>Ge\u00e7i\u015f senaryolar\u0131na girmeden \u00f6nce, \u00fczerinde konu\u015faca\u011f\u0131m\u0131z temel yap\u0131 ta\u015flar\u0131n\u0131 netle\u015ftirelim.<\/p>\n<h3><span id=\"MX_kayitlari_ve_TTL\">MX kay\u0131tlar\u0131 ve TTL<\/span><\/h3>\n<p><strong>MX (Mail Exchanger)<\/strong> kay\u0131tlar\u0131, bir alan ad\u0131 i\u00e7in e-postalar\u0131n hangi sunucuya teslim edilece\u011fini belirler. \u00d6rne\u011fin <code>example.com<\/code> alan ad\u0131n\u0131z varsa, MX kay\u0131tlar\u0131 &#8220;bu domain\u2019e gelen e-postalar\u0131 \u015fu servise g\u00f6nder&#8221; talimat\u0131d\u0131r.<\/p>\n<ul>\n<li><strong>MX de\u011fi\u015fikli\u011fi = Yol tabelas\u0131n\u0131 de\u011fi\u015ftirmek<\/strong>. Yanl\u0131\u015f zamanda yaparsan\u0131z, e-postalar iki farkl\u0131 yere da\u011f\u0131l\u0131r.<\/li>\n<li><strong>TTL (Time To Live)<\/strong>, DNS kayd\u0131n\u0131n \u00f6nbellekte ne kadar s\u00fcre tutulaca\u011f\u0131n\u0131 belirler. Ge\u00e7i\u015ften <em>\u00f6nce<\/em> TTL\u2019i d\u00fc\u015f\u00fcrmezseniz, baz\u0131 kullan\u0131c\u0131lar eski MX\u2019e uzun s\u00fcre gitmeye devam eder.<\/li>\n<\/ul>\n<p>DNS yay\u0131l\u0131m\u0131n\u0131 h\u0131zland\u0131rmak i\u00e7in TTL stratejisini nas\u0131l kullanaca\u011f\u0131n\u0131z\u0131 detayl\u0131ca anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirsin\/\">Zero-downtime ta\u015f\u0131ma i\u00e7in TTL stratejileri<\/a> yaz\u0131s\u0131na da g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"SPF_DKIM_ve_DMARC\">SPF, DKIM ve DMARC<\/span><\/h3>\n<p>E-posta kimlik do\u011frulama taraf\u0131n\u0131n \u00fc\u00e7 temel kayd\u0131 vard\u0131r:<\/p>\n<ul>\n<li><strong>SPF:<\/strong> Hangi sunucular\u0131n bu domain ad\u0131na e-posta g\u00f6ndermeye yetkili oldu\u011funu s\u00f6yler.<\/li>\n<li><strong>DKIM:<\/strong> G\u00f6nderilen e-postay\u0131, domain\u2019in \u00f6zel anahtar\u0131yla imzalayarak al\u0131c\u0131 tarafa &#8220;bu e-posta ger\u00e7ekten bu domain\u2019den&#8221; sinyali verir.<\/li>\n<li><strong>DMARC:<\/strong> SPF\/DKIM kontrol\u00fc ba\u015far\u0131s\u0131z olursa, al\u0131c\u0131 sunucunun ne yapmas\u0131 gerekti\u011fini (reddet, karantinaya al, raporla) tan\u0131mlar.<\/li>\n<\/ul>\n<p>Yeni altyap\u0131ya ge\u00e7erken SPF, DKIM ve DMARC\u2019\u0131 do\u011fru g\u00fcncellemezseniz, \u00f6zellikle Google Workspace ve Microsoft 365 gibi servisler \u00fczerinde teslim edilebilirlik s\u0131k\u0131nt\u0131lar\u0131 ya\u015fars\u0131n\u0131z. Bu alan\u0131 ad\u0131m ad\u0131m kurmak i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/\">SPF, DKIM, DMARC ile e-posta teslim edilebilirli\u011fini art\u0131rma rehberini<\/a> mutlaka okunacaklar listenize ekleyin.<\/p>\n<h3><span id=\"IMAP_senkronizasyonu_ve_veri_tasima\">IMAP senkronizasyonu ve veri ta\u015f\u0131ma<\/span><\/h3>\n<p>\u00c7o\u011fu kurumsal ge\u00e7i\u015fte as\u0131l kritik nokta, eski posta kutular\u0131ndaki verileri yeni ortama <strong>\u00f6nceden<\/strong> senkronize edebilmektir. Bunun i\u00e7in:<\/p>\n<ul>\n<li>IMAP \u00fczerinden eski ve yeni sunucuya ba\u011flan\u0131p klas\u00f6rleri bire bir kopyalayan ara\u00e7lar,<\/li>\n<li>Google Workspace \/ Microsoft 365\u2019in kendi sa\u011flad\u0131\u011f\u0131 Migration ara\u00e7lar\u0131,<\/li>\n<li>cPanel taraf\u0131nda tam hesap yede\u011fi (full backup) ve restore mekanizmalar\u0131<\/li>\n<\/ul>\n<p>kullan\u0131l\u0131r. cPanel\u2019den cPanel\u2019e ve cPanel\u2019den farkl\u0131 sunuculara e-posta ta\u015f\u0131may\u0131 teknik seviyede anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/cpanel-e%E2%80%91posta-hesaplarini-yeni-sunucuya-tasimak-imap-senkronizasyonu-ve-dns-cutover\/\">cPanel e-posta hesaplar\u0131n\u0131 yeni sunucuya ta\u015f\u0131mak<\/a> yaz\u0131s\u0131 da, bu yaz\u0131n\u0131n do\u011fal bir tamamlay\u0131c\u0131s\u0131d\u0131r.<\/p>\n<h2><span id=\"Genel_Sifir_Kesinti_Stratejisi_Cati_Plan\">Genel S\u0131f\u0131r Kesinti Stratejisi: \u00c7at\u0131 Plan<\/span><\/h2>\n<p>Google Workspace, Microsoft 365 ve cPanel aras\u0131nda t\u00fcm ge\u00e7i\u015f senaryolar\u0131nda uygulayabilece\u011finiz ortak bir \u00e7at\u0131 strateji var. \u00d6nce bu \u015fablonu anlatal\u0131m, sonra her senaryo i\u00e7in \u00f6zelle\u015ftirelim.<\/p>\n<ol>\n<li><strong>Envanter \u00e7\u0131kar\u0131n:<\/strong> Ka\u00e7 domain, ka\u00e7 kullan\u0131c\u0131, ka\u00e7 alias, hangi cihazlar (Outlook, mobil, webmail) kullan\u0131l\u0131yor? Da\u011f\u0131t\u0131k ekipler, departman bazl\u0131 \u00f6zel kurallar var m\u0131?<\/li>\n<li><strong>DNS eri\u015fimini netle\u015ftirin:<\/strong> Domain\u2019in DNS\u2019ini kim y\u00f6netiyor? Panel giri\u015fleri kimde? De\u011fi\u015fiklikleri kim uygulayacak?<\/li>\n<li><strong>TTL\u2019i \u00f6nceden d\u00fc\u015f\u00fcr\u00fcn:<\/strong> Ge\u00e7i\u015ften en az 24-48 saat \u00f6nce ilgili MX ve TXT (SPF, do\u011frulama kay\u0131tlar\u0131) i\u00e7in TTL\u2019i 300 saniye (veya 600) seviyesine indirin.<\/li>\n<li><strong>Yeni ortam\u0131 paralel kurun:<\/strong> Google Workspace \/ Microsoft 365 \/ cPanel \u00fczerinde domain\u2019i ekleyin, posta kutular\u0131n\u0131 olu\u015fturun, parolalar\u0131 belirleyin.<\/li>\n<li><strong>\u0130lk senkronizasyonu yap\u0131n:<\/strong> IMAP Migration veya yerle\u015fik ta\u015f\u0131ma ara\u00e7lar\u0131yla mevcut veriyi yeni ortama \u00e7ekin. Kullan\u0131c\u0131lar bu s\u0131rada eski sistemde \u00e7al\u0131\u015fmaya devam edebilir.<\/li>\n<li><strong>Test kullan\u0131c\u0131lar\u0131yla pilot ge\u00e7i\u015f:<\/strong> \u00d6nce 2-3 test hesab\u0131n\u0131 tamamen ta\u015f\u0131y\u0131n, MX\u2019leri onlar i\u00e7in de\u011fi\u015ftirin (m\u00fcmk\u00fcnse alt domain veya ayr\u0131 domainle).<\/li>\n<li><strong>MX cutover (ana ge\u00e7i\u015f):<\/strong> Her \u015fey yolundaysa, ana domain\u2019in MX kay\u0131tlar\u0131n\u0131 yeni altyap\u0131ya y\u00f6nlendirin.<\/li>\n<li><strong>Art\u0131k senkronizasyonu:<\/strong> MX de\u011fi\u015fiminden sonra bir s\u00fcre daha delta (sadece son de\u011fi\u015fiklikler) senkronizasyonu yaparak kay\u0131p riskini azalt\u0131n.<\/li>\n<li><strong>Eski altyap\u0131y\u0131 bir s\u00fcre a\u00e7\u0131k tutun:<\/strong> En az 3-7 g\u00fcn, m\u00fcmk\u00fcnse 2 hafta. B\u00f6ylece gecikmeli DNS yay\u0131l\u0131m\u0131ndan gelen son e-postalar\u0131 da yakalars\u0131n\u0131z.<\/li>\n<li><strong>Kullan\u0131c\u0131 taraf\u0131 temizlik:<\/strong> Outlook profilleri, mobil hesaplar, imzalar, payla\u015f\u0131ml\u0131 kutular vb. son r\u00f6tu\u015flar\u0131 yap\u0131n.<\/li>\n<\/ol>\n<p>Alan ad\u0131 \/ DNS taraf\u0131nda e-posta kesintisi ya\u015fama risklerini ayr\u0131ca anlatt\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-posta kesintisini \u00f6nlemek<\/a> yaz\u0131s\u0131n\u0131 da bu a\u015famada okuman\u0131z faydal\u0131 olur.<\/p>\n<h2><span id=\"Senaryo_1_cPanel8217den_Google_Workspace8217e_Gecis\">Senaryo 1: cPanel&#8217;den Google Workspace&#8217;e Ge\u00e7i\u015f<\/span><\/h2>\n<p>Bir\u00e7ok m\u00fc\u015fterimizin en s\u0131k yapt\u0131\u011f\u0131 ge\u00e7i\u015flerden biri: Klasik cPanel e-posta altyap\u0131s\u0131ndan Google Workspace\u2019e ta\u015f\u0131nmak. Burada ama\u00e7 genellikle spam filtreleme kalitesini, mobil entegrasyonlar\u0131 ve i\u015fbirli\u011fi ara\u00e7lar\u0131n\u0131 (Drive, Docs vb.) daha yo\u011fun kullanmak.<\/p>\n<h3><span id=\"1_Planlama_ve_hazirlik\">1. Planlama ve haz\u0131rl\u0131k<\/span><\/h3>\n<ul>\n<li>Hangi domain\u2019ler Google Workspace\u2019e ta\u015f\u0131nacak?<\/li>\n<li>Ka\u00e7 aktif kullan\u0131c\u0131, ka\u00e7 alias var?<\/li>\n<li>Mailing list, forwarder, catch-all kullan\u0131l\u0131yor mu?<\/li>\n<li>Toplam posta kutusu boyutlar\u0131 nedir? (Quota raporlar\u0131n\u0131 cPanel\u2019den alabilirsiniz.)<\/li>\n<\/ul>\n<p>Bu envanter, lisans say\u0131s\u0131n\u0131, ge\u00e7i\u015f s\u00fcresini ve bant geni\u015fli\u011fi ihtiyac\u0131n\u0131 netle\u015ftirir.<\/p>\n<h3><span id=\"2_Google_Workspace_uzerinde_domain_ve_kullanicilari_olusturma\">2. Google Workspace \u00fczerinde domain ve kullan\u0131c\u0131lar\u0131 olu\u015fturma<\/span><\/h3>\n<ul>\n<li>Google Workspace y\u00f6netim konsolunda domain\u2019i ekleyin.<\/li>\n<li>\u0130lgili TXT do\u011frulama kayd\u0131n\u0131 <strong>DNS\u2019e ekleyin<\/strong> ama MX kay\u0131tlar\u0131n\u0131 <strong>hen\u00fcz de\u011fi\u015ftirmeyin<\/strong>.<\/li>\n<li>Kullan\u0131c\u0131 hesaplar\u0131n\u0131 (mailbox\u2019lar\u0131) elle veya CSV\/import ile olu\u015fturun.<\/li>\n<li>Ge\u00e7ici parolalar olu\u015fturup, \u015fifre de\u011fi\u015fimini ilk giri\u015fte zorunlu k\u0131labilirsiniz.<\/li>\n<\/ul>\n<h3><span id=\"3_IMAP_Migration_ile_veri_senkronizasyonu\">3. IMAP Migration ile veri senkronizasyonu<\/span><\/h3>\n<p>Google Workspace\u2019in yerle\u015fik Migration arac\u0131n\u0131 kullanarak cPanel\u2019deki eski posta kutular\u0131n\u0131 yeni hesaplara IMAP \u00fczerinden \u00e7ekebilirsiniz. Ad\u0131mlar \u00f6zetle:<\/p>\n<ol>\n<li>cPanel sunucunuzda IMAP portlar\u0131n\u0131n (993\/143) d\u0131\u015far\u0131 a\u00e7\u0131k ve eri\u015filebilir oldu\u011funu do\u011frulay\u0131n.<\/li>\n<li>Migration kayna\u011f\u0131 olarak IMAP sunucunuzu (\u00f6rn. <code>mail.sirketiniz.com<\/code>) tan\u0131mlay\u0131n.<\/li>\n<li>Kullan\u0131c\u0131 e\u015fle\u015ftirmelerini (eski adres \u2192 yeni adres) girin.<\/li>\n<li>\u0130lk tam senkronizasyonu ba\u015flat\u0131n ve bitmesini bekleyin.<\/li>\n<\/ol>\n<p>Burada kritik nokta, kullan\u0131c\u0131lar\u0131n <strong>hala eski cPanel kutusunu kullanmaya devam etti\u011fi<\/strong> bir d\u00f6nemde ilk kopyalamay\u0131 yapman\u0131zd\u0131r. B\u00f6ylece b\u00fcy\u00fck veri k\u00fctlesini \u00f6nceden \u00e7ekip, MX de\u011fi\u015fiminden sonra sadece son farklar\u0131 (delta) kopyalars\u0131n\u0131z.<\/p>\n<h3><span id=\"4_MX_cutover_MX_kayitlarini_Google_Workspace8217e_yonlendirme\">4. MX cutover: MX kay\u0131tlar\u0131n\u0131 Google Workspace&#8217;e y\u00f6nlendirme<\/span><\/h3>\n<p>\u0130lk senkronizasyon tamamland\u0131ktan ve test hesaplar\u0131yla deneme yapt\u0131ktan sonra ana ge\u00e7i\u015fe haz\u0131rs\u0131n\u0131z.<\/p>\n<ol>\n<li>DNS panelinizde domain\u2019in MX kay\u0131tlar\u0131n\u0131 Google Workspace\u2019in \u00f6nerdi\u011fi de\u011ferlere g\u00fcncelleyin.<\/li>\n<li>\u00d6nceden TTL\u2019i 300-600 sn\u2019e d\u00fc\u015f\u00fcrd\u00fcyseniz, \u00e7o\u011fu istemci birka\u00e7 dakika i\u00e7inde yeni MX\u2019leri g\u00f6recektir.<\/li>\n<li>Google Workspace Migration arac\u0131yla bir <strong>ikinci senkronizasyon<\/strong> (delta sync) \u00e7al\u0131\u015ft\u0131r\u0131n. Bu, MX de\u011fi\u015fiminden \u00f6nce ve hemen sonra gelen e-postalar\u0131 da yeni kutulara \u00e7eker.<\/li>\n<li>cPanel taraf\u0131nda webmail\u2019e girerek yeni e-posta ak\u0131\u015f\u0131n\u0131n oraya gelmedi\u011finden emin olun. Gelen varsa manuel veya ikinci bir IMAP sync ile aktar\u0131n.<\/li>\n<\/ol>\n<h3><span id=\"5_SPF_DKIM_ve_DMARC_guncellemeleri\">5. SPF, DKIM ve DMARC g\u00fcncellemeleri<\/span><\/h3>\n<p>MX de\u011fi\u015fimiyle ayn\u0131 zaman diliminde kimlik do\u011frulama kay\u0131tlar\u0131n\u0131 da g\u00fcncellemelisiniz:<\/p>\n<ul>\n<li>SPF kayd\u0131n\u0131za Google Workspace\u2019in \u00f6nerdi\u011fi <code>include:<\/code> ifadesini ekleyin veya kay\u0131t bo\u015fsa s\u0131f\u0131rdan olu\u015fturun.<\/li>\n<li>Google Workspace \u00fczerinde DKIM anahtar\u0131n\u0131 \u00fcretin ve DNS\u2019e TXT kayd\u0131 olarak ekleyin.<\/li>\n<li>DMARC kayd\u0131n\u0131z\u0131 \u00f6nce <code>p=none<\/code> (sadece raporla) modunda ba\u015flat\u0131p, ak\u0131\u015f\u0131 g\u00f6zlemledikten sonra <code>quarantine<\/code> veya <code>reject<\/code> moduna \u00e7ekebilirsiniz.<\/li>\n<\/ul>\n<p>Bu a\u015famadan sonra, e-posta kimlik do\u011frulaman\u0131z\u0131n sa\u011fl\u0131kl\u0131 \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131, daha \u00f6nce bahsetti\u011fimiz <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 izleme ve kurtarma rehberi<\/a>ndeki ara\u00e7larla da test edebilirsiniz.<\/p>\n<h3><span id=\"6_Eski_cPanel_altyapisini_ne_zaman_kapatmali\">6. Eski cPanel altyap\u0131s\u0131n\u0131 ne zaman kapatmal\u0131?<\/span><\/h3>\n<p>Bizim sahadaki \u00f6nerimiz \u015fu: cPanel\u2019deki e-posta hesaplar\u0131n\u0131 ve hizmeti en az <strong>7-14 g\u00fcn<\/strong> daha a\u00e7\u0131k tutun.<\/p>\n<ul>\n<li>Bu s\u00fcrede webmail\u2019e arada bir girip yeni e-posta d\u00fc\u015f\u00fcp d\u00fc\u015fmedi\u011fini kontrol edin.<\/li>\n<li>Hi\u00e7 e-posta gelmedi\u011finden emin olduktan sonra, son bir tam IMAP sync \u00e7ekebilir ve cPanel taraf\u0131ndaki kutular\u0131 dondurabilirsiniz.<\/li>\n<\/ul>\n<h2><span id=\"Senaryo_2_cPanel8217den_Microsoft_3658217e_Gecis\">Senaryo 2: cPanel&#8217;den Microsoft 365&#8217;e Ge\u00e7i\u015f<\/span><\/h2>\n<p>Bu senaryonun mant\u0131\u011f\u0131, Google Workspace ge\u00e7i\u015fine \u00e7ok benzer; fark, kulland\u0131\u011f\u0131n\u0131z migration ara\u00e7lar\u0131 ve baz\u0131 DNS kay\u0131t detaylar\u0131d\u0131r.<\/p>\n<h3><span id=\"1_Microsoft_365_uzerinde_domain_ve_kullanicilari_kurma\">1. Microsoft 365 \u00fczerinde domain ve kullan\u0131c\u0131lar\u0131 kurma<\/span><\/h3>\n<ul>\n<li>Microsoft 365 y\u00f6netim panelinde domain\u2019i ekleyin.<\/li>\n<li>TXT do\u011frulama kayd\u0131n\u0131 DNS\u2019e girin; MX kay\u0131tlar\u0131n\u0131 hen\u00fcz de\u011fi\u015ftirmeyin.<\/li>\n<li>Kullan\u0131c\u0131 hesaplar\u0131n\u0131 olu\u015fturun, lisanslar\u0131 atay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"2_Migration_endpoint_ve_batch_migration\">2. Migration endpoint ve batch migration<\/span><\/h3>\n<p>Microsoft 365 taraf\u0131nda IMAP Migration i\u00e7in bir &#8220;migration endpoint&#8221; olu\u015fturman\u0131z gerekir:<\/p>\n<ol>\n<li>Kaynak sunucu olarak cPanel e-posta sunucunuzun hostname\u2019ini girin.<\/li>\n<li>IMAP portu, g\u00fcvenlik t\u00fcr\u00fc ve ba\u011flant\u0131 testlerini ge\u00e7in.<\/li>\n<li>Kullan\u0131c\u0131 e\u015fle\u015ftirmeleri i\u00e7in CSV dosyas\u0131 haz\u0131rlay\u0131n (eski e-posta, kullan\u0131c\u0131 ad\u0131, parola, yeni e-posta).<\/li>\n<li>Migration batch\u2019leri olu\u015fturarak hesaplar\u0131 gruplar halinde ta\u015f\u0131y\u0131n (\u00f6rne\u011fin departman bazl\u0131).<\/li>\n<\/ol>\n<h3><span id=\"3_MX_degisimi_ve_SPFDKIM_ayarlari\">3. MX de\u011fi\u015fimi ve SPF\/DKIM ayarlar\u0131<\/span><\/h3>\n<p>\u0130lk batch\u2019ler ba\u015far\u0131l\u0131 olduysa, s\u0131ra ana MX de\u011fi\u015fimine gelir:<\/p>\n<ul>\n<li>MX kay\u0131tlar\u0131n\u0131 Microsoft 365\u2019in verdi\u011fi adrese y\u00f6nlendirin.<\/li>\n<li>SPF kayd\u0131n\u0131za Microsoft 365\u2019in <code>include:<\/code> ifadesini ekleyin.<\/li>\n<li>Microsoft 365 \u00fczerinden DKIM\u2019i aktif edin, DNS\u2019e ilgili CNAME\/TXT kay\u0131tlar\u0131n\u0131 ekleyin.<\/li>\n<li>DMARC kayd\u0131n\u0131 \u00f6nce <code>none<\/code>, sonra kademeli olarak <code>reject<\/code> seviyesine ta\u015f\u0131y\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"4_Outlook_ve_mobil_istemcilerin_yeniden_yapilandirilmasi\">4. Outlook ve mobil istemcilerin yeniden yap\u0131land\u0131r\u0131lmas\u0131<\/span><\/h3>\n<p>Microsoft 365 ge\u00e7i\u015flerinde en \u00e7ok zaman alan i\u015flerden biri, \u00f6zellikle eski Outlook profillerini temizleyip yeni profilleri tan\u0131mlamakt\u0131r.<\/p>\n<ul>\n<li>Modern Outlook s\u00fcr\u00fcmleri, Autodiscover ile \u00e7o\u011fu ayar\u0131 otomatik bulur.<\/li>\n<li>Eski profillerde OST\/PST dosyalar\u0131n\u0131 yedeklemeyi unutmay\u0131n.<\/li>\n<li>Mobil cihazlarda (iOS\/Android) yeni hesaplar\u0131 Exchange\/Office 365 tipi olarak ekleyin.<\/li>\n<\/ul>\n<p>Bu a\u015famada, e-posta taraf\u0131n\u0131 ta\u015f\u0131ma s\u00fcrecini; genel altyap\u0131 ge\u00e7i\u015flerinizle (\u00f6rne\u011fin web sitenizin yeni sunucuya ta\u015f\u0131nmas\u0131) birlikte planl\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/paylasimli-hostingden-vpse-nasil-gecersin-kesintisiz-tasima-icin-sicacik-bir-kontrol-listesi\/\">payla\u015f\u0131ml\u0131 hosting\u2019den VPS\u2019e kesintisiz ge\u00e7i\u015f rehberimizdeki<\/a> &#8220;kademeli ge\u00e7i\u015f&#8221; yakla\u015f\u0131m\u0131n\u0131 da uygulayabilirsiniz.<\/p>\n<h2><span id=\"Senaryo_3_Google_Workspace_Microsoft_365_Arasi_Gecis\">Senaryo 3: Google Workspace \u2194 Microsoft 365 Aras\u0131 Ge\u00e7i\u015f<\/span><\/h2>\n<p>Bu ge\u00e7i\u015fte iki u\u00e7ta da &#8220;bulut e-posta&#8221; hizmeti oldu\u011fu i\u00e7in, i\u015fleri biraz daha dikkatli planlamak gerekiyor. \u00c7\u00fcnk\u00fc her iki tarafta da geli\u015fmi\u015f g\u00fcvenlik, kimlik do\u011frulama ve spam filtreleri aktif.<\/p>\n<h3><span id=\"1_Gecis_modelini_belirleyin_Big_bang_mi_kademeli_mi\">1. Ge\u00e7i\u015f modelini belirleyin: Big bang mi, kademeli mi?<\/span><\/h3>\n<ul>\n<li><strong>Big bang:<\/strong> Bir gece herkes tek seferde yeni platforma ge\u00e7er. Basit yap\u0131larda i\u015fe yarar ama risklidir.<\/li>\n<li><strong>Kademeli ge\u00e7i\u015f:<\/strong> Departman departman veya domain bazl\u0131 ge\u00e7i\u015f yap\u0131l\u0131r, bir s\u00fcre &#8220;hibrit&#8221; d\u00f6nem ya\u015fan\u0131r.<\/li>\n<\/ul>\n<p>Bizim sahada daha \u00e7ok \u00f6nerdi\u011fimiz model, kademeli ve hibrit senaryolard\u0131r. \u00d6zellikle 50+ kullan\u0131c\u0131l\u0131 ortamlarda, ayn\u0131 g\u00fcn t\u00fcm ekibi ta\u015f\u0131mak yerine, en az\u0131ndan pilot birimlerle ba\u015flamay\u0131 tavsiye ediyoruz.<\/p>\n<h3><span id=\"2_Veri_migrasyonu_API_tabanli_veya_IMAP_tabanli\">2. Veri migrasyonu: API tabanl\u0131 veya IMAP tabanl\u0131<\/span><\/h3>\n<p>Google Workspace ve Microsoft 365 aras\u0131nda iki ana veri aktar\u0131m y\u00f6ntemi vard\u0131r:<\/p>\n<ul>\n<li>Platformlar\u0131n sundu\u011fu <strong>yerel migration ara\u00e7lar\u0131<\/strong> ve API tabanl\u0131 \u00e7\u00f6z\u00fcmler,<\/li>\n<li>Eski usul <strong>IMAP tabanl\u0131<\/strong> senkronizasyon.<\/li>\n<\/ul>\n<p>API tabanl\u0131 y\u00f6ntemler \u00e7o\u011fu zaman daha h\u0131zl\u0131 ve g\u00fcvenilir olsa da, yetkilendirme ve kapsam izinleri dikkatli kurgulanmal\u0131d\u0131r. IMAP tabanl\u0131 ta\u015f\u0131ma, daha sade ama biraz daha uzun s\u00fcrebilir.<\/p>\n<h3><span id=\"3_Mail_flow_kurallari_ve_gecici_yonlendirmeler\">3. Mail flow kurallar\u0131 ve ge\u00e7ici y\u00f6nlendirmeler<\/span><\/h3>\n<p>Hibrit ge\u00e7i\u015flerde en kritik konulardan biri, iki sistem aras\u0131ndaki posta ak\u0131\u015f\u0131n\u0131 do\u011fru kurmakt\u0131r.<\/p>\n<ul>\n<li>\u00d6rne\u011fin Google Workspace\u2019ten Microsoft 365\u2019e ge\u00e7iyorsan\u0131z, belirli kullan\u0131c\u0131lara gelen e-postalar\u0131n ge\u00e7i\u015f s\u00fcresince di\u011fer tarafa y\u00f6nlendirilmesini sa\u011flayacak kurallar tan\u0131mlanabilir.<\/li>\n<li>Bu sayede, DNS taraf\u0131ndaki MX de\u011fi\u015fimi yap\u0131lmadan bile, ge\u00e7ici bir s\u00fcre i\u00e7in &#8220;arka planda&#8221; yeni sisteme akan bir posta trafi\u011fi kurabilirsiniz.<\/li>\n<\/ul>\n<p>Bu t\u00fcr karma senaryolarda mutlaka SPF, DKIM ve DMARC etkilerini iyi okumak gerekir; \u00e7\u00fcnk\u00fc y\u00f6nlendirmeler SPF\u2019yi bozabilir. Bu konuyu <a href=\"https:\/\/www.dchost.com\/blog\/e%E2%80%91posta-yonlendirmede-spf-dmarc-neden-kiriliyor-srs-ve-arc-ile-nasil-tatli-tatli-onarirsin\/\">e-posta y\u00f6nlendirmede SPF\/DMARC neden k\u0131r\u0131l\u0131yor?<\/a> yaz\u0131m\u0131zda detayl\u0131 anlatt\u0131k.<\/p>\n<h3><span id=\"4_Takvim_kisi_ve_paylasimli_kutular\">4. Takvim, ki\u015fi ve payla\u015f\u0131ml\u0131 kutular<\/span><\/h3>\n<p>E-posta i\u00e7eri\u011fi kadar \u00f6nemli olan bir di\u011fer ba\u015fl\u0131k da takvimler, ki\u015filer ve payla\u015f\u0131ml\u0131 posta kutular\u0131d\u0131r.<\/p>\n<ul>\n<li>Payla\u015f\u0131ml\u0131 posta kutular\u0131n\u0131n yeni sistemdeki kar\u015f\u0131l\u0131klar\u0131n\u0131 \u00f6nceden olu\u015fturun.<\/li>\n<li>Takvim payla\u015f\u0131m izinlerini ve toplant\u0131 odas\u0131 (resource mailbox) yap\u0131lar\u0131n\u0131 yeniden kurgulay\u0131n.<\/li>\n<li>Mobil cihazlarda takvim ve ki\u015filer i\u00e7in kullan\u0131lan senkronizasyon y\u00f6ntemlerini (Exchange, CardDAV, CalDAV vb.) g\u00f6zden ge\u00e7irin.<\/li>\n<\/ul>\n<h2><span id=\"Senaryo_4_Google_Workspace_Microsoft_3658217ten_cPanel_veya_Kendi_Sunucunuza_Donus\">Senaryo 4: Google Workspace \/ Microsoft 365&#8217;ten cPanel veya Kendi Sunucunuza D\u00f6n\u00fc\u015f<\/span><\/h2>\n<p>Bazen de tam tersi bir ge\u00e7i\u015f g\u00f6rmekteyiz: Maliyet, veri egemenli\u011fi veya \u00f6zel g\u00fcvenlik gereksinimleri nedeniyle Google Workspace ya da Microsoft 365\u2019ten ayr\u0131l\u0131p cPanel tabanl\u0131 bir \u00e7\u00f6z\u00fcme veya tamamen kendi <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\/<a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>suna kurulu bir posta sunucusuna ge\u00e7mek isteyen ekipler.<\/p>\n<h3><span id=\"1_Hedef_mimariyi_netlestirin\">1. Hedef mimariyi netle\u015ftirin<\/span><\/h3>\n<p>Burada iki opsiyon vard\u0131r:<\/p>\n<ul>\n<li><strong>cPanel tabanl\u0131 e-posta:<\/strong> Y\u00f6netimi kolay, k\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli i\u015fletmeler i\u00e7in pratik \u00e7\u00f6z\u00fcm.<\/li>\n<li><strong>VPS veya dedicated \u00fczerinde kendi MTA\u2019n\u0131z:<\/strong> Postfix + Dovecot + rspamd gibi bile\u015fenlerle tamamen size \u00f6zel bir altyap\u0131. Bu yolu tercih ediyorsan\u0131z, detayl\u0131 kurulum ve teslim edilebilirlik ayarlar\u0131 i\u00e7in <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 rehberimizi<\/a> mutlaka inceleyin.<\/li>\n<\/ul>\n<p>DCHost taraf\u0131nda, bu t\u00fcr senaryolar i\u00e7in hem cPanel hosting paketleri hem de kendi e-posta sunucunuzu kurabilece\u011finiz VPS ve dedicated sunucu altyap\u0131lar\u0131 sunuyoruz. B\u00f6ylece ihtiyac\u0131n\u0131z olan seviye kadar kontrol\u00fc elinizde tutabilirsiniz.<\/p>\n<h3><span id=\"2_Kullanici_ve_veri_tasima\">2. Kullan\u0131c\u0131 ve veri ta\u015f\u0131ma<\/span><\/h3>\n<p>Google Workspace veya Microsoft 365\u2019ten \u00e7\u0131karken de IMAP tabanl\u0131 veri ta\u015f\u0131ma temel y\u00f6ntemdir:<\/p>\n<ul>\n<li>cPanel\u2019de veya kendi posta sunucunuzda \u00f6nceden t\u00fcm kullan\u0131c\u0131 kutular\u0131n\u0131 olu\u015fturun.<\/li>\n<li>IMAP sync arac\u0131yla Google\/Microsoft taraf\u0131ndaki posta kutular\u0131n\u0131 yeni kutulara bire bir kopyalay\u0131n.<\/li>\n<li>\u0130lk tam kopyadan sonra, MX de\u011fi\u015fimine yak\u0131n d\u00f6nemde bir veya iki kez delta senkronizasyonu yap\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"3_MX_ve_SPFin_kontrollu_degisimi\">3. MX ve SPF\u2019in kontroll\u00fc de\u011fi\u015fimi<\/span><\/h3>\n<p>Google Workspace \/ Microsoft 365\u2019ten \u00e7\u0131karken yapman\u0131z gerekenler:<\/p>\n<ol>\n<li>Domain\u2019in MX kay\u0131tlar\u0131n\u0131 yeni cPanel veya posta sunucunuza y\u00f6nlendirin.<\/li>\n<li>SPF kayd\u0131ndan Google\/Microsoft ile ilgili <code>include:<\/code> ifadelerini kald\u0131r\u0131n, yerine yeni sunucunuzu tan\u0131mlay\u0131n (IP veya hostname bazl\u0131).<\/li>\n<li>Yeni sunucunuzda DKIM anahtarlar\u0131 \u00fcretip DNS\u2019e ekleyin. DMARC kayd\u0131n\u0131 da yeni duruma g\u00f6re g\u00fcncelleyin.<\/li>\n<\/ol>\n<p>Burada en s\u0131k yap\u0131lan hata, MX\u2019i de\u011fi\u015ftirdikten hemen sonra Google\/Microsoft taraf\u0131ndaki domain yap\u0131land\u0131rmas\u0131n\u0131 tamamen silmek. Bizim \u00f6nerimiz, en az <strong>1-2 hafta<\/strong> bu servisleri &#8220;pasif&#8221; ama yap\u0131land\u0131rma bozulmadan tutmak; b\u00f6ylece gecikmeli DNS veya istemci \u00f6nbelleklerinden gelecek son e-postalar\u0131 da garantilemi\u015f olursunuz.<\/p>\n<h2><span id=\"Kontrol_Listesi_Sifir_Kesinti_E-Posta_Tasima_Adimlari\">Kontrol Listesi: S\u0131f\u0131r Kesinti E-Posta Ta\u015f\u0131ma Ad\u0131mlar\u0131<\/span><\/h2>\n<p>T\u00fcm senaryolar\u0131 \u00f6zetleyen, sahada ger\u00e7ekten uygulayabilece\u011finiz bir kontrol listesini toparlayal\u0131m. Bunu kendi ge\u00e7i\u015f plan\u0131n\u0131z i\u00e7in checklist olarak kullanabilirsiniz.<\/p>\n<ol>\n<li><strong>Envanter:<\/strong> Domain\u2019ler, kullan\u0131c\u0131lar, alias\u2019lar, forwarding kurallar\u0131, payla\u015f\u0131ml\u0131 kutular, toplam veri boyutu.<\/li>\n<li><strong>DNS eri\u015fimi:<\/strong> Domain DNS paneli, y\u00f6netici hesaplar\u0131, kim hangi de\u011fi\u015fikli\u011fi ne zaman yapacak?<\/li>\n<li><strong>TTL d\u00fc\u015f\u00fcrme:<\/strong> Ge\u00e7i\u015ften 24-48 saat \u00f6nce MX ve ilgili TXT kay\u0131tlar\u0131n\u0131n TTL\u2019ini 300-600 sn\u2019e indirin.<\/li>\n<li><strong>Yeni altyap\u0131y\u0131 haz\u0131rlama:<\/strong> Google Workspace \/ Microsoft 365 \/ cPanel \/ kendi posta sunucunuz \u00fczerinde domain ve kullan\u0131c\u0131 kutular\u0131n\u0131 olu\u015fturun.<\/li>\n<li><strong>Kimlik do\u011frulama kay\u0131tlar\u0131n\u0131 tasarlama:<\/strong> SPF, DKIM, DMARC, rDNS plan\u0131n\u0131 \u00f6nceden ka\u011f\u0131da d\u00f6k\u00fcn; hangi IP\u2019ler hangi alanlar\u0131 imzalayacak?<\/li>\n<li><strong>\u0130lk veri senkronizasyonu:<\/strong> IMAP veya yerel migration ara\u00e7lar\u0131yla mevcut kutular\u0131 yeni sisteme kopyalay\u0131n.<\/li>\n<li><strong>Pilot kullan\u0131c\u0131larla test:<\/strong> En az 2-3 kullan\u0131c\u0131y\u0131 u\u00e7tan uca ta\u015f\u0131y\u0131p, hem g\u00f6nderme hem alma hem de spam durumlar\u0131n\u0131 test edin.<\/li>\n<li><strong>MX cutover zaman\u0131:<\/strong> Yo\u011fun trafi\u011fin nispeten d\u00fc\u015f\u00fck oldu\u011fu bir zaman dilimini se\u00e7in (genelde ak\u015fam saatleri veya hafta sonu).<\/li>\n<li><strong>MX de\u011fi\u015fimi ve anl\u0131k izleme:<\/strong> MX\u2019leri yeni sisteme y\u00f6nlendirdikten sonra, log\u2019lar\u0131 ve posta ak\u0131\u015f\u0131n\u0131 1-2 saat boyunca yak\u0131ndan izleyin.<\/li>\n<li><strong>Delta senkronizasyon:<\/strong> MX de\u011fi\u015fiminden sonra bir kez daha senkronizasyon \u00e7al\u0131\u015ft\u0131rarak, arada kalan son e-postalar\u0131 da ta\u015f\u0131y\u0131n.<\/li>\n<li><strong>\u0130stemci taraf\u0131 d\u00fczeltmeleri:<\/strong> Outlook profilleri, mobil hesaplar, imzalar, payla\u015f\u0131ml\u0131 kutu izinleri gibi kullan\u0131c\u0131 taraf\u0131 ayarlar\u0131n\u0131 finalize edin.<\/li>\n<li><strong>Eski altyap\u0131y\u0131 bekletme:<\/strong> Eski posta sunucusunu 7-14 g\u00fcn boyunca pasif ama eri\u015filebilir tutun; gerekirse gelen son e-postalar\u0131 manuel veya otomatik ta\u015f\u0131y\u0131n.<\/li>\n<li><strong>Log ve blacklist kontrol\u00fc:<\/strong> Yeni altyap\u0131n\u0131z\u0131n IP\u2019lerinin kara listelerde olup olmad\u0131\u011f\u0131n\u0131 ve SPF\/DKIM\/DMARC raporlar\u0131n\u0131 d\u00fczenli kontrol edin.<\/li>\n<\/ol>\n<p>Bu ad\u0131mlar\u0131n tamam\u0131n\u0131 disiplinli \u015fekilde uygularsan\u0131z, &#8220;s\u0131f\u0131r kesinti&#8221;ye \u00e7ok yakla\u015fan bir ge\u00e7i\u015f ger\u00e7ekle\u015ftirirsiniz. Kalan k\u00fc\u00e7\u00fck sorunlar da genellikle tekil kullan\u0131c\u0131 ayarlar\u0131na veya yerel istemci \u00f6nbelleklerine dair olacakt\u0131r.<\/p>\n<h2><span id=\"DCHost_ile_E-Posta_Gecisini_Daha_Guvenli_Yurutmek\">DCHost ile E-Posta Ge\u00e7i\u015fini Daha G\u00fcvenli Y\u00fcr\u00fctmek<\/span><\/h2>\n<p>E-posta altyap\u0131s\u0131 ge\u00e7i\u015fi, teknik olarak detayl\u0131 ama do\u011fru planland\u0131\u011f\u0131nda olduk\u00e7a kontroll\u00fc y\u00fcr\u00fct\u00fclebilen bir s\u00fcre\u00e7. DCHost olarak hem cPanel tabanl\u0131 e-posta hizmetlerinde, hem de kendi posta sunucusunu kurmak isteyen m\u00fc\u015fterilerimiz i\u00e7in VPS ve dedicated sunucu altyap\u0131lar\u0131nda y\u00fczlerce ge\u00e7i\u015f operasyonu g\u00f6rd\u00fck. Ortak ders \u015fu: <strong>DNS, kimlik do\u011frulama ve veri senkronizasyonu i\u00e7in net bir plan\u0131 olmayan hi\u00e7bir ge\u00e7i\u015f sorunsuz bitmiyor.<\/strong><\/p>\n<p>E\u011fer siz de Google Workspace, Microsoft 365 veya cPanel aras\u0131nda ge\u00e7i\u015f planl\u0131yorsan\u0131z ve kafan\u0131zda &#8220;MX\u2019i ne zaman de\u011fi\u015ftirmeliyim, SPF\u2019yi nas\u0131l yeniden yazaca\u011f\u0131m, eski kutular\u0131 nas\u0131l ta\u015f\u0131yaca\u011f\u0131m?&#8221; gibi sorular dola\u015f\u0131yorsa, bu yaz\u0131daki kontrol listesini kendi durumunuza uyarlayarak ba\u015flayabilirsiniz. Daha karma\u015f\u0131k senaryolarda (\u00e7oklu domain, hibrit yap\u0131, kendi MTA\u2019n\u0131z\u0131 kurmak gibi) DCHost taraf\u0131ndaki ekibimiz, domain y\u00f6netiminden VPS\/dedicated sunucu kurulumuna, <a href=\"https:\/\/www.dchost.com\/blog\/3-2-1-yedekleme-stratejisi-neden-ise-yariyor-cpanel-plesk-ve-vpste-otomatik-yedekleri-nasil-kurarsin\/\">otomatik yedekleme stratejilerine<\/a> kadar t\u00fcm altyap\u0131y\u0131 birlikte tasarlayabilir.<\/p>\n<p>Sonraki ad\u0131m olarak; mevcut e-posta altyap\u0131n\u0131z\u0131, DNS kay\u0131tlar\u0131n\u0131z\u0131 ve hedef mimarinizi k\u0131sa bir dok\u00fcman haline getirip bizimle payla\u015fman\u0131z yeterli. Beraber, i\u015finizin ritmini bozmadan, sakin ve \u00f6ng\u00f6r\u00fclebilir bir e-posta ge\u00e7i\u015f plan\u0131 \u00e7\u0131karabiliriz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>E-posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131mak, bir \u015firket i\u00e7in sadece teknik bir operasyon de\u011fil, i\u015f s\u00fcreklili\u011fini do\u011frudan etkileyen kritik bir ad\u0131md\u0131r. Sat\u0131\u015f ekibiniz m\u00fc\u015fteri tekliflerini, hukuk ekibiniz s\u00f6zle\u015fmeleri, operasyon ekibiniz g\u00fcnl\u00fck i\u015f ak\u0131\u015f\u0131n\u0131 e-posta \u00fczerinden y\u00fcr\u00fct\u00fcyor. Dolay\u0131s\u0131yla Google Workspace, Microsoft 365 veya cPanel tabanl\u0131 bir e-posta altyap\u0131s\u0131ndan di\u011ferine ge\u00e7erken ya\u015fanacak birka\u00e7 saatlik kesinti bile hem itibar hem de [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2755,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2754","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\/2754","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=2754"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2754\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2755"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2754"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2754"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2754"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}