{"id":4350,"date":"2026-02-03T15:21:18","date_gmt":"2026-02-03T12:21:18","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/cpanelden-google-workspace-microsoft-365e-e-posta-tasima-rehberi-imap-sync-ile-kesintisiz-gecis\/"},"modified":"2026-02-03T15:21:18","modified_gmt":"2026-02-03T12:21:18","slug":"cpanelden-google-workspace-microsoft-365e-e-posta-tasima-rehberi-imap-sync-ile-kesintisiz-gecis","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/cpanelden-google-workspace-microsoft-365e-e-posta-tasima-rehberi-imap-sync-ile-kesintisiz-gecis\/","title":{"rendered":"cPanel\u2019den Google Workspace \/ Microsoft 365\u2019e E\u2011Posta Ta\u015f\u0131ma Rehberi (IMAP Sync ile Kesintisiz Ge\u00e7i\u015f)"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>cPanel \u00fczerinde y\u0131llard\u0131r \u00e7al\u0131\u015fan bir e\u2011posta altyap\u0131s\u0131n\u0131 Google Workspace veya Microsoft 365\u2019e ta\u015f\u0131mak, ka\u011f\u0131t \u00fczerinde basit g\u00f6r\u00fcnebilir; ancak i\u015f kesintisiz ge\u00e7i\u015fe ve veri kayb\u0131 ya\u015famamaya gelince, k\u00fc\u00e7\u00fck hatalar bile b\u00fcy\u00fck sorunlara d\u00f6n\u00fc\u015febilir. DCHost ekibi olarak hem kendi altyap\u0131m\u0131z i\u00e7inde hem de m\u00fc\u015fterilerimizin projelerinde s\u0131k s\u0131k cPanel \u2192 bulut e\u2011posta ge\u00e7i\u015fleri yap\u0131yoruz ve pratikte en \u00e7ok i\u015fe yarayan yakla\u015f\u0131m\u0131n, iyi planlanm\u0131\u015f bir <strong>IMAP senkronizasyon (IMAP sync)<\/strong> stratejisi oldu\u011funu g\u00f6r\u00fcyoruz.<\/p>\n<p>Bu rehberde; cPanel\u2019den Google Workspace \/ Microsoft 365\u2019e ge\u00e7erken nelere dikkat etmeniz gerekti\u011fini, IMAP sync ile posta kutular\u0131n\u0131 nas\u0131l ta\u015f\u0131yaca\u011f\u0131n\u0131z\u0131, DNS taraf\u0131nda MX \/ SPF \/ DKIM \/ DMARC ayarlar\u0131n\u0131 nas\u0131l kurgulaman\u0131z gerekti\u011fini ve ge\u00e7i\u015fi <strong>neredeyse s\u0131f\u0131r kesinti<\/strong> ile nas\u0131l tamamlayabilece\u011finizi ad\u0131m ad\u0131m anlataca\u011f\u0131z. Amac\u0131m\u0131z, hem teknik ekibi hem de teknik detaya uzak i\u015fletme sahiplerini rahatlatacak kadar net ve uygulanabilir bir yol haritas\u0131 sunmak.<\/p>\n<p>E\u011fer hen\u00fcz hangi modeli se\u00e7ece\u011finize karar vermediyseniz, yani e\u2011postalar\u0131n\u0131z\u0131n tamamen hosting \u00fczerinde mi, yoksa Google Workspace \/ Microsoft 365 gibi servislerde mi kalmas\u0131 gerekti\u011fini tart\u0131\u015f\u0131yorsan\u0131z, \u00f6nce mutlaka <a href=\"https:\/\/www.dchost.com\/blog\/kendi-hosting-e-postaniz-mi-google-workspace-microsoft-365-mi\/\">kendi hosting e\u2011postan\u0131z m\u0131 Google Workspace \/ Microsoft 365 mi sorusunu teknik ve mali a\u00e7\u0131dan ele ald\u0131\u011f\u0131m\u0131z yaz\u0131m\u0131za<\/a> g\u00f6z atman\u0131z\u0131 \u00f6neririz. Bu makale ise, karar\u0131n\u0131 vermi\u015f ve art\u0131k cPanel\u2019den bulut e\u2011posta servislerine <strong>temiz, kontroll\u00fc ve geri d\u00f6n\u00fc\u015f\u00fc m\u00fcmk\u00fcn<\/strong> bir ge\u00e7i\u015f yapmak isteyenler i\u00e7in.<\/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=\"#Neden_Google_Workspace_Microsoft_365e_Geciliyor\"><span class=\"toc_number toc_depth_1\">1<\/span> Neden Google Workspace \/ Microsoft 365\u2019e Ge\u00e7iliyor?<\/a><\/li><li><a href=\"#Tasima_Oncesi_Planlama_ve_Envanter_Calismasi\"><span class=\"toc_number toc_depth_1\">2<\/span> Ta\u015f\u0131ma \u00d6ncesi Planlama ve Envanter \u00c7al\u0131\u015fmas\u0131<\/a><ul><li><a href=\"#1_Tum_posta_kutularinin_ve_rolleri_listesi\"><span class=\"toc_number toc_depth_2\">2.1<\/span> 1. T\u00fcm posta kutular\u0131n\u0131n ve rolleri listesi<\/a><\/li><li><a href=\"#2_Boyut_analizi_ve_kota_plani\"><span class=\"toc_number toc_depth_2\">2.2<\/span> 2. Boyut analizi ve kota plan\u0131<\/a><\/li><li><a href=\"#3_Sifreler_kimlik_dogrulama_ve_guvenlik\"><span class=\"toc_number toc_depth_2\">2.3<\/span> 3. \u015eifreler, kimlik do\u011frulama ve g\u00fcvenlik<\/a><\/li><li><a href=\"#4_Kesintisiz_gecis_stratejisi\"><span class=\"toc_number toc_depth_2\">2.4<\/span> 4. Kesintisiz ge\u00e7i\u015f stratejisi<\/a><\/li><\/ul><\/li><li><a href=\"#cPanel_Tarafinda_Hazirlik_Hesaplar_Kotalar_ve_Yedekler\"><span class=\"toc_number toc_depth_1\">3<\/span> cPanel Taraf\u0131nda Haz\u0131rl\u0131k: Hesaplar, Kotalar ve Yedekler<\/a><ul><li><a href=\"#1_Tam_yedek_ve_gerektiginde_geri_donus_plani\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. Tam yedek ve gerekti\u011finde geri d\u00f6n\u00fc\u015f plan\u0131<\/a><\/li><li><a href=\"#2_IMAP_erisimini_ve_baglanti_sinirlarini_kontrol_edin\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. IMAP eri\u015fimini ve ba\u011flant\u0131 s\u0131n\u0131rlar\u0131n\u0131 kontrol edin<\/a><\/li><li><a href=\"#3_Kullanicilar_icin_klasor_duzeni_ve_temizlik\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. Kullan\u0131c\u0131lar i\u00e7in klas\u00f6r d\u00fczeni ve temizlik<\/a><\/li><\/ul><\/li><li><a href=\"#IMAP_Sync_Mantigi_Eski_Sunucudan_Bulut_Servise_Veri_Tasimak\"><span class=\"toc_number toc_depth_1\">4<\/span> IMAP Sync Mant\u0131\u011f\u0131: Eski Sunucudan Bulut Servise Veri Ta\u015f\u0131mak<\/a><ul><li><a href=\"#Tek_yonlu_guvenli_kopyalama\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Tek y\u00f6nl\u00fc, g\u00fcvenli kopyalama<\/a><\/li><li><a href=\"#Ornek_IMAP_sync_komutu_genel_mantik\"><span class=\"toc_number toc_depth_2\">4.2<\/span> \u00d6rnek IMAP sync komutu (genel mant\u0131k)<\/a><\/li><li><a href=\"#Performans_limitler_ve_hiz_planlamasi\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Performans, limitler ve h\u0131z planlamas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_Adim_cPanelden_Google_Workspace_Microsoft_365e_Tasima_Senaryosu\"><span class=\"toc_number toc_depth_1\">5<\/span> Ad\u0131m Ad\u0131m cPanel\u2019den Google Workspace \/ Microsoft 365\u2019e Ta\u015f\u0131ma Senaryosu<\/a><ul><li><a href=\"#1_Pilot_kullanici_ile_prova\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. Pilot kullan\u0131c\u0131 ile prova<\/a><\/li><li><a href=\"#2_Toplu_hesap_olusturma_ve_on_senkronizasyon\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. Toplu hesap olu\u015fturma ve \u00f6n senkronizasyon<\/a><\/li><li><a href=\"#3_DNS_cutovera_yakin_ikinci_delta_senkronizasyon\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. DNS cutover\u2019a yak\u0131n ikinci (delta) senkronizasyon<\/a><\/li><li><a href=\"#4_MX_SPF_ve_Autodiscover_Autodiscover_Autoconfig_degisiklikleri\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. MX, SPF ve Autodiscover \/ Autodiscover (Autoconfig) de\u011fi\u015fiklikleri<\/a><\/li><li><a href=\"#5_MX_degisikliginden_sonra_kisa_sureli_izleme_ve_son_senkronizasyon\"><span class=\"toc_number toc_depth_2\">5.5<\/span> 5. MX de\u011fi\u015fikli\u011finden sonra k\u0131sa s\u00fcreli izleme ve son senkronizasyon<\/a><\/li><li><a href=\"#6_Eski_cPanel_posta_kutularinin_yalnizca_okuma_modunda_tutulmasi\"><span class=\"toc_number toc_depth_2\">5.6<\/span> 6. Eski cPanel posta kutular\u0131n\u0131n yaln\u0131zca okuma modunda tutulmas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_ve_Kesintisiz_Gecis_MX_TTL_ve_Yol_Haritasi\"><span class=\"toc_number toc_depth_1\">6<\/span> DNS ve Kesintisiz Ge\u00e7i\u015f: MX, TTL ve Yol Haritas\u0131<\/a><\/li><li><a href=\"#Guvenlik_ve_Teslim_Edilebilirlik_SPF_DKIM_DMARC_ve_MTASTS\"><span class=\"toc_number toc_depth_1\">7<\/span> G\u00fcvenlik ve Teslim Edilebilirlik: SPF, DKIM, DMARC ve MTA\u2011STS<\/a><ul><li><a href=\"#SPF_ve_DKIMi_dogru_kurmak\"><span class=\"toc_number toc_depth_2\">7.1<\/span> SPF ve DKIM\u2019i do\u011fru kurmak<\/a><\/li><li><a href=\"#DMARC_politikasi_ve_raporlarini_takip_etmek\"><span class=\"toc_number toc_depth_2\">7.2<\/span> DMARC politikas\u0131 ve raporlar\u0131n\u0131 takip etmek<\/a><\/li><li><a href=\"#Ek_guvenlik_katmanlari_MTASTS_TLSRPT_DANE\"><span class=\"toc_number toc_depth_2\">7.3<\/span> Ek g\u00fcvenlik katmanlar\u0131: MTA\u2011STS, TLS\u2011RPT, DANE<\/a><\/li><\/ul><\/li><li><a href=\"#Sik_Yapilan_Hatalar_ve_DCHost_Ekibinin_Onerdigi_Iyi_Uygulamalar\"><span class=\"toc_number toc_depth_1\">8<\/span> S\u0131k Yap\u0131lan Hatalar ve DCHost Ekibinin \u00d6nerdi\u011fi \u0130yi Uygulamalar<\/a><ul><li><a href=\"#1_IMAP_sync_yerine_PSTindiryukselt_ile_ugrasmak\"><span class=\"toc_number toc_depth_2\">8.1<\/span> 1. IMAP sync yerine PST\/indir\u2011y\u00fckselt ile u\u011fra\u015fmak<\/a><\/li><li><a href=\"#2_DNSi_erken_veya_plansiz_degistirmek\"><span class=\"toc_number toc_depth_2\">8.2<\/span> 2. DNS\u2019i erken veya plans\u0131z de\u011fi\u015ftirmek<\/a><\/li><li><a href=\"#3_SPFDKIMi_ihmal_etmek_ve_spam_sikayeti_almak\"><span class=\"toc_number toc_depth_2\">8.3<\/span> 3. SPF\/DKIM\u2019i ihmal etmek ve spam \u015fikayeti almak<\/a><\/li><li><a href=\"#4_Kullanici_iletisimini_unutarak_panik_yaratmak\"><span class=\"toc_number toc_depth_2\">8.4<\/span> 4. Kullan\u0131c\u0131 ileti\u015fimini unutarak panik yaratmak<\/a><\/li><li><a href=\"#5_Eski_sistemi_cok_erken_kapatmak\"><span class=\"toc_number toc_depth_2\">8.5<\/span> 5. Eski sistemi \u00e7ok erken kapatmak<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_DCHost_ile_Kontrollu_Seffaf_ve_Geri_Donusu_Mumkun_Bir_Gecis\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7: DCHost ile Kontroll\u00fc, \u015eeffaf ve Geri D\u00f6n\u00fc\u015f\u00fc M\u00fcmk\u00fcn Bir Ge\u00e7i\u015f<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Neden_Google_Workspace_Microsoft_365e_Geciliyor\">Neden Google Workspace \/ Microsoft 365\u2019e Ge\u00e7iliyor?<\/span><\/h2>\n<p>cPanel \u00fczerinde \u00e7al\u0131\u015fan klasik e\u2011posta sistemi, \u00f6zellikle web sitenizle ayn\u0131 hosting hesab\u0131nda oldu\u011fu i\u00e7in k\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli projelerde h\u00e2l\u00e2 olduk\u00e7a pratik. Buna ra\u011fmen bir\u00e7ok i\u015fletme, belirli bir olgunluk seviyesine geldi\u011finde e\u2011postas\u0131n\u0131 Google Workspace veya Microsoft 365 gibi hizmetlere ta\u015f\u0131may\u0131 tercih ediyor. Bunun ba\u015fl\u0131ca sebeplerini netle\u015ftirirsek, ge\u00e7i\u015f motivasyonunuz ve \u00f6ncelikleriniz de daha berrak hale gelir.<\/p>\n<p>\u00d6ne \u00e7\u0131kan motivasyonlar genellikle \u015funlar:<\/p>\n<ul>\n<li><strong>Daha g\u00fc\u00e7l\u00fc web aray\u00fcz\u00fc ve entegrasyonlar:<\/strong> Takvim, g\u00f6rev y\u00f6netimi, \u00e7evrim i\u00e7i ofis uygulamalar\u0131, Drive\/OneDrive entegrasyonlar\u0131 gibi ek \u00f6zellikler.<\/li>\n<li><strong>Mobil ve masa\u00fcst\u00fc istemcilerde sorunsuz deneyim:<\/strong> Otomatik yap\u0131land\u0131rma, kurumsal cihaz y\u00f6netimi, g\u00fcvenlik politikalar\u0131.<\/li>\n<li><strong>Daha iyi spam filtresi ve g\u00fcvenlik katmanlar\u0131:<\/strong> Geli\u015fmi\u015f anti\u2011spam, anti\u2011phishing, 2FA, oturum y\u00f6netimi, \u015f\u00fcpheli oturum uyar\u0131lar\u0131.<\/li>\n<li><strong>BT ekibinin y\u00fck\u00fcn\u00fcn azalmas\u0131:<\/strong> Disk, CPU, RAM, MTA y\u00f6netimi gibi konular\u0131 azaltarak e\u2011posta taraf\u0131n\u0131 k\u0131smen servis sa\u011flay\u0131c\u0131ya devretmek.<\/li>\n<li><strong>Uzun vadeli ar\u015fiv ve uyum gereksinimleri:<\/strong> Yasal saklama, e\u2011discovery, journaling, ar\u015fiv posta kutular\u0131 gibi ihtiya\u00e7lar.<\/li>\n<\/ul>\n<p>Bu avantajlar\u0131 al\u0131rken en b\u00fcy\u00fck kayg\u0131 ise \u015fu oluyor: \u201cMevcut cPanel mail\u2019lerim kaybolmadan, \u00e7al\u0131\u015fanlar\u0131m hi\u00e7bir \u015fey hissetmeden bu ge\u00e7i\u015fi nas\u0131l yapar\u0131m?\u201d \u0130\u015fte burada <strong>IMAP sync<\/strong> ve do\u011fru DNS planlamas\u0131, DCHost taraf\u0131nda da her projede uygulad\u0131\u011f\u0131m\u0131z kilit iki ara\u00e7 haline geliyor.<\/p>\n<h2><span id=\"Tasima_Oncesi_Planlama_ve_Envanter_Calismasi\">Ta\u015f\u0131ma \u00d6ncesi Planlama ve Envanter \u00c7al\u0131\u015fmas\u0131<\/span><\/h2>\n<p>Ba\u015far\u0131l\u0131 bir ge\u00e7i\u015fin %70\u2019i, asl\u0131nda <strong>ge\u00e7i\u015ften \u00f6nce<\/strong> yapt\u0131\u011f\u0131n\u0131z haz\u0131rl\u0131\u011fa ba\u011fl\u0131. DCHost taraf\u0131nda bir cPanel \u2192 Google Workspace \/ Microsoft 365 projesine ba\u015flarken ilk yapt\u0131\u011f\u0131m\u0131z i\u015f, detayl\u0131 bir envanter \u00e7\u0131kar\u0131p ge\u00e7i\u015f senaryosunu netle\u015ftirmek oluyor.<\/p>\n<h3><span id=\"1_Tum_posta_kutularinin_ve_rolleri_listesi\">1. T\u00fcm posta kutular\u0131n\u0131n ve rolleri listesi<\/span><\/h3>\n<p>\u00d6nce cPanel\u2019deki t\u00fcm e\u2011posta hesaplar\u0131n\u0131, alias\u2019lar\u0131 ve forward\u2019lar\u0131 listeleyin:<\/p>\n<ul>\n<li>Ki\u015fisel hesaplar: ornek@alanadiniz.com<\/li>\n<li>Departman hesaplar\u0131: info@, sales@, destek@<\/li>\n<li>Alias \/ forward adresler: info@ \u2192 ahmet@, destek@ \u2192 destek.ekip@ gibi<\/li>\n<li>Mailing list \/ da\u011f\u0131t\u0131m listeleri: cPanel\u2019de varsa bunlar\u0131 da not edin.<\/li>\n<\/ul>\n<p>Yeni tarafta (Google Workspace \/ Microsoft 365) bu rollerin hangisinin <strong>birebir posta kutusu<\/strong>, hangisinin <strong>da\u011f\u0131t\u0131m listesi<\/strong>, hangisinin <strong>payla\u015f\u0131lan posta kutusu<\/strong> olaca\u011f\u0131na \u00f6nceden karar verin. B\u00f6ylece IMAP sync taraf\u0131nda neyi, nereye ta\u015f\u0131yaca\u011f\u0131n\u0131z netle\u015fir.<\/p>\n<h3><span id=\"2_Boyut_analizi_ve_kota_plani\">2. Boyut analizi ve kota plan\u0131<\/span><\/h3>\n<p>cPanel\u2019de her posta kutusunun boyutunu ve toplam disk t\u00fcketimini kontrol edin. \u00d6zellikle 20\u201330 GB \u00fczeri posta kutular\u0131 i\u00e7in ge\u00e7i\u015f stratejisini ayr\u0131 d\u00fc\u015f\u00fcnmek gerekir. B\u00fcy\u00fck posta kutular\u0131 i\u00e7in:<\/p>\n<ul>\n<li>Klas\u00f6r baz\u0131nda \u00f6nceliklendirme (\u00f6r. Yaln\u0131zca son 2 y\u0131l + kritik klas\u00f6rler)<\/li>\n<li>Ar\u015fiv klas\u00f6rleri olu\u015fturarak eski mailleri ayr\u0131 bir posta kutusuna ta\u015f\u0131mak<\/li>\n<li>Ge\u00e7i\u015f \u00f6ncesi temizlik (spam, g\u00f6nderilmi\u015f \u00f6geler, b\u00fcy\u00fck ekler)<\/li>\n<\/ul>\n<p>cPanel taraf\u0131nda b\u00fcy\u00fck posta kutular\u0131n\u0131 nas\u0131l k\u00fc\u00e7\u00fcltebilece\u011finizi merak ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/cpanelde-e-posta-alani-yonetimi-kota-ek-temizligi-ve-dev-mail-kutularini-kucultme-rehberi\/\">dev mail kutular\u0131n\u0131 k\u00fc\u00e7\u00fcltme ve kota y\u00f6netimi i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z rehbere<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"3_Sifreler_kimlik_dogrulama_ve_guvenlik\">3. \u015eifreler, kimlik do\u011frulama ve g\u00fcvenlik<\/span><\/h3>\n<p>IMAP sync yaparken genellikle her posta kutusunun kullan\u0131c\u0131 ad\u0131 ve \u015fifresine ihtiyac\u0131n\u0131z olur. Baz\u0131 ara\u00e7lar OAuth ile \u00e7al\u0131\u015fsa da \u00e7o\u011fu senaryoda kullan\u0131c\u0131 \u015fifrelerini bilmek veya ge\u00e7ici \u015fifreler tan\u0131mlamak zorundas\u0131n\u0131z. Bu y\u00fczden:<\/p>\n<ul>\n<li>Var olan \u015fifrelerin g\u00fcvenle sakland\u0131\u011f\u0131 bir parola kasas\u0131 kullan\u0131n.<\/li>\n<li>Gerekirse ge\u00e7ici ge\u00e7i\u015f \u015fifreleri olu\u015fturup ge\u00e7i\u015f sonra \u015fifreleri yenileyin.<\/li>\n<li>Kullan\u0131c\u0131lar\u0131 s\u00fcrece dahil ederek \u015fifre de\u011fi\u015fimi plan\u0131n\u0131 \u00f6nceden duyurun.<\/li>\n<\/ul>\n<h3><span id=\"4_Kesintisiz_gecis_stratejisi\">4. Kesintisiz ge\u00e7i\u015f stratejisi<\/span><\/h3>\n<p>\u00d6zellikle kurumsal projelerde, \u201cGe\u00e7i\u015f s\u0131ras\u0131nda hi\u00e7bir e\u2011posta kaybolmas\u0131n, kullan\u0131c\u0131lar ayn\u0131 anda switch edilsin.\u201d beklentisi olur. Bunun i\u00e7in ideal yakla\u015f\u0131m:<\/p>\n<ol>\n<li>\u00d6n senkronizasyon (bulk IMAP sync) \u2192 Eski postalar\u0131n b\u00fcy\u00fck k\u0131sm\u0131n\u0131 \u00f6nceden ta\u015f\u0131mak<\/li>\n<li>DNS cutover\u2019dan hemen \u00f6nce delta \/ incremental sync \u2192 Son farklar\u0131 ta\u015f\u0131mak<\/li>\n<li>MX de\u011fi\u015fikli\u011finden sonra k\u0131sa bir s\u00fcre daha ters y\u00f6nl\u00fc kontrol \u2192 Ka\u00e7an mail var m\u0131 diye bakmak<\/li>\n<\/ol>\n<p>Bu mant\u0131\u011f\u0131n daha genel halini, MX ge\u00e7i\u015flerine \u00f6zel olarak anlatt\u0131\u011f\u0131m\u0131z <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 i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z kontrol listesinde<\/a> de bulabilirsiniz.<\/p>\n<h2><span id=\"cPanel_Tarafinda_Hazirlik_Hesaplar_Kotalar_ve_Yedekler\">cPanel Taraf\u0131nda Haz\u0131rl\u0131k: Hesaplar, Kotalar ve Yedekler<\/span><\/h2>\n<p>Ge\u00e7i\u015fe ba\u015flamadan \u00f6nce cPanel taraf\u0131n\u0131 sa\u011flama almak, veri b\u00fct\u00fcnl\u00fc\u011f\u00fc a\u00e7\u0131s\u0131ndan kritik. DCHost altyap\u0131s\u0131ndaki cPanel sunucular\u0131nda bu ad\u0131mlar\u0131 rutin olarak uygular\u0131z.<\/p>\n<h3><span id=\"1_Tam_yedek_ve_gerektiginde_geri_donus_plani\">1. Tam yedek ve gerekti\u011finde geri d\u00f6n\u00fc\u015f plan\u0131<\/span><\/h3>\n<p>Her \u015feyden \u00f6nce, cPanel hesab\u0131n\u0131n (veya en az\u0131ndan t\u00fcm e\u2011posta verisinin) bir tam yede\u011fini al\u0131n:<\/p>\n<ul>\n<li>cPanel &gt; Yedekleme veya Tam Yedek alma b\u00f6l\u00fcm\u00fc \u00fczerinden full backup<\/li>\n<li>veya yaln\u0131zca mail dizinlerini (mail\/, etc\/aliases vb.) rsync ile g\u00fcvenli bir depolamaya kopyalamak<\/li>\n<\/ul>\n<p>Bu sayede IMAP sync s\u0131ras\u0131nda ya da DNS cutover\u2019dan sonra ortaya \u00e7\u0131kabilecek beklenmedik bir sorun durumunda elinizde geriye d\u00f6n\u00fck, tutarl\u0131 bir kopya olur.<\/p>\n<h3><span id=\"2_IMAP_erisimini_ve_baglanti_sinirlarini_kontrol_edin\">2. IMAP eri\u015fimini ve ba\u011flant\u0131 s\u0131n\u0131rlar\u0131n\u0131 kontrol edin<\/span><\/h3>\n<p>IMAP sync arac\u0131, cPanel sunucusuna yo\u011fun \u015fekilde ba\u011flanaca\u011f\u0131 i\u00e7in:<\/p>\n<ul>\n<li>IMAP (993 TLS) servisinin stabil \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun.<\/li>\n<li>Ba\u011flant\u0131 s\u0131n\u0131rlar\u0131n\u0131 (concurrency limit, rate limit vb.) hosting sa\u011flay\u0131c\u0131n\u0131z veya sunucu y\u00f6neticinizle netle\u015ftirin.<\/li>\n<li>Gerekirse ge\u00e7ici olarak limitler biraz y\u00fckseltilsin; aksi h\u00e2lde sync s\u00fcreci \u00e7ok uzayabilir.<\/li>\n<\/ul>\n<h3><span id=\"3_Kullanicilar_icin_klasor_duzeni_ve_temizlik\">3. Kullan\u0131c\u0131lar i\u00e7in klas\u00f6r d\u00fczeni ve temizlik<\/span><\/h3>\n<p>IMAP sync, klas\u00f6r yap\u0131s\u0131n\u0131 aynen ta\u015f\u0131d\u0131\u011f\u0131 i\u00e7in ge\u00e7i\u015f \u00f6ncesinde basit bir temizlik yapman\u0131z faydal\u0131 olur:<\/p>\n<ul>\n<li>Gereksiz klas\u00f6rleri kapatmak veya bir araya toplamak<\/li>\n<li>Trash \/ Junk klas\u00f6rlerindeki \u00e7ok eski posta ve ekleri temizlemek<\/li>\n<li>Gereksiz taslak \/ g\u00f6nderilmi\u015f klas\u00f6rlerini birle\u015ftirmek<\/li>\n<\/ul>\n<p>Bu hem hedef tarafta daha d\u00fczenli bir posta kutusu sa\u011flar hem de senkronizasyon s\u00fcresini k\u0131salt\u0131r.<\/p>\n<h2><span id=\"IMAP_Sync_Mantigi_Eski_Sunucudan_Bulut_Servise_Veri_Tasimak\">IMAP Sync Mant\u0131\u011f\u0131: Eski Sunucudan Bulut Servise Veri Ta\u015f\u0131mak<\/span><\/h2>\n<p><strong>IMAP senkronizasyonu<\/strong>, temelde iki IMAP sunucusu aras\u0131ndaki klas\u00f6r ve mesaj i\u00e7eriklerinin kopyalanmas\u0131d\u0131r. cPanel taraf\u0131 \u201ckaynak\u201d, Google Workspace \/ Microsoft 365 taraf\u0131 ise \u201chedef\u201d IMAP sunucusu olur. Ara\u00e7, ilgili hesap i\u00e7in \u00f6nce klas\u00f6r listesini \u00e7ekip, sonra her klas\u00f6rdeki mesajlar\u0131 tek tek kopyalar ve UID\u2019leri e\u015fle\u015ftirir.<\/p>\n<h3><span id=\"Tek_yonlu_guvenli_kopyalama\">Tek y\u00f6nl\u00fc, g\u00fcvenli kopyalama<\/span><\/h3>\n<p>IMAP sync i\u015flemi genellikle <strong>tek y\u00f6nl\u00fcd\u00fcr<\/strong>: cPanel \u2192 Google Workspace \/ Microsoft 365. Yani yanl\u0131\u015f bir komut vermedi\u011finiz s\u00fcrece hedef taraftan kaynak tarafa veri silmez veya yazmaz. Bu da ge\u00e7i\u015fin g\u00f6rece g\u00fcvenli olmas\u0131n\u0131 sa\u011flar.<\/p>\n<p>Kulland\u0131\u011f\u0131n\u0131z araca g\u00f6re yap\u0131land\u0131rma de\u011fi\u015fse de temel parametreler \u015funlard\u0131r:<\/p>\n<ul>\n<li>Kaynak IMAP sunucusu: host, port, SSL\/TLS, kullan\u0131c\u0131 ad\u0131, \u015fifre<\/li>\n<li>Hedef IMAP sunucusu: host, port, SSL\/TLS, kullan\u0131c\u0131 ad\u0131, \u015fifre<\/li>\n<li>Hangi klas\u00f6rlerin ta\u015f\u0131naca\u011f\u0131 ve hari\u00e7 tutulaca\u011f\u0131<\/li>\n<li>E\u015fzamanl\u0131 ba\u011flant\u0131 say\u0131s\u0131 (performans ve limitler i\u00e7in \u00f6nemli)<\/li>\n<\/ul>\n<h3><span id=\"Ornek_IMAP_sync_komutu_genel_mantik\">\u00d6rnek IMAP sync komutu (genel mant\u0131k)<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki \u00f6rnek, s\u0131k kullan\u0131lan bir IMAP sync arac\u0131n\u0131n mant\u0131\u011f\u0131n\u0131 anlatmak i\u00e7in <strong>temsili<\/strong> bir komuttur. Kulland\u0131\u011f\u0131n\u0131z araca g\u00f6re parametreler de\u011fi\u015febilir:<\/p>\n<pre>\nimapsync \n  --host1 mail.eski-sunucu.com --user1 kullanici@alanadiniz.com --password1 \"ESKI_SIFRE\" \n  --host2 imap.yeni-sunucu.com --user2 kullanici@alanadiniz.com --password2 \"YENI_SIFRE\" \n  --ssl1 --ssl2 \n  --automap --skipjunk \n  --nofoldersizes --useheader 'Message-ID' --skipsize\n<\/pre>\n<p>Buradaki ama\u00e7, kaynaktaki posta kutusunu hedefe kopyalarken gereksiz klas\u00f6rleri (\u00f6rne\u011fin baz\u0131 spam klas\u00f6rleri) atlamak ve IMAP sunucular\u0131 aras\u0131ndaki klas\u00f6r isim farklar\u0131n\u0131 (Sent, G\u00f6nderilmi\u015f \u00f6\u011feler gibi) otomatik e\u015fle\u015ftirmektir.<\/p>\n<h3><span id=\"Performans_limitler_ve_hiz_planlamasi\">Performans, limitler ve h\u0131z planlamas\u0131<\/span><\/h3>\n<p>\u00d6zellikle on binlerce mesaj i\u00e7eren posta kutular\u0131nda IMAP sync, saatler s\u00fcrebilir. Bu y\u00fczden:<\/p>\n<ul>\n<li>K\u00fc\u00e7\u00fck bir pilot kullan\u0131c\u0131yla s\u00fcre ve h\u0131z testini mutlaka yap\u0131n.<\/li>\n<li>E\u015fzamanl\u0131 hesap (parallel) say\u0131s\u0131n\u0131 ve ba\u011flant\u0131 adetini limitler dahilinde ayarlay\u0131n.<\/li>\n<li>Ge\u00e7i\u015fi m\u00fcmk\u00fcnse mesai d\u0131\u015f\u0131 saatlere veya hafta sonuna denk getirin.<\/li>\n<\/ul>\n<p>Kaynak sunucu kapasiteniz s\u0131n\u0131rl\u0131ysa, \u00e7ok fazla hesab\u0131 ayn\u0131 anda senkronize etmek yerine <strong>dalga dalga<\/strong> (\u00f6r. 10\u2019lu gruplar halinde) ilerlemek daha sa\u011fl\u0131kl\u0131d\u0131r.<\/p>\n<h2><span id=\"Adim_Adim_cPanelden_Google_Workspace_Microsoft_365e_Tasima_Senaryosu\">Ad\u0131m Ad\u0131m cPanel\u2019den Google Workspace \/ Microsoft 365\u2019e Ta\u015f\u0131ma Senaryosu<\/span><\/h2>\n<p>\u015eimdi teoriyi bir kenara b\u0131rak\u0131p pratik bir ge\u00e7i\u015f senaryosunu birlikte kural\u0131m. Bu ad\u0131mlar, DCHost m\u00fc\u015fterilerinde s\u0131k kulland\u0131\u011f\u0131m\u0131z, kendini kan\u0131tlam\u0131\u015f bir ak\u0131\u015f.<\/p>\n<h3><span id=\"1_Pilot_kullanici_ile_prova\">1. Pilot kullan\u0131c\u0131 ile prova<\/span><\/h3>\n<ul>\n<li>1\u20132 temsilci kullan\u0131c\u0131 se\u00e7in (tercihen teknik ekibe yak\u0131n veya s\u00fcreci test etmeye istekli ki\u015filer).<\/li>\n<li>Google Workspace \/ Microsoft 365 taraf\u0131nda ilgili posta kutular\u0131n\u0131 olu\u015fturun.<\/li>\n<li>IMAP sync ile cPanel \u2192 yeni servis aras\u0131nda ilk senkronizasyonu yap\u0131n.<\/li>\n<li>Masa\u00fcst\u00fc ve mobil istemcilerde yeni hesaplar\u0131 tan\u0131mlay\u0131p, klas\u00f6r yap\u0131s\u0131 ve mesaj taml\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<\/ul>\n<p>Pilot a\u015famada g\u00f6rece\u011finiz sorunlar (kar\u0131\u015fan klas\u00f6r isimleri, eksik klas\u00f6rler, \u00e7ok eski e\u2011postalar\u0131n gereksiz \u015fekilde ta\u015f\u0131nmas\u0131 vb.) toplu ge\u00e7i\u015f \u00f6ncesi d\u00fczeltmeniz i\u00e7in size zaman kazand\u0131r\u0131r.<\/p>\n<h3><span id=\"2_Toplu_hesap_olusturma_ve_on_senkronizasyon\">2. Toplu hesap olu\u015fturma ve \u00f6n senkronizasyon<\/span><\/h3>\n<p>Pilot sorunsuz ise, cPanel\u2019deki kullan\u0131c\u0131 listenizi Google Workspace \/ Microsoft 365 taraf\u0131na toplu olarak i\u00e7e aktar\u0131n (CSV vb.) ve t\u00fcm posta kutular\u0131n\u0131 olu\u015fturun. Ard\u0131ndan:<\/p>\n<ul>\n<li>Her kullan\u0131c\u0131 i\u00e7in IMAP sync komutlar\u0131n\u0131\/i\u015flerini haz\u0131rlay\u0131n.<\/li>\n<li>\u00d6nce <strong>\u00f6n senkronizasyon<\/strong> yap\u0131n: Yani DNS\u2019i de\u011fi\u015ftirmeden, mevcut t\u00fcm posta kutular\u0131n\u0131 yeni tarafa kopyalay\u0131n.<\/li>\n<li>Bu a\u015famada, yeni gelen e\u2011postalar h\u00e2l\u00e2 cPanel\u2019e d\u00fc\u015fmeye devam edecektir, bu normal.<\/li>\n<\/ul>\n<p>\u00d6n senkronizasyon tamamland\u0131\u011f\u0131nda, yeni tarafta t\u00fcm kullan\u0131c\u0131lara ait \u201cneredeyse g\u00fcncel\u201d bir kopyan\u0131z olu\u015fmu\u015f olur.<\/p>\n<h3><span id=\"3_DNS_cutovera_yakin_ikinci_delta_senkronizasyon\">3. DNS cutover\u2019a yak\u0131n ikinci (delta) senkronizasyon<\/span><\/h3>\n<p>\u00d6n senkronizasyondan sonra cPanel\u2019de yeni e\u2011postalar birikmeye devam etti\u011fi i\u00e7in, MX kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirmeden hemen \u00f6nce ikinci bir <strong>delta \/ incremental senkronizasyon<\/strong> turu yap\u0131n. \u00c7o\u011fu IMAP sync arac\u0131, daha \u00f6nce kopyalanm\u0131\u015f mesajlar\u0131 atlay\u0131p yaln\u0131zca yeni olanlar\u0131 ta\u015f\u0131may\u0131 destekler.<\/p>\n<p>Bu ikinci tur sayesinde, MX kay\u0131tlar\u0131n\u0131 yeni servise y\u00f6nlendirdi\u011finiz anda eski tarafta \u201csadece birka\u00e7 dakikal\u0131k fark\u201d kalm\u0131\u015f olur.<\/p>\n<h3><span id=\"4_MX_SPF_ve_Autodiscover_Autodiscover_Autoconfig_degisiklikleri\">4. MX, SPF ve Autodiscover \/ Autodiscover (Autoconfig) de\u011fi\u015fiklikleri<\/span><\/h3>\n<p>Art\u0131k s\u0131ra DNS taraf\u0131nda. Bu a\u015famada:<\/p>\n<ul>\n<li><strong>MX kay\u0131tlar\u0131n\u0131<\/strong>, Google Workspace veya Microsoft 365\u2019in size verdi\u011fi hedeflere g\u00fcncelleyin.<\/li>\n<li><strong>SPF kayd\u0131n\u0131z\u0131<\/strong>, yeni servis sa\u011flay\u0131c\u0131y\u0131 da i\u00e7erecek \u015fekilde d\u00fczenleyin (\u00f6r. include:google.com \/ include:spf.protection.outlook.com gibi).<\/li>\n<li>cPanel taraf\u0131nda e\u2011posta g\u00f6ndermeye devam etmeyecekseniz eski SMTP IP\u2019lerinizi SPF\u2019ten \u00e7\u0131kar\u0131n.<\/li>\n<li>Autodiscover \/ autoconfig (\u00f6zellikle Outlook kurumsal ortamlar\u0131nda) i\u00e7in \u00f6nerilen CNAME \/ SRV kay\u0131tlar\u0131n\u0131 ekleyin.<\/li>\n<\/ul>\n<p>DNS kay\u0131tlar\u0131n\u0131 yaparken TTL de\u011ferlerini do\u011fru kullanmak, ge\u00e7i\u015fi \u00e7ok h\u0131zland\u0131r\u0131r. Bu konuda detayl\u0131 bir strateji i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber\/\">A, MX, CNAME ve TXT kay\u0131tlar\u0131 i\u00e7in TTL de\u011ferlerini nas\u0131l planlaman\u0131z gerekti\u011fini anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> mutlaka bak\u0131n.<\/p>\n<h3><span id=\"5_MX_degisikliginden_sonra_kisa_sureli_izleme_ve_son_senkronizasyon\">5. MX de\u011fi\u015fikli\u011finden sonra k\u0131sa s\u00fcreli izleme ve son senkronizasyon<\/span><\/h3>\n<p>MX kay\u0131tlar\u0131 yeni servise yay\u0131lmaya ba\u015flad\u0131ktan sonra:<\/p>\n<ul>\n<li>cPanel mail log\u2019lar\u0131n\u0131 izleyin; h\u00e2l\u00e2 eski sunucuya gelen posta var m\u0131 diye kontrol edin.<\/li>\n<li>Varsa, bir <strong>son delta IMAP sync<\/strong> daha \u00e7al\u0131\u015ft\u0131rarak bu fark\u0131 da kapat\u0131n.<\/li>\n<li>Kullan\u0131c\u0131lara masa\u00fcst\u00fc ve mobil istemcilerde yeni hesab\u0131 varsay\u0131lan hale getirmeleri i\u00e7in talimat g\u00f6nderin.<\/li>\n<\/ul>\n<p>Genellikle 24\u201348 saat i\u00e7inde global DNS yay\u0131l\u0131m\u0131 tamamlan\u0131r ve yeni e\u2011posta trafi\u011finin neredeyse tamam\u0131 Google Workspace \/ Microsoft 365 taraf\u0131na d\u00fc\u015fmeye ba\u015flar.<\/p>\n<h3><span id=\"6_Eski_cPanel_posta_kutularinin_yalnizca_okuma_modunda_tutulmasi\">6. Eski cPanel posta kutular\u0131n\u0131n yaln\u0131zca okuma modunda tutulmas\u0131<\/span><\/h3>\n<p>Ge\u00e7i\u015ften hemen sonra eski cPanel hesaplar\u0131n\u0131 silmek yerine, belli bir s\u00fcre boyunca (\u00f6r. 1\u20133 ay) \u201cokuma ama\u00e7l\u0131, kilitli\u201d \u015fekilde b\u0131rakmak, olas\u0131 atlanan maillere kar\u015f\u0131 g\u00fcvenlik yast\u0131\u011f\u0131 olur. Bu s\u00fcre i\u00e7erisinde:<\/p>\n<ul>\n<li>Kullan\u0131c\u0131lara eski hesab\u0131 kullanmamalar\u0131, yaln\u0131zca gerekti\u011finde webmail\u2019den g\u00f6r\u00fcnt\u00fclemeleri gerekti\u011fini net anlat\u0131n.<\/li>\n<li>\u0130sterseniz eski posta kutular\u0131n\u0131 art\u0131k yazma hakk\u0131 olmayan bir kullan\u0131c\u0131ya devir ederek yetkileri k\u0131s\u0131tlay\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"DNS_ve_Kesintisiz_Gecis_MX_TTL_ve_Yol_Haritasi\">DNS ve Kesintisiz Ge\u00e7i\u015f: MX, TTL ve Yol Haritas\u0131<\/span><\/h2>\n<p>cPanel\u2019den Google Workspace \/ Microsoft 365\u2019e e\u2011posta ta\u015f\u0131rken, as\u0131l veri hareketini IMAP sync sa\u011flasa da hangi yeni postan\u0131n nereye gidece\u011fini <strong>DNS \/ MX kay\u0131tlar\u0131<\/strong> belirler. \u0130yi DNS planlanmam\u0131\u015f bir ge\u00e7i\u015fte tipik sorunlar \u015funlard\u0131r:<\/p>\n<ul>\n<li>Bir k\u0131sm\u0131 h\u00e2l\u00e2 eski cPanel sunucusuna d\u00fc\u015fen e\u2011postalar<\/li>\n<li>Yanl\u0131\u015f MX \/ yanl\u0131\u015f SPF nedeniyle spam\u2019e d\u00fc\u015fen kritik mailler<\/li>\n<li>Uzayan DNS yay\u0131l\u0131m\u0131 y\u00fcz\u00fcnden g\u00fcnlerce kar\u0131\u015f\u0131k bir durum<\/li>\n<\/ul>\n<p>Bunlar\u0131 \u00f6nlemek i\u00e7in DCHost taraf\u0131nda uygulad\u0131\u011f\u0131m\u0131z tipik yol haritas\u0131:<\/p>\n<ol>\n<li>Ge\u00e7i\u015ften birka\u00e7 g\u00fcn \u00f6nce MX, SPF ve ilgili TXT kay\u0131tlar\u0131n\u0131n TTL\u2019ini 300 sn (veya alt\u0131na) d\u00fc\u015f\u00fcrmek<\/li>\n<li>Ge\u00e7i\u015f saatinde MX\u2019leri yeni servise \u00e7evirmek ve eski MX\u2019leri tamamen silmek<\/li>\n<li>SPF kayd\u0131n\u0131 an\u0131nda g\u00fcncellemek; hem yeni servisi eklemek hem de kullan\u0131lmayan IP\/hostname\u2019leri \u00e7\u0131karmak<\/li>\n<li>MX de\u011fi\u015fikli\u011finden sonraki ilk 24 saat boyunca log\u2019lar\u0131 izlemeye devam etmek<\/li>\n<\/ol>\n<h2><span id=\"Guvenlik_ve_Teslim_Edilebilirlik_SPF_DKIM_DMARC_ve_MTASTS\">G\u00fcvenlik ve Teslim Edilebilirlik: SPF, DKIM, DMARC ve MTA\u2011STS<\/span><\/h2>\n<p>Yeni tarafa ge\u00e7i\u015fte en fazla ihmal edilen konulardan biri de, e\u2011posta kimlik do\u011frulama kay\u0131tlar\u0131n\u0131n do\u011fru yap\u0131land\u0131r\u0131lmas\u0131. Google Workspace \/ Microsoft 365, DKIM imzalama gibi bir\u00e7ok konuda i\u015finizi kolayla\u015ft\u0131rsa da alan ad\u0131n\u0131z\u0131n DNS\u2019ini siz y\u00f6netti\u011finiz i\u00e7in SPF, DKIM ve DMARC kay\u0131tlar\u0131 h\u00e2l\u00e2 sizin sorumlulu\u011funuzda.<\/p>\n<h3><span id=\"SPF_ve_DKIMi_dogru_kurmak\">SPF ve DKIM\u2019i do\u011fru kurmak<\/span><\/h3>\n<p>Ge\u00e7i\u015f sonras\u0131 yapman\u0131z gerekenler:<\/p>\n<ul>\n<li>SPF kayd\u0131n\u0131zda yaln\u0131zca ger\u00e7ekten kulland\u0131\u011f\u0131n\u0131z e\u2011posta g\u00f6nderim kaynaklar\u0131n\u0131 tutun.<\/li>\n<li>Google Workspace \/ Microsoft 365 i\u00e7in dok\u00fcmantasyonda verilen include\u2019lar\u0131 do\u011fru ekleyin.<\/li>\n<li>Yeni serviste DKIM anahtar\u0131n\u0131 olu\u015fturup ilgili TXT kayd\u0131n\u0131 DNS taraf\u0131na ekleyin.<\/li>\n<\/ul>\n<p>Bu s\u00fcrece daha hakim olmak 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\u2019\u0131 s\u0131f\u0131rdan kurma rehberimizi<\/a> okuyarak temelleri netle\u015ftirmenizi \u00f6neririz.<\/p>\n<h3><span id=\"DMARC_politikasi_ve_raporlarini_takip_etmek\">DMARC politikas\u0131 ve raporlar\u0131n\u0131 takip etmek<\/span><\/h3>\n<p>DMARC, SPF ve DKIM\u2019in birlikte tutarl\u0131 \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 denetleyen ve al\u0131c\u0131 sunuculara \u201cBu alan ad\u0131na aitmi\u015f gibi g\u00f6r\u00fcnen mailleri nas\u0131l muamele edelim?\u201d bilgisini veren kritik bir mekanizma. Ge\u00e7i\u015f sonras\u0131:<\/p>\n<ul>\n<li>\u00d6nce p=none ile ba\u015flay\u0131p raporlar\u0131 (RUA\/RUF) izleyin.<\/li>\n<li>Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f \u00fc\u00e7\u00fcnc\u00fc parti servisleri (CRM, fatura yaz\u0131l\u0131mlar\u0131 vb.) tespit edin.<\/li>\n<li>Ad\u0131m ad\u0131m p=quarantine ve p=reject seviyelerine ge\u00e7in.<\/li>\n<\/ul>\n<p>Bu s\u00fcreci daha stratejik y\u00f6netmek i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/dmarc-raporlari-aggregate-ve-forensic-analiz-ile-pnonedan-prejecte-gecis\/\">DMARC raporlar\u0131yla p=none\u2019dan p=reject\u2019e ge\u00e7i\u015fi ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z yaz\u0131ya<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"Ek_guvenlik_katmanlari_MTASTS_TLSRPT_DANE\">Ek g\u00fcvenlik katmanlar\u0131: MTA\u2011STS, TLS\u2011RPT, DANE<\/span><\/h3>\n<p>\u0130leri seviye kurumsal ortamlarda, MTA\u2011STS, TLS\u2011RPT ve DANE\/TLSA gibi DNS tabanl\u0131 g\u00fcvenlik mekanizmalar\u0131 da g\u00fcndeme gelir. Bu protokoller:<\/p>\n<ul>\n<li>Sunucular aras\u0131 e\u2011posta trafi\u011finin TLS ile \u015fifrelenmesini zorunlu k\u0131labilir.<\/li>\n<li>Yanl\u0131\u015f veya sald\u0131rgan ara sunucular\u0131n devreye girmesini zorla\u015ft\u0131r\u0131r.<\/li>\n<li>Hatal\u0131 TLS kurulumlar\u0131n\u0131 raporlayarak iyile\u015ftirme imkan\u0131 sunar.<\/li>\n<\/ul>\n<p>Bu konularla ilgileniyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/mta-sts-tls-rpt-ve-bimi-nedir-e-posta-guvenligi-ve-marka-gorunurlugu-icin-gelismis-dns-ayarlari\/\">MTA\u2011STS, TLS\u2011RPT ve BIMI i\u00e7in geli\u015fmi\u015f DNS ayarlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> iyi bir ba\u015flang\u0131\u00e7 olacakt\u0131r.<\/p>\n<h2><span id=\"Sik_Yapilan_Hatalar_ve_DCHost_Ekibinin_Onerdigi_Iyi_Uygulamalar\">S\u0131k Yap\u0131lan Hatalar ve DCHost Ekibinin \u00d6nerdi\u011fi \u0130yi Uygulamalar<\/span><\/h2>\n<p>cPanel\u2019den Google Workspace \/ Microsoft 365\u2019e ge\u00e7i\u015flerde sahada en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar ve bunlara kar\u015f\u0131 \u00f6nerilerimizi \u00f6zetleyelim.<\/p>\n<h3><span id=\"1_IMAP_sync_yerine_PSTindiryukselt_ile_ugrasmak\">1. IMAP sync yerine PST\/indir\u2011y\u00fckselt ile u\u011fra\u015fmak<\/span><\/h3>\n<p>Bireysel kullan\u0131c\u0131 g\u00f6z\u00fcyle bak\u0131nca Outlook\u2019tan PST export al\u0131p yeni hesaba import etmek \u201ckolay\u201d gibi g\u00f6r\u00fcn\u00fcr; ancak onlarca kullan\u0131c\u0131, y\u00fczlerce gigabayt veri oldu\u011funda bu y\u00f6ntem kabusa d\u00f6ner. IMAP sync ile:<\/p>\n<ul>\n<li>Merkezi, tekrarlanabilir bir s\u00fcre\u00e7 kurars\u0131n\u0131z.<\/li>\n<li>Geriye d\u00f6n\u00fck delta senkronizasyonlarla farklar\u0131 kapatabilirsiniz.<\/li>\n<li>Kullan\u0131c\u0131lara minimum i\u015f b\u0131rak\u0131rs\u0131n\u0131z.<\/li>\n<\/ul>\n<h3><span id=\"2_DNSi_erken_veya_plansiz_degistirmek\">2. DNS\u2019i erken veya plans\u0131z de\u011fi\u015ftirmek<\/span><\/h3>\n<p>En yayg\u0131n problem: MX kay\u0131tlar\u0131 de\u011fi\u015ftirilip IMAP sync\u2019e ge\u00e7 ba\u015flanmas\u0131. Bu durumda:<\/p>\n<ul>\n<li>Yeni tarafta veri eksik kal\u0131r.<\/li>\n<li>Eski ve yeni posta kutular\u0131 aras\u0131nda kar\u0131\u015f\u0131kl\u0131k ya\u015fan\u0131r.<\/li>\n<li>Kullan\u0131c\u0131lar \u201cBaz\u0131 maillerim kay\u0131p.\u201d demeye ba\u015flar.<\/li>\n<\/ul>\n<p>Her zaman \u00f6nce <strong>\u00f6n senkronizasyon<\/strong>, ard\u0131ndan MX de\u011fi\u015fikli\u011fi ve son olarak <strong>delta senkronizasyon<\/strong> s\u0131ras\u0131na sad\u0131k kal\u0131n.<\/p>\n<h3><span id=\"3_SPFDKIMi_ihmal_etmek_ve_spam_sikayeti_almak\">3. SPF\/DKIM\u2019i ihmal etmek ve spam \u015fikayeti almak<\/span><\/h3>\n<p>SPF ve DKIM do\u011fru kurulmad\u0131\u011f\u0131nda, yeni sistemden g\u00f6nderdi\u011finiz e\u2011postalar al\u0131c\u0131 taraf\u0131nda g\u00fcvenilir g\u00f6r\u00fcnmez ve spam klas\u00f6r\u00fcne d\u00fc\u015febilir. Bu da ge\u00e7i\u015f sonras\u0131 \u201cYeni sistem k\u00f6t\u00fc, mailler gitmiyor.\u201d alg\u0131s\u0131 olu\u015fturur. Ge\u00e7i\u015f plan\u0131na SPF, DKIM ve DMARC g\u00fcncellemelerini mutlaka dahil edin. \u0130lgili alanlarda detay isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/e-postalar-neden-spam-klasorune-dusuyor-paylasimli-hosting-ve-vps-icin-teslim-edilebilirlik-kontrol-listesi\/\">e\u2011postalar neden spam klas\u00f6r\u00fcne d\u00fc\u015f\u00fcyor ba\u015fl\u0131kl\u0131 teslim edilebilirlik kontrol listemiz<\/a> size \u00e7ok yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"4_Kullanici_iletisimini_unutarak_panik_yaratmak\">4. Kullan\u0131c\u0131 ileti\u015fimini unutarak panik yaratmak<\/span><\/h3>\n<p>Teknik taraf m\u00fckemmel olabilir; ancak kullan\u0131c\u0131lar s\u00fcrecin ne zaman, nas\u0131l ve kendilerini nas\u0131l etkileyece\u011fini bilmezse, ge\u00e7i\u015f g\u00fcn\u00fc \u015fikayet ya\u011fmuruna tutulursunuz. Bu y\u00fczden:<\/p>\n<ul>\n<li>Ge\u00e7i\u015ften \u00f6nce net bir bilgi e\u2011postas\u0131 g\u00f6nderin.<\/li>\n<li>Yeni giri\u015f adresleri, istemci ayarlar\u0131 ve \u015fifre politikalar\u0131n\u0131 a\u00e7\u0131k\u00e7a yaz\u0131n.<\/li>\n<li>Ge\u00e7i\u015f g\u00fcn\u00fc ve sonras\u0131nda destek taleplerini toplayacak net bir kanal belirleyin.<\/li>\n<\/ul>\n<h3><span id=\"5_Eski_sistemi_cok_erken_kapatmak\">5. Eski sistemi \u00e7ok erken kapatmak<\/span><\/h3>\n<p>IMAP sync bitti, MX\u2019ler g\u00fcncellendi diye cPanel taraf\u0131n\u0131 hemen kapatmak yerine, belirli bir s\u00fcre yaln\u0131zca okuma modunda tutmak; atlanm\u0131\u015f mailleri yakalama, beklenmedik bir sorunda h\u0131zl\u0131 rollback yapma imkan\u0131 sa\u011flar. DCHost olarak kritik projelerde mutlaka bir \u201cgeri d\u00f6n\u00fc\u015f plan\u0131\u201d ve bu plan\u0131 destekleyecek yedek \/ eski sistem bekleme s\u00fcresi tan\u0131mlar\u0131z.<\/p>\n<h2><span id=\"Sonuc_DCHost_ile_Kontrollu_Seffaf_ve_Geri_Donusu_Mumkun_Bir_Gecis\">Sonu\u00e7: DCHost ile Kontroll\u00fc, \u015eeffaf ve Geri D\u00f6n\u00fc\u015f\u00fc M\u00fcmk\u00fcn Bir Ge\u00e7i\u015f<\/span><\/h2>\n<p>cPanel\u2019den Google Workspace veya Microsoft 365\u2019e ge\u00e7i\u015f, do\u011fru planland\u0131\u011f\u0131nda hem kullan\u0131c\u0131 deneyimini hem de kurumsal g\u00fcvenli\u011fi ciddi \u015fekilde iyile\u015ftiren bir ad\u0131m. Ancak bunun bir gecede, hi\u00e7bir haz\u0131rl\u0131k yapmadan sadece MX\u2019leri de\u011fi\u015ftirerek \u00e7\u00f6z\u00fclebilecek basit bir i\u015flem olmad\u0131\u011f\u0131n\u0131 bilmek gerekiyor. IMAP sync, DNS planlamas\u0131, SPF\/DKIM\/DMARC ayarlar\u0131 ve kullan\u0131c\u0131 ileti\u015fimi birlikte ele al\u0131nd\u0131\u011f\u0131nda, ge\u00e7i\u015f s\u00fcreci <strong>kontroll\u00fc, \u015feffaf ve gerekti\u011finde geri d\u00f6n\u00fclebilir<\/strong> hale geliyor.<\/p>\n<p>DCHost ekibi olarak cPanel, DNS ve e\u2011posta altyap\u0131s\u0131n\u0131 b\u00fct\u00fcnsel bir \u015fekilde ele al\u0131yoruz. Web siteniz h\u00e2l\u00e2 bizim sunucular\u0131m\u0131zda kal\u0131rken, e\u2011postan\u0131z\u0131 Google Workspace \/ Microsoft 365 gibi hizmetlere ta\u015f\u0131yabilir; DNS, SSL ve e\u2011posta do\u011frulama kay\u0131tlar\u0131n\u0131 tek bir mimari i\u00e7inde y\u00f6netebiliriz. E\u011fer hen\u00fcz \u201ckendi hosting e\u2011postan\u0131z m\u0131 yoksa bulut tabanl\u0131 e\u2011posta m\u0131 sizin i\u00e7in daha mant\u0131kl\u0131?\u201d sorusuna cevap ar\u0131yorsan\u0131z, mutlaka <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-hosting-secimi-kendi-sunucunuz-mu-paylasimli-hosting-mi-google-workspace-ve-microsoft-365-mi\/\">e\u2011posta hosting se\u00e7imi rehberimizi<\/a> de okuman\u0131z\u0131 \u00f6neririz.<\/p>\n<p>Ge\u00e7i\u015fi kendiniz yapmak isterseniz, bu yaz\u0131daki ad\u0131mlar\u0131 bir kontrol listesi gibi kullanabilir; \u00f6zellikle IMAP sync ve DNS cutover taraf\u0131nda ad\u0131m ad\u0131m ilerleyerek riskleri minimize edebilirsiniz. Daha karma\u015f\u0131k, \u00e7ok alan adl\u0131 veya \u00e7ok lokasyonlu yap\u0131larda ise DCHost teknik ekibinden destek olarak projeyi birlikte planlayabiliriz. B\u00f6ylece hem kesinti riskini en aza indirir, hem de uzun vadede s\u00fcrd\u00fcr\u00fclebilir bir e\u2011posta ve DNS mimarisi kurmu\u015f olursunuz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>cPanel \u00fczerinde y\u0131llard\u0131r \u00e7al\u0131\u015fan bir e\u2011posta altyap\u0131s\u0131n\u0131 Google Workspace veya Microsoft 365\u2019e ta\u015f\u0131mak, ka\u011f\u0131t \u00fczerinde basit g\u00f6r\u00fcnebilir; ancak i\u015f kesintisiz ge\u00e7i\u015fe ve veri kayb\u0131 ya\u015famamaya gelince, k\u00fc\u00e7\u00fck hatalar bile b\u00fcy\u00fck sorunlara d\u00f6n\u00fc\u015febilir. DCHost ekibi olarak hem kendi altyap\u0131m\u0131z i\u00e7inde hem de m\u00fc\u015fterilerimizin projelerinde s\u0131k s\u0131k cPanel \u2192 bulut e\u2011posta ge\u00e7i\u015fleri yap\u0131yoruz ve pratikte en \u00e7ok [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4351,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4350","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\/4350","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=4350"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4350\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4351"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}