{"id":4440,"date":"2026-02-04T16:00:18","date_gmt":"2026-02-04T13:00:18","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/e-posta-hata-kodlarini-anlamak-550-554-421-ve-bounce-mesajlarini-cozmek\/"},"modified":"2026-02-04T16:00:18","modified_gmt":"2026-02-04T13:00:18","slug":"e-posta-hata-kodlarini-anlamak-550-554-421-ve-bounce-mesajlarini-cozmek","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/e-posta-hata-kodlarini-anlamak-550-554-421-ve-bounce-mesajlarini-cozmek\/","title":{"rendered":"E\u2011Posta Hata Kodlar\u0131n\u0131 Anlamak: 550, 554, 421 ve Bounce Mesajlar\u0131n\u0131 \u00c7\u00f6zmek"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Eposta_hata_kodlari_neden_bu_kadar_can_sikici_ama_bir_o_kadar_da_degerli\"><span class=\"toc_number toc_depth_1\">1<\/span> E\u2011posta hata kodlar\u0131 neden bu kadar can s\u0131k\u0131c\u0131 ama bir o kadar da de\u011ferli?<\/a><\/li><li><a href=\"#SMTP_ve_bounce_mantigini_kisaca_anlamak\"><span class=\"toc_number toc_depth_1\">2<\/span> SMTP ve bounce mant\u0131\u011f\u0131n\u0131 k\u0131saca anlamak<\/a><ul><li><a href=\"#SMTP_durum_kodlarinin_yapisi_2xx_4xx_5xx\"><span class=\"toc_number toc_depth_2\">2.1<\/span> SMTP durum kodlar\u0131n\u0131n yap\u0131s\u0131: 2xx, 4xx, 5xx<\/a><\/li><li><a href=\"#Hard_bounce_vs_soft_bounce\"><span class=\"toc_number toc_depth_2\">2.2<\/span> Hard bounce vs soft bounce<\/a><\/li><\/ul><\/li><li><a href=\"#En_sik_gorulen_hata_kodlari_550_554_421_ve_digerleri\"><span class=\"toc_number toc_depth_1\">3<\/span> En s\u0131k g\u00f6r\u00fclen hata kodlar\u0131: 550, 554, 421 ve di\u011ferleri<\/a><ul><li><a href=\"#550_serisi_hatalar_Yanlis_adres_mi_politika_mi_DNS_mi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 550 serisi hatalar: Yanl\u0131\u015f adres mi, politika m\u0131, DNS mi?<\/a><\/li><li><a href=\"#554_hatalari_Spam_politika_ve_itibar_duvari\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 554 hatalar\u0131: Spam, politika ve itibar duvar\u0131<\/a><\/li><li><a href=\"#421_hatalari_Sunucu_yogunlugu_ve_rate_limit_problemleri\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 421 hatalar\u0131: Sunucu yo\u011funlu\u011fu ve rate limit problemleri<\/a><\/li><li><a href=\"#450_451_452_Yine_soft_bounce_ama_dikkate_alinmali\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 450 \/ 451 \/ 452: Yine soft bounce ama dikkate al\u0131nmal\u0131<\/a><\/li><li><a href=\"#552_553_ve_digerleri_Kota_boyut_ve_adres_hatalari\"><span class=\"toc_number toc_depth_2\">3.5<\/span> 552 \/ 553 ve di\u011ferleri: Kota, boyut ve adres hatalar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Gelen_bounce_mesajini_dogru_okumak\"><span class=\"toc_number toc_depth_1\">4<\/span> Gelen bounce mesaj\u0131n\u0131 do\u011fru okumak<\/a><ul><li><a href=\"#Hangi_alanlara_bakmalisiniz\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Hangi alanlara bakmal\u0131s\u0131n\u0131z?<\/a><\/li><li><a href=\"#Ornek_bir_bounce_mesaji_nasil_gorunur\"><span class=\"toc_number toc_depth_2\">4.2<\/span> \u00d6rnek bir bounce mesaj\u0131 nas\u0131l g\u00f6r\u00fcn\u00fcr?<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_adim_teshis_rehberi_Hata_kodundan_cozume_giden_yol\"><span class=\"toc_number toc_depth_1\">5<\/span> Ad\u0131m ad\u0131m te\u015fhis rehberi: Hata kodundan \u00e7\u00f6z\u00fcme giden yol<\/a><ul><li><a href=\"#1_Hata_kodunu_ve_Diagnostic-Code_satirini_not_edin\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. Hata kodunu ve Diagnostic-Code sat\u0131r\u0131n\u0131 not edin<\/a><\/li><li><a href=\"#2_Adres_hatasi_mi_alan_adi_hatasi_mi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. Adres hatas\u0131 m\u0131, alan ad\u0131 hatas\u0131 m\u0131?<\/a><\/li><li><a href=\"#3_SPAM_politika_kaynakli_mi\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. SPAM \/ politika kaynakl\u0131 m\u0131?<\/a><\/li><li><a href=\"#4_Icerik_ve_ek_boyutlarini_gozden_gecirin\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. \u0130\u00e7erik ve ek boyutlar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/a><\/li><li><a href=\"#5_Rate_limit_ve_baglanti_sinirlarini_kontrol_edin\"><span class=\"toc_number toc_depth_2\">5.5<\/span> 5. Rate limit ve ba\u011flant\u0131 s\u0131n\u0131rlar\u0131n\u0131 kontrol edin<\/a><\/li><li><a href=\"#6_Sorun_sizde_degil_karsi_tarafta_olabilir\"><span class=\"toc_number toc_depth_2\">5.6<\/span> 6. Sorun sizde de\u011fil kar\u015f\u0131 tarafta olabilir<\/a><\/li><li><a href=\"#7_Itibar_sorunu_derinse_kurtarma_plani_yapin\"><span class=\"toc_number toc_depth_2\">5.7<\/span> 7. \u0130tibar sorunu derinse, kurtarma plan\u0131 yap\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Bu_hatalarin_surekli_tekrarlanmamasi_icin_onleyici_adimlar\"><span class=\"toc_number toc_depth_1\">6<\/span> Bu hatalar\u0131n s\u00fcrekli tekrarlanmamas\u0131 i\u00e7in \u00f6nleyici ad\u0131mlar<\/a><ul><li><a href=\"#Temiz_liste_yonetimi_ve_hard_bouncelari_hizlica_ayiklama\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Temiz liste y\u00f6netimi ve hard bounce\u2019lar\u0131 h\u0131zl\u0131ca ay\u0131klama<\/a><\/li><li><a href=\"#DNS_ve_dogrulama_kayitlarini_bir_kere_duzgun_kurup_izleyin\"><span class=\"toc_number toc_depth_2\">6.2<\/span> DNS ve do\u011frulama kay\u0131tlar\u0131n\u0131 bir kere d\u00fczg\u00fcn kurup izleyin<\/a><\/li><li><a href=\"#Altyapiyi_is_yukune_gore_planlayin\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Altyap\u0131y\u0131 i\u015f y\u00fck\u00fcne g\u00f6re planlay\u0131n<\/a><\/li><li><a href=\"#Izleme_ve_log_analizi_kulturu_olusturun\"><span class=\"toc_number toc_depth_2\">6.4<\/span> \u0130zleme ve log analizi k\u00fclt\u00fcr\u00fc olu\u015fturun<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_ve_DCHost_ile_yol_haritaniz\"><span class=\"toc_number toc_depth_1\">7<\/span> Sonu\u00e7 ve DCHost ile yol haritan\u0131z<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Eposta_hata_kodlari_neden_bu_kadar_can_sikici_ama_bir_o_kadar_da_degerli\">E\u2011posta hata kodlar\u0131 neden bu kadar can s\u0131k\u0131c\u0131 ama bir o kadar da de\u011ferli?<\/span><\/h2>\n<p>E\u2011posta g\u00f6nderiyorsunuz, \u00f6zellikle de kurumsal tarafta; teklif, fatura, \u015fifre s\u0131f\u0131rlama, bildirim\u2026 Ve bir bak\u0131yorsunuz, m\u00fc\u015fteriden yan\u0131t gelmek yerine posta kutunuza karma\u015f\u0131k bir geri d\u00f6n\u00fc\u015f iletisi d\u00fc\u015fm\u00fc\u015f: <strong>&#8220;550 5.1.1 User unknown&#8221;<\/strong>, <strong>&#8220;554 5.7.1 Message rejected&#8221;<\/strong> ya da <strong>&#8220;421 4.7.0 Temporary rate limit&#8221;<\/strong>. \u0130lk bak\u0131\u015fta \u015fifre gibi g\u00f6r\u00fcnen bu hata kodlar\u0131, asl\u0131nda size e\u2011posta altyap\u0131n\u0131z hakk\u0131nda son derece kritik bilgiler veriyor.<\/p>\n<p>DCHost taraf\u0131nda y\u00fczlerce alan ad\u0131 ve e\u2011posta altyap\u0131s\u0131 y\u00f6netirken en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz sorunlardan biri, bu hata mesajlar\u0131n\u0131n yok say\u0131lmas\u0131 ya da yanl\u0131\u015f yorumlanmas\u0131. Oysa \u00e7o\u011fu zaman, bounce mesaj\u0131na dikkatlice bakarak sorunun <strong>spam filtreleri mi<\/strong>, <strong>yanl\u0131\u015f adres mi<\/strong>, <strong>IP itibar\u0131n\u0131z m\u0131<\/strong> yoksa <strong>DNS\/SPF\/DKIM yap\u0131land\u0131rmas\u0131 m\u0131<\/strong> kaynakl\u0131 oldu\u011funu birka\u00e7 dakikada anlamak m\u00fcmk\u00fcn.<\/p>\n<p>Bu yaz\u0131da, \u00f6zellikle <strong>550, 554 ve 421<\/strong> ba\u015fta olmak \u00fczere yayg\u0131n e\u2011posta hata kodlar\u0131n\u0131 sade bir dille a\u00e7\u0131klayaca\u011f\u0131z, gelen bounce mesaj\u0131n\u0131 sat\u0131r sat\u0131r nas\u0131l okuman\u0131z gerekti\u011fini g\u00f6sterece\u011fiz ve DCHost ekibinin sahada kulland\u0131\u011f\u0131 <strong>ad\u0131m ad\u0131m te\u015fhis ve \u00e7\u00f6z\u00fcm rehberini<\/strong> payla\u015faca\u011f\u0131z. B\u00f6ylece her yeni hatada paniklemek yerine, sistematik bir checklist ile ilerleyebilir hale geleceksiniz.<\/p>\n<h2><span id=\"SMTP_ve_bounce_mantigini_kisaca_anlamak\">SMTP ve bounce mant\u0131\u011f\u0131n\u0131 k\u0131saca anlamak<\/span><\/h2>\n<p>Hata kodlar\u0131n\u0131 \u00e7\u00f6zebilmek i\u00e7in \u00f6nce e\u2011postan\u0131n arka planda nas\u0131l iletildi\u011fini anlamak gerekiyor. E\u2011posta g\u00f6nderimi <strong>SMTP<\/strong> adl\u0131 protokol \u00fczerinden y\u00fcr\u00fcr. G\u00f6nderen sunucu ile al\u0131c\u0131 sunucu aras\u0131nda, t\u0131pk\u0131 web isteklerindeki HTTP durum kodlar\u0131 gibi, <strong>3 basamakl\u0131 durum kodlar\u0131<\/strong> kullan\u0131l\u0131r.<\/p>\n<h3><span id=\"SMTP_durum_kodlarinin_yapisi_2xx_4xx_5xx\">SMTP durum kodlar\u0131n\u0131n yap\u0131s\u0131: 2xx, 4xx, 5xx<\/span><\/h3>\n<ul>\n<li><strong>2xx (Ba\u015far\u0131l\u0131)<\/strong>: \u0130\u015flem ba\u015far\u0131l\u0131. \u00d6rne\u011fin <strong>250 OK<\/strong>.<\/li>\n<li><strong>4xx (Ge\u00e7ici hata)<\/strong>: Soft hata. Al\u0131c\u0131 sunucu \u201c\u015fu an kabul edemiyorum ama sonra tekrar dene\u201d diyor. \u00d6rne\u011fin <strong>421 4.7.0 Temporary failure<\/strong>.<\/li>\n<li><strong>5xx (Kal\u0131c\u0131 hata)<\/strong>: Hard hata. \u201cBu mesaj\u0131 asla kabul etmeyece\u011fim\u201d anlam\u0131na gelen kal\u0131c\u0131 ret. \u00d6rne\u011fin <strong>550 5.1.1 User unknown<\/strong> veya <strong>554 5.7.1 Message rejected<\/strong>.<\/li>\n<\/ul>\n<p>Modern sunucular, bu 3 basamakl\u0131 koda ek olarak <strong>geli\u015fmi\u015f durum kodlar\u0131<\/strong> da d\u00f6ner: <strong>5.1.1, 5.2.2, 5.7.1<\/strong> gibi. Bunlar hatan\u0131n <em>nedenini<\/em> daha net ifade eder:<\/p>\n<ul>\n<li><strong>5.1.x<\/strong>: Adresleme (yanl\u0131\u015f\/var olmayan adres, alan ad\u0131 problemi)<\/li>\n<li><strong>5.2.x<\/strong>: Mail kutusu (dolu, devre d\u0131\u015f\u0131, kota a\u015f\u0131m\u0131)<\/li>\n<li><strong>5.7.x<\/strong>: Yetki\/spam politikalar\u0131 (IP kara listede, SPF\/DKIM uyumsuz, politikaya tak\u0131lma)<\/li>\n<\/ul>\n<h3><span id=\"Hard_bounce_vs_soft_bounce\">Hard bounce vs soft bounce<\/span><\/h3>\n<p>Hata kodlar\u0131n\u0131 pratikte iki ana grupta d\u00fc\u015f\u00fcnmek faydal\u0131:<\/p>\n<ul>\n<li><strong>Soft bounce (4xx kodlar)<\/strong>: Ge\u00e7ici sorun. \u00d6rnekler:\n<ul>\n<li>Al\u0131c\u0131 sunucu yo\u011fun veya bak\u0131mda<\/li>\n<li>Rate limit\u2019e tak\u0131lm\u0131\u015fs\u0131n\u0131z<\/li>\n<li>DNS\/ge\u00e7ici a\u011f sorunlar\u0131<\/li>\n<\/ul>\n<p>\u00c7o\u011fu MTA ayn\u0131 mesaj\u0131 birka\u00e7 defa otomatik yeniden dener.<\/li>\n<li><strong>Hard bounce (5xx kodlar)<\/strong>: Kal\u0131c\u0131 sorun. \u00d6rnekler:\n<ul>\n<li>Adres hatal\u0131 veya hi\u00e7 yok (<strong>550 5.1.1<\/strong>)<\/li>\n<li>Spam politikas\u0131na tak\u0131lm\u0131\u015fs\u0131n\u0131z (<strong>554 5.7.1<\/strong>)<\/li>\n<li>Al\u0131c\u0131 alan ad\u0131 yok veya MX kayd\u0131 hatal\u0131<\/li>\n<\/ul>\n<p>Bu tip adresleri listelerinizden \u00e7\u0131karmaman\u0131z, hem itibar\u0131n\u0131z\u0131 hem de teslim edilebilirli\u011fi bozar.<\/li>\n<\/ul>\n<p>Daha protokol seviyesi detaylara girmek isterseniz, haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/smtp-hata-kodlari-ve-bounce-mesajlari-rehberi\/\">SMTP hata kodlar\u0131 ve bounce mesajlar\u0131 rehberimizde<\/a> RFC seviyesinde a\u00e7\u0131klamalar da bulabilirsiniz. Bu yaz\u0131da ise odak noktam\u0131z, bu hatalar\u0131 <strong>ger\u00e7ek d\u00fcnyada nas\u0131l te\u015fhis edip \u00e7\u00f6zece\u011finiz<\/strong> olacak.<\/p>\n<h2><span id=\"En_sik_gorulen_hata_kodlari_550_554_421_ve_digerleri\">En s\u0131k g\u00f6r\u00fclen hata kodlar\u0131: 550, 554, 421 ve di\u011ferleri<\/span><\/h2>\n<h3><span id=\"550_serisi_hatalar_Yanlis_adres_mi_politika_mi_DNS_mi\">550 serisi hatalar: Yanl\u0131\u015f adres mi, politika m\u0131, DNS mi?<\/span><\/h3>\n<p><strong>550<\/strong> ile ba\u015flayan hatalar, en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hard bounce t\u00fcrlerinden. En yayg\u0131n varyasyonlar:<\/p>\n<ul>\n<li><strong>550 5.1.1 User unknown<\/strong><br \/>Al\u0131c\u0131 e\u2011posta adresi yok. \u00d6rne\u011fin <code>info@ornekfirma.com<\/code> adresi hi\u00e7 olu\u015fturulmam\u0131\u015f ya da silinmi\u015f.<\/li>\n<li><strong>550 5.1.0 Address rejected<\/strong><br \/>Adres bi\u00e7imi yanl\u0131\u015f, alan ad\u0131 hatal\u0131 yaz\u0131lm\u0131\u015f (<code>gnail.com<\/code> gibi) veya al\u0131c\u0131 sunucu bu alan ad\u0131na mail kabul etmiyor.<\/li>\n<li><strong>550 5.2.2 Mailbox full<\/strong><br \/>Al\u0131c\u0131 posta kutusunun kotas\u0131 dolmu\u015f. \u00d6zellikle k\u00fc\u00e7\u00fck i\u015fletmelerde s\u0131k g\u00f6r\u00fcl\u00fcr.<\/li>\n<li><strong>550 5.7.1 Relaying denied \/ Message rejected<\/strong><br \/>Genellikle <strong>yetkilendirme ve g\u00fcvenlik politikalar\u0131<\/strong> ile ilgilidir. Yanl\u0131\u015f SMTP portu\/\u015fifre ile relay etmeye \u00e7al\u0131\u015fmak, a\u00e7\u0131k relay denemeleri veya SPF\/DKIM uyumsuzluklar\u0131 tetikleyebilir.<\/li>\n<\/ul>\n<p>Nas\u0131l yakla\u015fmal\u0131?<\/p>\n<ul>\n<li>\u00d6nce hata mesaj\u0131ndaki <strong>&#8220;User unknown&#8221; \/ &#8220;No such user&#8221;<\/strong> gibi net ipu\u00e7lar\u0131n\u0131 okuyun.<\/li>\n<li>E\u011fer adres ger\u00e7ekten yanl\u0131\u015fsa, adres listesini temizleyin. Bu adreslere tekrar mail atmay\u0131n.<\/li>\n<li>&#8220;Mailbox full&#8221; ise kar\u015f\u0131 tarafla farkl\u0131 bir kanaldan ileti\u015fime ge\u00e7ip durumu haber verin.<\/li>\n<li>&#8220;Relaying denied&#8221; gibi bir hata, genellikle sizin <strong>SMTP kimlik do\u011frulama ya da sunucu ayarlar\u0131n\u0131zda<\/strong> sorun oldu\u011funa i\u015faret eder.<\/li>\n<\/ul>\n<h3><span id=\"554_hatalari_Spam_politika_ve_itibar_duvari\">554 hatalar\u0131: Spam, politika ve itibar duvar\u0131<\/span><\/h3>\n<p><strong>554<\/strong> kodu, \u00e7o\u011fu zaman <strong>spam politikas\u0131 kaynakl\u0131 red<\/strong> anlam\u0131na gelir. \u00d6rnekler:<\/p>\n<ul>\n<li><strong>554 5.7.1 Message rejected due to content restrictions<\/strong><\/li>\n<li><strong>554 5.7.1 Service unavailable; Client host blocked<\/strong><\/li>\n<li><strong>554 5.7.1 Your IP is listed in RBL<\/strong><\/li>\n<\/ul>\n<p>Bu tip hatalar genellikle \u015funlarla ba\u011flant\u0131l\u0131d\u0131r:<\/p>\n<ul>\n<li>IP adresiniz bir <strong>kara listede (RBL)<\/strong><\/li>\n<li>SPF, DKIM, DMARC kay\u0131tlar\u0131n\u0131z eksik ya da hatal\u0131<\/li>\n<li>Alan ad\u0131n\u0131z\u0131n ge\u00e7mi\u015fi k\u00f6t\u00fc (daha \u00f6nce spam i\u00e7in kullan\u0131lm\u0131\u015f olabilir)<\/li>\n<li>\u0130\u00e7erik taraf\u0131nda tetikleyici anahtar kelimeler, ekler veya linkler bulunuyor<\/li>\n<\/ul>\n<p>DNS tabanl\u0131 do\u011frulama ayarlar\u0131n\u0131z\u0131n sa\u011flam oldu\u011fundan emin olmak i\u00e7in, ad\u0131m ad\u0131m anlat\u0131ml\u0131 <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 kurulum rehberimizi<\/a> mutlaka incelemenizi \u00f6neririz.<\/p>\n<h3><span id=\"421_hatalari_Sunucu_yogunlugu_ve_rate_limit_problemleri\">421 hatalar\u0131: Sunucu yo\u011funlu\u011fu ve rate limit problemleri<\/span><\/h3>\n<p><strong>421<\/strong> kodu, <strong>ge\u00e7ici (soft) hata<\/strong> s\u0131n\u0131f\u0131nda yer al\u0131r. \u00d6rnek iletiler:<\/p>\n<ul>\n<li><strong>421 4.7.0 Temporary server error. Please try again later.<\/strong><\/li>\n<li><strong>421 4.7.0 Too many connections from your IP<\/strong><\/li>\n<li><strong>421 4.4.2 Connection dropped<\/strong><\/li>\n<\/ul>\n<p>\u00c7o\u011funlukla:<\/p>\n<ul>\n<li>Al\u0131c\u0131 sunucunun yo\u011fun olmas\u0131<\/li>\n<li>Sizden gelen ba\u011flant\u0131 say\u0131s\u0131n\u0131n limitleri a\u015fmas\u0131 (rate limit)<\/li>\n<li>Al\u0131c\u0131 taraf\u0131n bak\u0131m veya ge\u00e7ici a\u011f sorunlar\u0131 ya\u015famas\u0131<\/li>\n<\/ul>\n<p>DCHost altyap\u0131s\u0131nda, bu tip hatalarda MTA\u2019lar otomatik retry yapar. Ancak:<\/p>\n<ul>\n<li>K\u0131sa s\u00fcrede <strong>\u00e7ok y\u00fcksek hacimli g\u00f6nderim<\/strong> yap\u0131yorsan\u0131z (kampanya, b\u00fclten vb.), al\u0131c\u0131 sunucu sizi yava\u015flatmak i\u00e7in 421 d\u00f6nd\u00fcrebilir.<\/li>\n<li>Toplu g\u00f6nderimler i\u00e7in <strong>ba\u011flant\u0131 ve g\u00f6nderim h\u0131zlar\u0131n\u0131 kademeli art\u0131rmak<\/strong> ve gerekiyorsa <a href=\"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/\">dedicated IP \u0131s\u0131tma ve itibar y\u00f6netimi<\/a> stratejileri kullanmak gerekir.<\/li>\n<\/ul>\n<h3><span id=\"450_451_452_Yine_soft_bounce_ama_dikkate_alinmali\">450 \/ 451 \/ 452: Yine soft bounce ama dikkate al\u0131nmal\u0131<\/span><\/h3>\n<ul>\n<li><strong>450 4.2.0 Mailbox temporarily unavailable<\/strong><br \/>Al\u0131c\u0131 kutusu ge\u00e7ici olarak kilitli veya kullan\u0131lam\u0131yor.<\/li>\n<li><strong>451 4.3.0 Temporary local problem<\/strong><br \/>Al\u0131c\u0131 sunucunun i\u00e7 problemi (disk, servis, konfig\u00fcrasyon). Genelde sizlik bir durum yoktur.<\/li>\n<li><strong>452 4.2.2 Insufficient system storage<\/strong><br \/>Al\u0131c\u0131 sunucuda disk\/kota problemi.<\/li>\n<\/ul>\n<p>Bu kodlar\u0131 g\u00f6r\u00fcyorsan\u0131z, MTA\u2019n\u0131z zaten tekrar deneyecektir. Ancak ayn\u0131 al\u0131c\u0131ya g\u00fcnlerce hep ayn\u0131 kod d\u00f6n\u00fcyorsa, listelerde bu adresleri \u201csorunlu\u201d i\u015faretleyip manuel takip etmekte fayda var.<\/p>\n<h3><span id=\"552_553_ve_digerleri_Kota_boyut_ve_adres_hatalari\">552 \/ 553 ve di\u011ferleri: Kota, boyut ve adres hatalar\u0131<\/span><\/h3>\n<ul>\n<li><strong>552 5.2.2 Over quota \/ Mailbox full<\/strong><br \/>Al\u0131c\u0131 kutusunun kotas\u0131 tamamen dolu.<\/li>\n<li><strong>552 5.3.4 Message size exceeds fixed limit<\/strong><br \/>Ekleriniz veya mailiniz al\u0131c\u0131 sunucunun izin verdi\u011finden b\u00fcy\u00fck.<\/li>\n<li><strong>553 5.1.1 Mailbox name not allowed<\/strong><br \/>Adres format\u0131 desteklenmiyor ya da politikaya ayk\u0131r\u0131.<\/li>\n<\/ul>\n<p>\u00d6zellikle b\u00fcy\u00fck ekler i\u00e7eren tasar\u0131m dosyalar\u0131, katalog PDF\u2019leri vb. payla\u015f\u0131yorsan\u0131z, 552 kodlar\u0131n\u0131 s\u0131k g\u00f6rebilirsiniz. Bu durumda ekleri do\u011frudan g\u00f6ndermek yerine, <strong>download linki<\/strong> payla\u015fmak daha sa\u011fl\u0131kl\u0131 olur.<\/p>\n<h2><span id=\"Gelen_bounce_mesajini_dogru_okumak\">Gelen bounce mesaj\u0131n\u0131 do\u011fru okumak<\/span><\/h2>\n<p>\u00c7o\u011fu kullan\u0131c\u0131, posta kutusuna d\u00fc\u015fen geri d\u00f6n\u00fc\u015f iletisini g\u00f6r\u00fcr g\u00f6rmez kapat\u0131yor. Oysa as\u0131l alt\u0131n madeniniz, bu bounce mail\u2019in <strong>tam metni<\/strong> i\u00e7inde sakl\u0131.<\/p>\n<h3><span id=\"Hangi_alanlara_bakmalisiniz\">Hangi alanlara bakmal\u0131s\u0131n\u0131z?<\/span><\/h3>\n<ul>\n<li><strong>Subject<\/strong>: \u00c7o\u011funlukla &#8220;Mail delivery failed&#8221;, &#8220;Undelivered Mail Returned to Sender&#8221; gibi ba\u015fl\u0131klar g\u00f6r\u00fcrs\u00fcn\u00fcz.<\/li>\n<li><strong>Final-Recipient<\/strong>: Tam olarak hangi adrese teslim edilemedi\u011fini g\u00f6sterir.<\/li>\n<li><strong>Action<\/strong>: Genellikle <strong>failed<\/strong>, <strong>delayed<\/strong> veya <strong>relayed<\/strong> yazar. &#8220;failed&#8221; \u2192 hard bounce.<\/li>\n<li><strong>Status<\/strong>: Geli\u015fmi\u015f durum kodu (\u00f6r. 5.1.1, 4.7.0).<\/li>\n<li><strong>Diagnostic-Code<\/strong>: En kritik b\u00f6l\u00fcm. As\u0131l hata mesaj\u0131 burada.<\/li>\n<li><strong>Remote-MTA<\/strong>: Hangi uzak sunucudan hata d\u00f6nd\u00fc\u011f\u00fcn\u00fc g\u00f6sterir.<\/li>\n<\/ul>\n<h3><span id=\"Ornek_bir_bounce_mesaji_nasil_gorunur\">\u00d6rnek bir bounce mesaj\u0131 nas\u0131l g\u00f6r\u00fcn\u00fcr?<\/span><\/h3>\n<pre>Final-Recipient: rfc822; info@ornekfirma.com\nAction: failed\nStatus: 5.1.1\nRemote-MTA: dns; mx.ornekfirma.com\nDiagnostic-Code: smtp; 550 5.1.1 &lt;info@ornekfirma.com&gt;: Recipient address rejected: User unknown<\/pre>\n<p>Bu mesajdan net olarak \u015funlar\u0131 \u00e7\u0131karabiliriz:<\/p>\n<ul>\n<li>Adres: <code>info@ornekfirma.com<\/code><\/li>\n<li>Hata tipi: <strong>5.1.1 \u2192 kullan\u0131c\u0131 yok<\/strong><\/li>\n<li>Sunucu: <code>mx.ornekfirma.com<\/code> bu cevab\u0131 d\u00f6nd\u00fcrm\u00fc\u015f<\/li>\n<\/ul>\n<p>Dolay\u0131s\u0131yla bu adresi liste d\u0131\u015f\u0131na alman\u0131z, hem gereksiz tekrar denemeleri hem de itibar kayb\u0131n\u0131 \u00f6nleyecektir.<\/p>\n<h2><span id=\"Adim_adim_teshis_rehberi_Hata_kodundan_cozume_giden_yol\">Ad\u0131m ad\u0131m te\u015fhis rehberi: Hata kodundan \u00e7\u00f6z\u00fcme giden yol<\/span><\/h2>\n<p>\u015eimdi pratik bir checklist \u00fczerinden gidelim. DCHost taraf\u0131nda bir m\u00fc\u015fterimizin e\u2011posta problemi oldu\u011funda biz genellikle \u015fu s\u0131rayla ilerliyoruz:<\/p>\n<h3><span id=\"1_Hata_kodunu_ve_Diagnostic-Code_satirini_not_edin\">1. Hata kodunu ve Diagnostic-Code sat\u0131r\u0131n\u0131 not edin<\/span><\/h3>\n<ul>\n<li>\u00d6nce 3 basamakl\u0131 kodu (421, 550, 554\u2026) ve varsa <strong>5.x.x \/ 4.x.x<\/strong> detay\u0131n\u0131 not al\u0131n.<\/li>\n<li>Ard\u0131ndan <strong>Diagnostic-Code<\/strong> sat\u0131r\u0131ndaki c\u00fcmleyi kelime kelime okuyun. &#8220;User unknown&#8221;, &#8220;Mailbox full&#8221;, &#8220;Client host blocked&#8221;, &#8220;Spam content&#8221; gibi anahtar kelimeler size do\u011frudan sebebi s\u00f6yler.<\/li>\n<\/ul>\n<h3><span id=\"2_Adres_hatasi_mi_alan_adi_hatasi_mi\">2. Adres hatas\u0131 m\u0131, alan ad\u0131 hatas\u0131 m\u0131?<\/span><\/h3>\n<ul>\n<li><strong>5.1.1 \/ User unknown<\/strong> ise: Adres bozuk ya da al\u0131c\u0131 yok. Listenizi temizleyin.<\/li>\n<li>Ayn\u0131 etki alan\u0131ndaki <em>t\u00fcm adreslerde<\/em> hata al\u0131yorsan\u0131z, alan ad\u0131n\u0131n <strong>MX kay\u0131tlar\u0131n\u0131<\/strong> kontrol edin.<\/li>\n<li>Alan ad\u0131 yaz\u0131m hatalar\u0131n\u0131 (\u00f6r. <code>hotmial.com<\/code>) g\u00f6zden ge\u00e7irin.<\/li>\n<\/ul>\n<p>DNS tarafta neyin nas\u0131l olmas\u0131 gerekti\u011fini bilmiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-nedir-a-aaaa-cname-mx-txt-ve-srv-rehberi\/\">DNS kay\u0131tlar\u0131 A, MX, CNAME ve TXT rehberimiz<\/a> burada \u00e7ok i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"3_SPAM_politika_kaynakli_mi\">3. SPAM \/ politika kaynakl\u0131 m\u0131?<\/span><\/h3>\n<p>Diagnostic-Code i\u00e7inde \u015fu kelimeleri g\u00f6r\u00fcyorsan\u0131z:<\/p>\n<ul>\n<li><strong>&#8220;blocked&#8221;<\/strong>, <strong>&#8220;blacklisted&#8221;<\/strong>, <strong>&#8220;RBL&#8221;<\/strong>, <strong>&#8220;spam&#8221;<\/strong>, <strong>&#8220;policy&#8221;<\/strong>, <strong>&#8220;5.7.1&#8221;<\/strong><\/li>\n<\/ul>\n<p>Bu, b\u00fcy\u00fck ihtimalle:<\/p>\n<ul>\n<li>IP\u2019nizin veya alan ad\u0131n\u0131z\u0131n itibar problemi oldu\u011fu<\/li>\n<li>SPF\/DKIM\/DMARC kay\u0131tlar\u0131n\u0131z\u0131n eksik ya da \u00e7eli\u015fkili oldu\u011fu<\/li>\n<li>A\u015f\u0131r\u0131 agresif i\u00e7erik\/spam filtrelerine tak\u0131ld\u0131\u011f\u0131n\u0131z<\/li>\n<\/ul>\n<p>anlam\u0131na gelir. Bu noktada \u015fu ad\u0131mlar\u0131 takip etmek iyi bir ba\u015flang\u0131\u00e7t\u0131r:<\/p>\n<ol>\n<li><strong>SPF, DKIM, DMARC kay\u0131tlar\u0131n\u0131<\/strong> g\u00fcncelleyin ve test edin. Bunun i\u00e7in hem temel hem geli\u015fmi\u015f seviye rehberler haz\u0131rlad\u0131k:\n<ul>\n<li><a href=\"https:\/\/www.dchost.com\/blog\/temel-spf-dkim-ve-dmarc-ayarlari-kucuk-isletmeler-icin-adim-adim-e-posta-dogrulama\/\">K\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in temel SPF, DKIM ve DMARC ayarlar\u0131<\/a><\/li>\n<li><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 teslim edilebilirli\u011fi art\u0131rma rehberi<\/a><\/li>\n<\/ul>\n<\/li>\n<li>IP\u2019nizi hangi RBL listelerinde g\u00f6rd\u00fc\u011f\u00fcn\u00fcz\u00fc kontrol edin ve gerekiyorsa delist ba\u015fvurusu yap\u0131n.<\/li>\n<li>G\u00f6nderim h\u0131z\u0131n\u0131 ve hacmini kademeli art\u0131r\u0131n, \u00f6zellikle yeni bir IP veya alan ad\u0131 kullan\u0131yorsan\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/\">dedicated IP \u0131s\u0131tma ve itibar y\u00f6netimi<\/a> kurallar\u0131na uyun.<\/li>\n<\/ol>\n<h3><span id=\"4_Icerik_ve_ek_boyutlarini_gozden_gecirin\">4. \u0130\u00e7erik ve ek boyutlar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/span><\/h3>\n<ul>\n<li>&#8220;Message size exceeds&#8221; veya <strong>552 5.3.4<\/strong> g\u00f6r\u00fcyorsan\u0131z, eklerinizi k\u00fc\u00e7\u00fclt\u00fcn ya da linkle payla\u015f\u0131n.<\/li>\n<li>\u015e\u00fcpheli g\u00f6r\u00fclebilecek kelimeleri, a\u015f\u0131r\u0131 say\u0131da linki ve y\u00fcr\u00fct\u00fclebilir ek uzant\u0131lar\u0131n\u0131 (exe, js, scr vb.) temizleyin.<\/li>\n<li>HTML e\u2011postan\u0131zda mail body\u2019nin \u00e7ok da\u011f\u0131n\u0131k\/bozuk olmamas\u0131na dikkat edin; baz\u0131 spam filtreleri &#8220;garip&#8221; HTML yap\u0131s\u0131n\u0131 riskli g\u00f6r\u00fcr.<\/li>\n<\/ul>\n<h3><span id=\"5_Rate_limit_ve_baglanti_sinirlarini_kontrol_edin\">5. Rate limit ve ba\u011flant\u0131 s\u0131n\u0131rlar\u0131n\u0131 kontrol edin<\/span><\/h3>\n<p>421 veya 4.7.x ile birlikte &#8220;too many connections&#8221;, &#8220;rate limit exceeded&#8221; gibi ifadeler varsa:<\/p>\n<ul>\n<li>Toplu g\u00f6nderim yapan uygulaman\u0131z\u0131n <strong>saniyedeki mail say\u0131s\u0131n\u0131<\/strong> d\u00fc\u015f\u00fcr\u00fcn.<\/li>\n<li>Ayn\u0131 al\u0131c\u0131 alan ad\u0131na k\u0131sa s\u00fcrede a\u015f\u0131r\u0131 mail g\u00f6ndermeyin; g\u00f6nderimi zamana yay\u0131n.<\/li>\n<li>SMTP oturumlar\u0131n\u0131 daha verimli kullan\u0131n (tek ba\u011flant\u0131da birden fazla mail g\u00f6ndermek gibi).<\/li>\n<\/ul>\n<h3><span id=\"6_Sorun_sizde_degil_karsi_tarafta_olabilir\">6. Sorun sizde de\u011fil kar\u015f\u0131 tarafta olabilir<\/span><\/h3>\n<p>&#8220;Temporary local problem&#8221;, &#8220;insufficient system storage&#8221; gibi iletiler genellikle al\u0131c\u0131 sunucunun i\u00e7 meselesidir. Yine de:<\/p>\n<ul>\n<li>\u00d6nemli bir m\u00fc\u015fteri ise, onlara ekran g\u00f6r\u00fcnt\u00fcs\u00fcyle birlikte hata detay\u0131n\u0131 iletip kendi BT ekiplerine paslay\u0131n.<\/li>\n<li>Kritik operasyonel mailler (fatura, \u015fifre s\u0131f\u0131rlama vb.) i\u00e7in, bu tip durumlarda <strong>yedek al\u0131c\u0131 adres<\/strong> veya farkl\u0131 kanal (SMS, portal bildirimi) gibi alternatifler olu\u015fturun.<\/li>\n<\/ul>\n<h3><span id=\"7_Itibar_sorunu_derinse_kurtarma_plani_yapin\">7. \u0130tibar sorunu derinse, kurtarma plan\u0131 yap\u0131n<\/span><\/h3>\n<p>E\u011fer \u00e7ok say\u0131da al\u0131c\u0131dan 554 5.7.1 benzeri retler geliyorsa, bu art\u0131k sadece tekil bir sorun de\u011fil, <strong>genel e\u2011posta itibar\u0131n\u0131z\u0131n zarar g\u00f6rd\u00fc\u011f\u00fc<\/strong> anlam\u0131na gelir. B\u00f6yle durumlar i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-itibarini-kurtarma-rehberi-blacklist-delisting-postmaster-araclari-ve-guvenli-ip-isitma-nasil-kurtarici-olur\/\">e\u2011posta itibar\u0131n\u0131 kurtarma rehberinde<\/a> blacklist\u2019ten \u00e7\u0131k\u0131\u015f, postmaster ara\u00e7lar\u0131 ve g\u00fcvenli IP \u0131s\u0131tma ad\u0131mlar\u0131n\u0131 u\u00e7tan uca bulabilirsiniz.<\/p>\n<h2><span id=\"Bu_hatalarin_surekli_tekrarlanmamasi_icin_onleyici_adimlar\">Bu hatalar\u0131n s\u00fcrekli tekrarlanmamas\u0131 i\u00e7in \u00f6nleyici ad\u0131mlar<\/span><\/h2>\n<h3><span id=\"Temiz_liste_yonetimi_ve_hard_bouncelari_hizlica_ayiklama\">Temiz liste y\u00f6netimi ve hard bounce\u2019lar\u0131 h\u0131zl\u0131ca ay\u0131klama<\/span><\/h3>\n<ul>\n<li>Hard bounce (5xx) d\u00f6nen adresleri d\u00fczenli aral\u0131klarla listelerinizden \u00e7\u0131kar\u0131n.<\/li>\n<li>Eski ve pasif listeleri tekrar tekrar kullanmay\u0131n; \u00e7ift onayl\u0131 (double opt\u2011in) sistemler tercih edin.<\/li>\n<li>&#8220;User unknown&#8221; hatas\u0131 ald\u0131\u011f\u0131n\u0131z adreslere asla tekrar mail g\u00f6ndermeyin; bu, spam skorunuzu olumsuz etkiler.<\/li>\n<\/ul>\n<h3><span id=\"DNS_ve_dogrulama_kayitlarini_bir_kere_duzgun_kurup_izleyin\">DNS ve do\u011frulama kay\u0131tlar\u0131n\u0131 bir kere d\u00fczg\u00fcn kurup izleyin<\/span><\/h3>\n<ul>\n<li>Alan ad\u0131n\u0131z\u0131n SPF, DKIM, DMARC, rDNS kay\u0131tlar\u0131n\u0131 bir defa do\u011fru kurup, de\u011fi\u015fiklik yapt\u0131\u011f\u0131n\u0131zda mutlaka tekrar test edin.<\/li>\n<li>DMARC raporlar\u0131n\u0131 (RUA\/RUF) analiz ederek kimler ad\u0131n\u0131za mail g\u00f6nderiyor, hangi sunucular s\u0131k hata al\u0131yor g\u00f6rebilirsiniz. Bu konuda daha derinlemesine bilgi i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/dmarc-raporlari-aggregate-ve-forensic-analiz-ile-pnonedan-prejecte-gecis\/\">DMARC raporlar\u0131 ile p=none\u2019dan p=reject\u2019e ge\u00e7i\u015f rehberimizi<\/a> inceleyebilirsiniz.<\/li>\n<\/ul>\n<h3><span id=\"Altyapiyi_is_yukune_gore_planlayin\">Altyap\u0131y\u0131 i\u015f y\u00fck\u00fcne g\u00f6re planlay\u0131n<\/span><\/h3>\n<p>K\u00fc\u00e7\u00fck hacimli kurumsal mailler i\u00e7in <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> \u00fczerindeki standart mail servisi \u00e7o\u011fu zaman yeterli olur. Ancak:<\/p>\n<ul>\n<li>Yo\u011fun transactional mail (\u015fifre s\u0131f\u0131rlama, sipari\u015f bildirimleri)<\/li>\n<li>Y\u00fcksek hacimli pazarlama kampanyalar\u0131<\/li>\n<li>Birden \u00e7ok markan\u0131n ayn\u0131 IP\u2019den mail atmas\u0131<\/li>\n<\/ul>\n<p>gibi senaryolarda, <strong>ayr\u0131 bir e\u2011posta sunucusu<\/strong>, <strong>VPS<\/strong> veya <strong>dedicated sunucu<\/strong> \u00fczerinde daha kontroll\u00fc bir SMTP altyap\u0131s\u0131 kurmak \u00e7ok daha sa\u011fl\u0131kl\u0131 olabilir. DCHost olarak bu tip senaryolarda; IP planlamas\u0131, reverse DNS, SPF\/DKIM\/DMARC, rate limit ve yedeklilik tasar\u0131m\u0131n\u0131 birlikte kurguluyoruz.<\/p>\n<h3><span id=\"Izleme_ve_log_analizi_kulturu_olusturun\">\u0130zleme ve log analizi k\u00fclt\u00fcr\u00fc olu\u015fturun<\/span><\/h3>\n<ul>\n<li>Mail kuyru\u011fu boyutlar\u0131n\u0131 ve hata oranlar\u0131n\u0131 d\u00fczenli takip edin.<\/li>\n<li>Belirli bir al\u0131c\u0131 alan ad\u0131na g\u00f6nderilen maillerde hata oran\u0131 h\u0131zla y\u00fckseliyorsa, otomatik alarm kurun.<\/li>\n<li>Loglar\u0131 sadece &#8220;sorun \u00e7\u0131kt\u0131\u011f\u0131nda&#8221; de\u011fil, periyodik olarak da kontrol etmek, itibar problemleri b\u00fcy\u00fcmeden m\u00fcdahale etmenizi sa\u011flar.<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_ve_DCHost_ile_yol_haritaniz\">Sonu\u00e7 ve DCHost ile yol haritan\u0131z<\/span><\/h2>\n<p>E\u2011posta hata kodlar\u0131 ilk bak\u0131\u015fta karma\u015f\u0131k g\u00f6r\u00fcnebilir; ama asl\u0131nda her biri, altyap\u0131n\u0131z\u0131n size g\u00f6nderdi\u011fi detayl\u0131 bir sa\u011fl\u0131k raporu gibidir. <strong>550<\/strong> size adres veya kullan\u0131c\u0131 sorunu oldu\u011funu, <strong>554<\/strong> itibar ve politika duvar\u0131na \u00e7arpt\u0131\u011f\u0131n\u0131z\u0131, <strong>421<\/strong> ise \u00e7o\u011fu zaman h\u0131z veya ge\u00e7ici sunucu problemlerini anlat\u0131r. Bu kodlar\u0131 do\u011fru okuyabildi\u011finizde, hem m\u00fc\u015fterilerinizle ileti\u015fiminiz kesintiye u\u011framaz hem de alan ad\u0131n\u0131z\u0131n ve IP\u2019lerinizin itibar\u0131n\u0131 uzun vadede korumu\u015f olursunuz.<\/p>\n<p>DCHost ekibi olarak, sadece sunucu ve hosting sa\u011flamakla kalm\u0131yor; <strong>e\u2011posta teslim edilebilirli\u011fi, SPF\/DKIM\/DMARC yap\u0131land\u0131rmas\u0131, IP \u0131s\u0131tma ve itibar y\u00f6netimi<\/strong> gibi konularda da yan\u0131n\u0131zda duruyoruz. \u0130ster payla\u015f\u0131ml\u0131 hosting, ister <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ya da colocation altyap\u0131s\u0131 kullan\u0131n; mail trafi\u011finizi sa\u011fl\u0131kl\u0131 tutmak i\u00e7in yukar\u0131daki ad\u0131mlar\u0131 uygulaman\u0131z ve d\u00fczenli olarak loglara\/bounce mesajlar\u0131na bakman\u0131z yeterli.<\/p>\n<p>E\u011fer elinizde \u00e7\u00f6zemedi\u011finiz karma\u015f\u0131k bir bounce \u00f6rne\u011fi varsa, DCHost paneliniz \u00fczerinden destek talebi a\u00e7\u0131p ilgili hata mesaj\u0131n\u0131 bizimle payla\u015fabilirsiniz. Birlikte, <strong>kodu \u2192 sebebi \u2192 \u00e7\u00f6z\u00fcm\u00fc<\/strong> netle\u015ftirecek ve e\u2011posta altyap\u0131n\u0131z\u0131 uzun vadede sorunsuz \u00e7al\u0131\u015facak \u015fekilde g\u00fc\u00e7lendirece\u011fiz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 E\u2011posta hata kodlar\u0131 neden bu kadar can s\u0131k\u0131c\u0131 ama bir o kadar da de\u011ferli?2 SMTP ve bounce mant\u0131\u011f\u0131n\u0131 k\u0131saca anlamak2.1 SMTP durum kodlar\u0131n\u0131n yap\u0131s\u0131: 2xx, 4xx, 5xx2.2 Hard bounce vs soft bounce3 En s\u0131k g\u00f6r\u00fclen hata kodlar\u0131: 550, 554, 421 ve di\u011ferleri3.1 550 serisi hatalar: Yanl\u0131\u015f adres mi, politika m\u0131, DNS mi?3.2 554 hatalar\u0131: [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4441,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4440","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\/4440","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=4440"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4440\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4441"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}