{"id":194,"date":"2026-10-25T09:01:20","date_gmt":"2026-10-25T06:01:20","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/e-postada-turkce-karakterli-konu-basliklari-neden-bozulur-smtputf8-8bitmime-mime-encoding\/"},"modified":"2026-10-25T09:01:20","modified_gmt":"2026-10-25T06:01:20","slug":"e-postada-turkce-karakterli-konu-basliklari-neden-bozulur-smtputf8-8bitmime-mime-encoding","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/e-postada-turkce-karakterli-konu-basliklari-neden-bozulur-smtputf8-8bitmime-mime-encoding\/","title":{"rendered":"E-Postada T\u00fcrk\u00e7e Karakterli Konu ve Ba\u015fl\u0131klar Neden Bozulur? SMTPUTF8, 8BITMIME ve MIME Encoding Rehberi"},"content":{"rendered":"<h2>T\u00fcrk\u00e7e karakterler neden \u201cbozulur\u201d?<\/h2>\n<p>Kurumsal e-postalarda en s\u0131k g\u00f6r\u00fclen \u015fikayetlerden biri \u015fudur: Konu sat\u0131r\u0131 do\u011fru yaz\u0131lm\u0131\u015ft\u0131r ama al\u0131c\u0131da \u201c\u00c4\u00b0\u00c5\u0178 teklifiniz\u201d, \u201c=?UTF-8?B?&#8230;?=\u201d gibi garip ifadeler g\u00f6r\u00fcn\u00fcr, bazen de tamamen \u201c???\u201c olur. Benzer bozulmalar From\/To g\u00f6r\u00fcnen adlar\u0131nda, otomatik bildirimlerde, imza sat\u0131rlar\u0131nda veya baz\u0131 sistemlerin ekledi\u011fi \u00f6zel header alanlar\u0131nda da ya\u015fanabilir.<\/p>\n<p>Bu sorun \u00e7o\u011fu zaman \u201ckullan\u0131c\u0131n\u0131n klavyesi\u201d veya \u201cOutlook\/Taray\u0131c\u0131 hatas\u0131\u201d de\u011fildir. K\u00f6k neden genellikle e-posta ekosisteminde h\u00e2l\u00e2 bir arada \u00e7al\u0131\u015fan farkl\u0131 d\u00f6nemlerin standartlar\u0131n\u0131n, yanl\u0131\u015f yap\u0131land\u0131rmalar\u0131n ve hatal\u0131 kodlama (encoding) varsay\u0131mlar\u0131n\u0131n \u00e7ak\u0131\u015fmas\u0131d\u0131r. E-postan\u0131n g\u00f6vdesi (body) \u00e7o\u011fu zaman UTF-8\u2019dir ve do\u011fru g\u00f6r\u00fcn\u00fcr; sorun daha \u00e7ok konu sat\u0131r\u0131 ve header alanlar\u0131nda ortaya \u00e7\u0131kar \u00e7\u00fcnk\u00fc header\u2019lar\u0131n nas\u0131l kodlanaca\u011f\u0131 ayr\u0131 kurallara tabidir.<\/p>\n<h2>Temel kavramlar: ASCII, UTF-8 ve iki farkl\u0131 d\u00fcnya<\/h2>\n<h3>1) SMTP\u2019nin tarihsel s\u0131n\u0131rlamas\u0131: 7-bit<\/h3>\n<p>SMTP uzun s\u00fcre 7-bit ASCII odakl\u0131 tasarland\u0131. Bu, g\u00fcvenli varsay\u0131m\u0131n \u201cyaln\u0131zca \u0130ngilizce karakterler\u201d olmas\u0131 demekti. T\u00fcrk\u00e7e karakterler (\u00c7, \u015e, \u0130, \u011f vb.) ASCII d\u0131\u015f\u0131d\u0131r. Bu y\u00fczden \u201c8-bit veri\u201d veya \u201cUTF-8 adres\/ba\u015fl\u0131k\u201d gibi ihtiya\u00e7lar zamanla ek mekanizmalarla \u00e7\u00f6z\u00fcld\u00fc.<\/p>\n<h3>2) UTF-8 i\u00e7erik ba\u015fka, header ba\u015fka<\/h3>\n<p>E-postan\u0131n g\u00f6vdesi genellikle MIME ile tan\u0131mlan\u0131r ve UTF-8 olarak ta\u015f\u0131nabilir. Ancak konu sat\u0131r\u0131 (Subject) ve baz\u0131 header alanlar\u0131 uzun y\u0131llar do\u011frudan \u201cham UTF-8\u201d olarak yaz\u0131lamazd\u0131. Bunun yerine \u201cencoded-word\u201d denen MIME ba\u015fl\u0131k kodlamas\u0131 kullan\u0131l\u0131r: =?charset?encoding?encoded-text?= bi\u00e7imiyle karakter seti ve kodlama a\u00e7\u0131k\u00e7a belirtilir.<\/p>\n<h2>SMTPUTF8 ve 8BITMIME: Ne i\u015fe yararlar, neyi \u00e7\u00f6zmezler?<\/h2>\n<h3>SMTPUTF8 (EAI) nedir?<\/h3>\n<p>SMTPUTF8, e-posta adreslerinde ve SMTP oturumunda UTF-8 karakterleri desteklemeyi hedefleyen geni\u015fletmedir. Uluslararas\u0131 karakterli e-posta adresleri (\u00f6r. ad.soyad@\u015firket.tld gibi) i\u00e7in kritik bir par\u00e7ad\u0131r. Ancak pratikte \u015funu bilmek gerekir: SMTPUTF8 desteklemek, tek ba\u015f\u0131na konu sat\u0131r\u0131n\u0131n her yerde sorunsuz g\u00f6r\u00fcnece\u011fi anlam\u0131na gelmez. \u00c7\u00fcnk\u00fc konu sat\u0131r\u0131 bir header alan\u0131d\u0131r ve header taraf\u0131nda h\u00e2l\u00e2 MIME encoding kurallar\u0131 devrededir. Ayr\u0131ca aradaki her MTA\/MDA\/antispam\/archiver bile\u015feninin bu uzant\u0131y\u0131 d\u00fczg\u00fcn i\u015flemesi gerekir.<\/p>\n<h3>8BITMIME nedir?<\/h3>\n<p>8BITMIME, mesaj g\u00f6vdesinin (body) 8-bit i\u00e7eri\u011fi bozmadan ta\u015f\u0131nabilmesini kolayla\u015ft\u0131r\u0131r. \u00d6zellikle quoted-printable veya base64\u2019e zorunlu d\u00f6n\u00fc\u015f\u00fcm ihtiyac\u0131n\u0131 azaltabilir. Fakat 8BITMIME de \u201cheader sorunlar\u0131n\u0131\u201d otomatik \u00e7\u00f6zmez. Header\u2019larda uygun RFC uyumlu kodlama yap\u0131lm\u0131yorsa, al\u0131c\u0131 sistemler ya yanl\u0131\u015f yorumlar ya da oldu\u011fu gibi \u201ckodlanm\u0131\u015f\u201d ifadeyi kullan\u0131c\u0131ya g\u00f6sterir.<\/p>\n<h2>As\u0131l kritik konu: MIME header encoding (Subject ve g\u00f6r\u00fcnen adlar)<\/h2>\n<h3>Subject sat\u0131r\u0131 nas\u0131l do\u011fru kodlan\u0131r?<\/h3>\n<p>Subject bir header alan\u0131d\u0131r ve ASCII d\u0131\u015f\u0131 karakter i\u00e7eriyorsa, do\u011fru y\u00f6ntem \u201cencoded-word\u201d kullanmakt\u0131r. \u0130ki yayg\u0131n yol vard\u0131r:<\/p>\n<ul>\n<li><strong>Base64 (B)<\/strong>: UTF-8 byte\u2019lar\u0131n\u0131 base64\u2019e \u00e7evirir. Uzun ve karma\u015f\u0131k ba\u015fl\u0131klarda s\u0131k kullan\u0131l\u0131r.<\/li>\n<li><strong>Quoted-Printable (Q)<\/strong>: Daha okunabilir olabilir; bo\u015fluk ve \u00f6zel karakterler belirli bi\u00e7imde ka\u00e7\u0131\u015flan\u0131r.<\/li>\n<\/ul>\n<p>\u00d6nemli nokta \u015fudur: Ba\u015fl\u0131\u011f\u0131 \u00fcreten uygulama (CRM, helpdesk, web uygulamas\u0131, yaz\u0131c\u0131\/cihaz, script) do\u011fru header encoding yapm\u0131yorsa, mail sunucusu her zaman bunu \u201csonradan d\u00fczeltemez\u201d. Baz\u0131 ge\u00e7itler (gateway) veya g\u00fcvenlik katmanlar\u0131 \u201cyeniden yazma\u201d yapabilir ama bu riskli olabilir; \u00e7\u00fcnk\u00fc yanl\u0131\u015f m\u00fcdahale imzalar\u0131 (DKIM) bozabilir veya mesaj\u0131n b\u00fct\u00fcnl\u00fc\u011f\u00fcne zarar verebilir.<\/p>\n<h3>From\/To g\u00f6r\u00fcnen adlar\u0131 neden bozulur?<\/h3>\n<p>\u201cG\u00f6r\u00fcnen ad\u201d k\u0131sm\u0131 (display name) da header\u2019larda ta\u015f\u0131n\u0131r. \u00d6rne\u011fin \u201cMuhasebe \u015eefi\u201d gibi bir ifade de ASCII d\u0131\u015f\u0131 i\u00e7erir ve ayn\u0131 \u015fekilde MIME encoded-word ile kodlanmal\u0131d\u0131r. Baz\u0131 uygulamalar bunu atlar, baz\u0131lar\u0131 yanl\u0131\u015f charset yazar (ISO-8859-9 san\u0131p UTF-8 g\u00f6ndermek gibi), baz\u0131lar\u0131 da iki kez kodlar (double-encoding). Sonu\u00e7 al\u0131c\u0131da bozuk g\u00f6r\u00fcnt\u00fcd\u00fcr.<\/p>\n<h2>Tipik k\u00f6k nedenler ve te\u015fhis yakla\u015f\u0131m\u0131<\/h2>\n<h3>1) Yanl\u0131\u015f charset beyan\u0131<\/h3>\n<p>Mesaj UTF-8\u2019dir ama header\u2019da ISO-8859-1\/9 yaz\u0131yordur (veya tersi). Al\u0131c\u0131 \u201cbeyan edilen\u201d charset\u2019e g\u00f6re \u00e7\u00f6zd\u00fc\u011f\u00fc i\u00e7in karakterler \u00e7orba olur.<\/p>\n<h3>2) Uygulama ham UTF-8 header yaz\u0131yordur<\/h3>\n<p>Baz\u0131 eski k\u00fct\u00fcphaneler, Subject\u2019i do\u011frudan UTF-8 koyar ama encoded-word \u00fcretmez. Baz\u0131 al\u0131c\u0131lar toleransl\u0131d\u0131r, baz\u0131lar\u0131 de\u011fildir; bir noktada bozulma ka\u00e7\u0131n\u0131lmaz hale gelir.<\/p>\n<h3>3) Ara sistem header\u2019\u0131 \u201ctemizler\u201d veya yeniden bi\u00e7imler<\/h3>\n<p>Antispam\/AV, ar\u015fivleme, DLP, ticketing entegrasyonu gibi sistemler bazen header alanlar\u0131n\u0131 normalize eder. Bu s\u00fcre\u00e7te kodlama bozulabilir. \u00d6zellikle \u201cfolding\u201d (sat\u0131r b\u00f6lme) kurallar\u0131 yanl\u0131\u015f uygulan\u0131rsa base64 bloklar\u0131 k\u0131r\u0131labilir.<\/p>\n<h3>4) Double-encoding<\/h3>\n<p>Subject zaten =?UTF-8?B?&#8230;?= iken bir katman bunu tekrar kodlar. Al\u0131c\u0131 bu sefer \u201ckodlanm\u0131\u015f metni\u201d kodlanm\u0131\u015f kabul eder ve kullan\u0131c\u0131ya garip bir g\u00f6r\u00fcn\u00fcm \u00e7\u0131kar.<\/p>\n<h3>5) Test\/otomasyon e-postalar\u0131nda k\u00f6t\u00fc pratik<\/h3>\n<p>Script\u2019lerle SMTP \u00fczerinden mail atan bir\u00e7ok otomasyon, header kodlamas\u0131n\u0131 do\u011fru yapmaz. \u201c\u00c7\u201d gibi karakterler \u00e7\u0131plak halde header\u2019a yaz\u0131l\u0131r. Bu e-postalar bir ortamda do\u011fru g\u00f6r\u00fcn\u00fcrken ba\u015fka bir ortamda bozulabilir.<\/p>\n<h2>Sistematik kontrol listesi (IT ekipleri i\u00e7in)<\/h2>\n<h3>Mesaj kayna\u011f\u0131n\u0131 belirleyin<\/h3>\n<ul>\n<li>Bozuk g\u00f6r\u00fcnen e-posta hangi sistemden \u00e7\u0131k\u0131yor? Kullan\u0131c\u0131 istemcisi mi, web uygulamas\u0131 m\u0131, cihaz m\u0131, CRM mi?<\/li>\n<li>Bozulma her al\u0131c\u0131da m\u0131, belirli al\u0131c\u0131larda m\u0131 g\u00f6r\u00fcl\u00fcyor?<\/li>\n<\/ul>\n<h3>Ham header incelemesi yap\u0131n<\/h3>\n<p>Bozuk bir \u00f6rnek mesaj\u0131n ham kayna\u011f\u0131n\u0131 a\u00e7\u0131n. \u00d6zellikle Subject, From, To, Content-Type ve Content-Transfer-Encoding alanlar\u0131na bak\u0131n. Arad\u0131\u011f\u0131n\u0131z i\u015faretler:<\/p>\n<ul>\n<li>Subject sat\u0131r\u0131nda ASCII d\u0131\u015f\u0131 karakter var m\u0131 ve encoded-word var m\u0131?<\/li>\n<li>Content-Type i\u00e7inde charset do\u011fru mu (\u00f6rn. UTF-8)?<\/li>\n<li>Subject birden fazla sat\u0131ra b\u00f6l\u00fcnm\u00fc\u015fse (folding) kurala uygun mu?<\/li>\n<\/ul>\n<h3>G\u00f6nderim k\u00fct\u00fcphanesi\/uygulama ayarlar\u0131n\u0131 d\u00fczeltin<\/h3>\n<p>\u00c7o\u011fu modern mail k\u00fct\u00fcphanesinde (uygulama taraf\u0131nda) \u201cUTF-8 header encoding\u201d ayar\u0131 vard\u0131r. Hedef, Subject ve g\u00f6r\u00fcnen adlar\u0131n otomatik olarak RFC uyumlu \u015fekilde kodlanmas\u0131d\u0131r. Burada yap\u0131lacak d\u00fczeltme, mail sunucusunda yap\u0131lacak ge\u00e7ici yamalardan genellikle daha kal\u0131c\u0131 ve daha g\u00fcvenlidir.<\/p>\n<h3>\u0130\u00e7erik transfer kodlamas\u0131n\u0131 do\u011fru se\u00e7in<\/h3>\n<p>G\u00f6vde i\u00e7in quoted-printable\/base64\/8bit se\u00e7enekleri vard\u0131r. B\u00fcy\u00fck oranda k\u00fct\u00fcphane do\u011fru se\u00e7im yapar. Ancak baz\u0131 sistemlerde 8bit g\u00f6vde, aradaki eski bir ge\u00e7itte sorun \u00e7\u0131karabilir; bu durumda quoted-printable daha uyumlu bir se\u00e7enek olabilir. Bu karar \u201ct\u00fcm yol\u201d (end-to-end) uyumlulukla verilmelidir.<\/p>\n<h3>Aradaki g\u00fcvenlik katmanlar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/h3>\n<p>Bir g\u00fcvenlik gateway\u2019i veya ar\u015fiv sistemi header\u2019lar\u0131 de\u011fi\u015ftiriyorsa, \u201cheader normalization\u201d veya \u201cMIME repair\u201d benzeri \u00f6zellikler dikkatle incelenmelidir. D\u00fczeltmeye \u00e7al\u0131\u015f\u0131rken daha fazla bozulmaya yol a\u00e7abilir.<\/p>\n<h2>Kal\u0131c\u0131 \u00e7\u00f6z\u00fcm stratejisi: Standartlara yak\u0131n kal\u0131n<\/h2>\n<p>Pratikte en sa\u011fl\u0131kl\u0131 yakla\u015f\u0131m \u015fudur: Header alanlar\u0131nda ASCII d\u0131\u015f\u0131 i\u00e7erik \u00fcretilecekse, bunu mesaj\u0131 \u00fcreten uygulama do\u011fru \u015fekilde MIME encoded-word ile kodlamal\u0131d\u0131r. G\u00f6vdede UTF-8 ve uygun Content-Transfer-Encoding kullan\u0131lmal\u0131d\u0131r. SMTPUTF8 ve 8BITMIME destekleri ise u\u00e7tan uca uyumlulu\u011fu art\u0131r\u0131r ama \u201cyanl\u0131\u015f header \u00fcreten uygulamay\u0131\u201d otomatik olarak d\u00fczeltmez.<\/p>\n<h2>Kurumsal ortamda \u00f6nerilen test senaryolar\u0131<\/h2>\n<ul>\n<li>T\u00fcrk\u00e7e karakterli Subject (\u0130, \u0131, \u015e, \u015f, \u011e, \u011f, \u00c7, \u00e7, \u00d6, \u00f6, \u00dc, \u00fc) i\u00e7eren k\u0131sa ve uzun ba\u015fl\u0131k testleri<\/li>\n<li>From g\u00f6r\u00fcnen ad\u0131nda T\u00fcrk\u00e7e karakter testleri<\/li>\n<li>Farkl\u0131 al\u0131c\u0131 sistemlere (harici domainler, farkl\u0131 istemciler) g\u00f6nderim<\/li>\n<li>\u0130mza (DKIM) kullan\u0131lan ve kullan\u0131lmayan \u00f6rneklerde kar\u015f\u0131la\u015ft\u0131rma<\/li>\n<li>G\u00fcvenlik\/antispam katman\u0131 a\u00e7\u0131kken ve bypass testleri<\/li>\n<\/ul>\n<h2>Sonu\u00e7: Bozuk konu sat\u0131r\u0131 \u201ck\u00fc\u00e7\u00fck\u201d g\u00f6r\u00fcn\u00fcr, b\u00fcy\u00fck sorunlar\u0131n habercisi olabilir<\/h2>\n<p>Konu sat\u0131r\u0131 veya header bozulmas\u0131, \u00e7o\u011fu zaman sadece kullan\u0131c\u0131 deneyimi problemi gibi alg\u0131lan\u0131r. Oysa arka planda standarda ayk\u0131r\u0131 header \u00fcretimi, yanl\u0131\u015f charset beyan\u0131 veya ara sistemlerin MIME\u2019\u0131 hatal\u0131 yeniden yazmas\u0131 gibi daha geni\u015f uyumluluk problemlerini i\u015faret edebilir. Bu tip hatalar; bilet sistemlerinde hatal\u0131 e\u015fle\u015fme, ar\u015fivlemelerde yanl\u0131\u015f indeksleme ve baz\u0131 durumlarda teslim edilebilirlik sorunlar\u0131na kadar uzanabilir.<\/p>\n<p>MX1Mail gibi kurumsal e-posta altyap\u0131s\u0131 kullanan ekipler i\u00e7in en do\u011fru yol, sorunu \u201csunucu her \u015feyi d\u00fczeltir\u201d beklentisiyle de\u011fil; mesaj\u0131 \u00fcreten kaynak uygulamay\u0131 RFC\/MIME kurallar\u0131na uygun hale getirerek ve yol \u00fczerindeki bile\u015fenleri uyumluluk a\u00e7\u0131s\u0131ndan kontrol ederek \u00e7\u00f6zmektir. B\u00f6ylece T\u00fcrk\u00e7e karakterler yaln\u0131zca g\u00f6vdede de\u011fil, konu sat\u0131r\u0131nda ve t\u00fcm header alanlar\u0131nda da tutarl\u0131 g\u00f6r\u00fcn\u00fcr.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>T\u00fcrk\u00e7e karakterli konu sat\u0131r\u0131 ve ba\u015fl\u0131klar\u0131n \u201c???\u201d ya da garip sembollere d\u00f6n\u00fc\u015fmesinin teknik nedenlerini, SMTPUTF8\/8BITMIME ve MIME encoding mant\u0131\u011f\u0131n\u0131 ve kal\u0131c\u0131 \u00e7\u00f6z\u00fcm ad\u0131mlar\u0131n\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[211],"tags":[522,520,471],"class_list":["post-194","post","type-post","status-publish","format-standard","hentry","category-e-posta-altyapisi","tag-e-posta-uyumlulugu","tag-mime","tag-smtputf8"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/194","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/comments?post=194"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/194\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=194"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=194"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=194"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}