{"id":198,"date":"2026-10-26T09:01:35","date_gmt":"2026-10-26T06:01:35","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/e-posta-govdesinde-turkce-karakterler-neden-bozulur-7bit-8bit-8bitmime-quoted-printable-base64\/"},"modified":"2026-10-26T09:01:35","modified_gmt":"2026-10-26T06:01:35","slug":"e-posta-govdesinde-turkce-karakterler-neden-bozulur-7bit-8bit-8bitmime-quoted-printable-base64","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/e-posta-govdesinde-turkce-karakterler-neden-bozulur-7bit-8bit-8bitmime-quoted-printable-base64\/","title":{"rendered":"E-Posta G\u00f6vdesinde T\u00fcrk\u00e7e Karakterler Neden Bozulur? 7bit\/8bit, 8BITMIME, Quoted-Printable ve Base64 Rehberi"},"content":{"rendered":"<h2>Sorun neye benzer ve neden \u00f6nemlidir?<\/h2>\n<p>Kurumsal e-postada \u201cT\u00fcrk\u00e7e karakterler bozuk geliyor\u201d \u015fik\u00e2yeti \u00e7o\u011fu zaman konu sat\u0131r\u0131ndan (subject) de\u011fil, e-posta g\u00f6vdesinden (body) kaynaklan\u0131r. Al\u0131c\u0131, mesaj i\u00e7inde \u201c\u015f, \u011f, \u00fc, \u0131, \u00f6, \u00e7\u201d gibi karakterlerin soru i\u015fareti, kare kutu veya anlams\u0131z semboller olarak g\u00f6r\u00fcnd\u00fc\u011f\u00fcn\u00fc s\u00f6yler. Bazen sadece baz\u0131 cihazlarda (\u00f6rne\u011fin mobilde do\u011fru, Outlook\u2019ta bozuk) ortaya \u00e7\u0131kar. Bu durum yaln\u0131zca okunabilirli\u011fi de\u011fil; m\u00fc\u015fteri ileti\u015fimini, destek s\u00fcre\u00e7lerini, s\u00f6zle\u015fme\/teklif metinlerinin do\u011frulu\u011funu ve markaya olan g\u00fcveni de etkiler.<\/p>\n<p>Bu tip bozulmalar\u0131n temelinde genellikle MIME i\u00e7erik ba\u015fl\u0131klar\u0131 (Content-Type, charset), i\u00e7erik aktar\u0131m kodlamas\u0131 (Content-Transfer-Encoding) ve sunucular aras\u0131 SMTP yetenek pazarl\u0131\u011f\u0131 (\u00f6zellikle 8BITMIME) bulunur. Do\u011fru te\u015fhis i\u00e7in \u201cT\u00fcrk\u00e7e karakter var\u201d demek yetmez; mesaj\u0131n hangi a\u015famada hangi forma d\u00f6n\u00fc\u015ft\u00fcr\u00fcld\u00fc\u011f\u00fcn\u00fc anlamak gerekir.<\/p>\n<h2>\u00d6nce temel kavramlar: charset, 7bit\/8bit ve MIME<\/h2>\n<h3>Charset (karakter seti) nedir?<\/h3>\n<p>Charset, metindeki baytlar\u0131n hangi harflere kar\u015f\u0131l\u0131k geldi\u011fini belirleyen kural setidir. Bug\u00fcn pratikte en do\u011fru ve en geni\u015f uyumluluk sa\u011flayan se\u00e7im UTF-8\u2019dir. Ancak baz\u0131 sistemler h\u00e2l\u00e2 ISO-8859-9 veya Windows-1254 gibi kodlamalara d\u00fc\u015febilir; bu da farkl\u0131 istemcilerin farkl\u0131 yorumlamas\u0131na yol a\u00e7abilir.<\/p>\n<h3>7bit ve 8bit ne demektir?<\/h3>\n<p>Klasik SMTP d\u00fcnyas\u0131nda g\u00fcvenli aktar\u0131m varsay\u0131m\u0131 7-bit ASCII idi. Yani her bayt\u0131n en \u00fcst biti s\u0131f\u0131r kabul edilirdi. T\u00fcrk\u00e7e karakterler gibi ASCII d\u0131\u015f\u0131 karakterler UTF-8 ile g\u00f6nderildi\u011finde metin 8-bit baytlar i\u00e7erir. E\u011fer aktar\u0131m yolu 8-bit veriyi g\u00fcvenle ta\u015f\u0131yam\u0131yorsa (veya arada 7-bit\u2019e zorlayan bir bile\u015fen varsa), metin bozulur.<\/p>\n<h3>MIME neden gerekli?<\/h3>\n<p>MIME, e-postan\u0131n sadece \u201cd\u00fcz ASCII metin\u201d olmad\u0131\u011f\u0131n\u0131 anlatan standartlar\u0131n b\u00fct\u00fcn\u00fc gibidir. MIME ba\u015fl\u0131klar\u0131; mesaj\u0131n t\u00fcr\u00fcn\u00fc (text\/plain, text\/html), charset bilgisini (utf-8) ve g\u00f6vdenin nas\u0131l kodland\u0131\u011f\u0131n\u0131 (quoted-printable, base64 gibi) belirtir. \u0130stemci, bu ba\u015fl\u0131klara bakarak metni do\u011fru \u00e7\u00f6zer.<\/p>\n<h2>8BITMIME: Sunucular aras\u0131 \u201c8-bit kabul ediyor musun?\u201d pazarl\u0131\u011f\u0131<\/h2>\n<p>Bir posta sunucusu di\u011ferine SMTP ile teslimat yaparken, kar\u015f\u0131 taraf\u0131n hangi yetenekleri destekledi\u011fini EHLO yan\u0131t\u0131nda g\u00f6r\u00fcr. Bu yeteneklerden biri <strong>8BITMIME<\/strong>\u2019d\u0131r. Kar\u015f\u0131 taraf 8BITMIME destekliyorsa, g\u00f6nderici 8-bit g\u00f6vdeyi (\u00f6rne\u011fin UTF-8 metin) 7-bit\u2019e \u00e7evirmeden iletebilir.<\/p>\n<p>8BITMIME yoksa ya da aradaki gateway \u201cben 8-bit ta\u015f\u0131m\u0131yorum\u201d diyorsa, g\u00f6nderici genellikle g\u00f6vdeyi 7-bit uyumlu h\u00e2le getirmek i\u00e7in MIME transfer encoding uygular. \u0130\u015fte bozulmalar\u0131n \u00f6nemli bir k\u0131sm\u0131 burada olur: baz\u0131 sistemler d\u00f6n\u00fc\u015f\u00fcm\u00fc yanl\u0131\u015f yapar, baz\u0131lar\u0131 charset\u2019i yanl\u0131\u015f etiketler, baz\u0131lar\u0131 da d\u00f6n\u00fc\u015f\u00fcm yapmadan 8-bit\u2019i zorla ge\u00e7irir ve yol \u00fczerinde k\u0131r\u0131lma ya\u015fan\u0131r.<\/p>\n<h2>Content-Transfer-Encoding: quoted-printable ve base64 ne i\u015fe yarar?<\/h2>\n<p>MIME d\u00fcnyas\u0131nda g\u00f6vde verisini \u201cta\u015f\u0131nabilir\u201d h\u00e2le getirmenin iki yayg\u0131n yolu vard\u0131r:<\/p>\n<ul>\n<li><strong>quoted-printable<\/strong>: Metin a\u011f\u0131rl\u0131kl\u0131 i\u00e7erik i\u00e7in idealdir. ASCII karakterlerin b\u00fcy\u00fck k\u0131sm\u0131 oldu\u011fu gibi kal\u0131r; 8-bit karakterler ve baz\u0131 \u00f6zel baytlar =XX bi\u00e7iminde kodlan\u0131r. T\u00fcrk\u00e7e karakterli normal bir e-posta metninde genellikle en okunabilir ve verimli se\u00e7enektir.<\/li>\n<li><strong>base64<\/strong>: \u0130kili veriler (PDF, g\u00f6rsel) i\u00e7in \u00e7ok uygundur. Metin i\u00e7in de kullan\u0131labilir; ancak t\u00fcm i\u00e7erik kodland\u0131\u011f\u0131 i\u00e7in insan g\u00f6z\u00fcyle okunmas\u0131 zorla\u015f\u0131r ve baz\u0131 eski\/yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f sistemlerde sat\u0131r katlama (line wrapping) hatalar\u0131 daha s\u0131k g\u00f6r\u00fcl\u00fcr.<\/li>\n<\/ul>\n<p>G\u00f6vde bozulmalar\u0131nda s\u0131k kar\u015f\u0131la\u015f\u0131lan senaryolar \u015funlard\u0131r: mesaj UTF-8\u2019dir ama header\u2019da charset yanl\u0131\u015f yaz\u0131lm\u0131\u015ft\u0131r; quoted-printable uygulanm\u0131\u015ft\u0131r ama sat\u0131r sonlar\u0131 yanl\u0131\u015f katlanm\u0131\u015ft\u0131r; base64 uygulanm\u0131\u015ft\u0131r ama al\u0131c\u0131 tarafta yanl\u0131\u015f \u00e7\u00f6z\u00fclm\u00fc\u015ft\u00fcr; ya da 8BITMIME desteklenmedi\u011fi h\u00e2lde mesaj \u201c8bit\u201d olarak etiketlenip iletilmi\u015ftir.<\/p>\n<h2>En yayg\u0131n k\u00f6k nedenler (ve nas\u0131l ay\u0131rt edilir?)<\/h2>\n<h3>1) Yanl\u0131\u015f charset etiketi: UTF-8 i\u00e7erik, ISO-8859-9 diye i\u015faretlenmi\u015f<\/h3>\n<p>Bu durumda ayn\u0131 mesaj baz\u0131 istemcilerde \u201ck\u0131smen do\u011fru\u201d g\u00f6r\u00fcn\u00fcrken baz\u0131lar\u0131nda tamamen bozulur. \u00c7\u00fcnk\u00fc istemcinin otomatik alg\u0131lama davran\u0131\u015f\u0131 farkl\u0131 olabilir. Te\u015fhis i\u00e7in e-posta header\u2019\u0131nda Content-Type sat\u0131r\u0131na bak\u0131l\u0131r: <strong>Content-Type: text\/plain; charset=&#8230;<\/strong>. Mesaj g\u00f6vdesi UTF-8 iken charset farkl\u0131ysa bozulma ka\u00e7\u0131n\u0131lmazd\u0131r.<\/p>\n<h3>2) Transfer encoding yok veya hatal\u0131: 8-bit veri 7-bit yolda k\u0131r\u0131l\u0131yor<\/h3>\n<p>E\u011fer mesaj 8-bit karakterler i\u00e7eriyor ama Content-Transfer-Encoding \u201c7bit\u201d ya da hi\u00e7 yoksa, aradaki sistemler veriyi de\u011fi\u015ftirebilir. Baz\u0131 ge\u00e7itler 8-bit\u2019i \u201ctemizlemek\u201d i\u00e7in karakterleri d\u00fc\u015f\u00fcr\u00fcr, baz\u0131lar\u0131 soru i\u015faretine \u00e7evirir.<\/p>\n<h3>3) Quoted-printable sat\u0131r katlama hatalar\u0131<\/h3>\n<p>Quoted-printable\u2019da sat\u0131r sonlar\u0131nda \u201csoft line break\u201d i\u00e7in = i\u015fareti kullan\u0131l\u0131r. Baz\u0131 yanl\u0131\u015f uygulamalar sat\u0131r sonlar\u0131n\u0131 hatal\u0131 ekler veya UTF-8 \u00e7ok baytl\u0131 karakterin ortas\u0131nda b\u00f6ler. Sonu\u00e7: \u00f6zellikle uzun sat\u0131rlarda T\u00fcrk\u00e7e karakterler bozulur. Bu, \u201ck\u0131sa mesajlarda sorun yok, uzun imza\/\u015fablonda bozuluyor\u201d diye kendini g\u00f6sterebilir.<\/p>\n<h3>4) HTML g\u00f6vde ve yanl\u0131\u015f meta\/charset uyumsuzlu\u011fu<\/h3>\n<p>Mesaj Content-Type\u2019\u0131 text\/html ve charset=utf-8 g\u00f6r\u00fcnse bile, HTML i\u00e7inde farkl\u0131 bir meta etiketi (\u00f6rne\u011fin iso-8859-9) varsa baz\u0131 istemciler HTML meta\u2019s\u0131n\u0131 \u00f6ncelikli kabul edebilir. Sonu\u00e7 istemciye g\u00f6re de\u011fi\u015fen bozulmalard\u0131r.<\/p>\n<h3>5) \u015eablon\/uygulama taraf\u0131nda yanl\u0131\u015f kodlama<\/h3>\n<p>CRM, form, otomasyon veya \u00f6zel bir uygulama e-posta \u00fcretirken metni asl\u0131nda Windows-1254 olarak tutup \u201cutf-8\u201d diye etiketleyebilir (veya tam tersi). Bu tip sorunlar \u00e7o\u011fu zaman sadece belirli bir kaynaktan gelen iletilerde g\u00f6r\u00fcl\u00fcr; insan kullan\u0131c\u0131lar\u0131n yazd\u0131\u011f\u0131 normal e-postalar sorunsuzdur.<\/p>\n<h2>Pratik te\u015fhis ad\u0131mlar\u0131: IT ekibi neye bakmal\u0131?<\/h2>\n<h3>1) Sorunu yeniden \u00fcret ve \u201cham kaynak\u201d (raw) i\u00e7eri\u011fi al<\/h3>\n<p>Bozuk gelen mesaj\u0131n ham kayna\u011f\u0131 olmadan kesin konu\u015fmak zordur. Kullan\u0131c\u0131dan mesaj kayna\u011f\u0131n\u0131 (headers + body) payla\u015fmas\u0131n\u0131 isteyin.<\/p>\n<h3>2) Header\u2019larda \u00fc\u00e7 sat\u0131r\u0131 kontrol et<\/h3>\n<ul>\n<li><strong>Content-Type<\/strong>: text\/plain m\u0131 text\/html m\u0131? charset ne?<\/li>\n<li><strong>Content-Transfer-Encoding<\/strong>: quoted-printable m\u0131 base64 m\u00fc 8bit mi?<\/li>\n<li><strong>MIME-Version<\/strong>: genellikle 1.0 olmal\u0131; yoksa baz\u0131 istemciler farkl\u0131 davranabilir.<\/li>\n<\/ul>\n<h3>3) Mesaj\u0131n hangi a\u015famada de\u011fi\u015fti\u011fini bul<\/h3>\n<p>G\u00f6nderici uygulama m\u0131, g\u00f6nderici mail sunucusu mu, bir outbound relay\/gateway mi, al\u0131c\u0131 taraftaki antispam\/AV mi, yoksa istemci mi d\u00f6n\u00fc\u015ft\u00fcr\u00fcyor? \u201cReceived:\u201d header sat\u0131rlar\u0131 ile mesaj\u0131n ge\u00e7ti\u011fi noktalar\u0131 s\u0131ralayarak hangi hop\u2019tan sonra bozulma ortaya \u00e7\u0131k\u0131yor anla\u015f\u0131labilir.<\/p>\n<h3>4) \u0130stemci farklar\u0131n\u0131 test et<\/h3>\n<p>Ayn\u0131 mesaj\u0131 webmail, mobil ve masa\u00fcst\u00fc istemcide kar\u015f\u0131la\u015ft\u0131r\u0131n. E\u011fer sadece bir istemcide bozuksa sorun o istemcinin kodlama yorumunda veya HTML meta\/charset \u00e7ak\u0131\u015fmas\u0131nda olabilir.<\/p>\n<h2>Do\u011fru yap\u0131land\u0131rma i\u00e7in \u00f6nerilen yakla\u015f\u0131m<\/h2>\n<ul>\n<li><strong>Varsay\u0131lan charset olarak UTF-8 standardize edin<\/strong>. \u015eablonlar, imzalar ve otomasyon metinleri dahil.<\/li>\n<li><strong>Text i\u00e7eriklerde quoted-printable tercih edin<\/strong>. Metin a\u011f\u0131rl\u0131kl\u0131 ileti\u015fimde hem uyumluluk hem okunabilirlik sa\u011flar.<\/li>\n<li><strong>HTML i\u00e7erikte charset uyumunu koruyun<\/strong>: Content-Type charset ile HTML i\u00e7indeki meta charset \u00e7eli\u015fmesin.<\/li>\n<li><strong>Aradaki relay\/gateway\u2019leri en aza indirin<\/strong> veya her bile\u015fenin 8BITMIME\/MIME uyumlu \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun.<\/li>\n<li><strong>\u015eablon \u00fcreten uygulamalar\u0131 kontrol edin<\/strong>: Uygulama katman\u0131nda string kodlamas\u0131, mail k\u00fct\u00fcphanesi ayarlar\u0131 ve \u00e7\u0131kt\u0131 header\u2019lar\u0131 tutarl\u0131 olmal\u0131.<\/li>\n<\/ul>\n<h2>S\u0131k yap\u0131lan hatalar: \u201cH\u0131zl\u0131 \u00e7\u00f6z\u00fcm\u201d diye sorunu b\u00fcy\u00fctenler<\/h2>\n<h3>Her \u015feyi base64 yapmak<\/h3>\n<p>Base64 metni her zaman \u201cdaha g\u00fcvenli ta\u015f\u0131r\u201d gibi d\u00fc\u015f\u00fcn\u00fclse de, yanl\u0131\u015f sat\u0131r katlama uygulamalar\u0131 ve baz\u0131 sistemlerdeki limitler nedeniyle sorunlar\u0131 gizleyip daha zor te\u015fhis edilir h\u00e2le getirebilir. Metin i\u00e7in temel hedef do\u011fru charset + do\u011fru quoted-printable uygulamas\u0131d\u0131r.<\/p>\n<h3>Charset\u2019i rastgele de\u011fi\u015ftirmek<\/h3>\n<p>UTF-8 yerine \u201cT\u00fcrk\u00e7e charset\u201d se\u00e7mek bazen ge\u00e7ici olarak baz\u0131 istemcilerde d\u00fczelmi\u015f gibi g\u00f6r\u00fcn\u00fcr, ama global uyumluluk d\u00fc\u015fer. Modern e-posta ekosisteminde en sa\u011fl\u0131kl\u0131 ortak payda UTF-8\u2019dir.<\/p>\n<h3>Bozulmay\u0131 kullan\u0131c\u0131 hatas\u0131 sanmak<\/h3>\n<p>Bu sorunlar\u0131n \u00e7o\u011fu kullan\u0131c\u0131dan de\u011fil, sistemler aras\u0131 d\u00f6n\u00fc\u015f\u00fcm ve yanl\u0131\u015f etiketlemeden kaynaklan\u0131r. Kullan\u0131c\u0131ya \u201cfarkl\u0131 klavye dene\u201d demek zaman kaybettirir.<\/p>\n<h2>Sonu\u00e7: Standartla\u015ft\u0131rma ve izlenebilirlik bozulmalar\u0131 bitirir<\/h2>\n<p>E-posta g\u00f6vdesinde T\u00fcrk\u00e7e karakter bozulmas\u0131; \u00e7o\u011funlukla 7bit\/8bit uyumsuzlu\u011fu, 8BITMIME deste\u011fi, yanl\u0131\u015f charset etiketi veya hatal\u0131 quoted-printable\/base64 d\u00f6n\u00fc\u015f\u00fcm\u00fcnden do\u011far. Kal\u0131c\u0131 \u00e7\u00f6z\u00fcm, mesaj \u00fcretim noktas\u0131ndan teslimata kadar MIME ba\u015fl\u0131klar\u0131n\u0131n tutarl\u0131 olmas\u0131 ve her hop\u2019ta aktar\u0131m\u0131n bozulmadan s\u00fcrmesidir.<\/p>\n<p>Kurumsal e-posta altyap\u0131n\u0131z\u0131 y\u00f6netirken, benzer karakter kodlama problemlerini h\u0131zl\u0131 te\u015fhis edebilmek i\u00e7in ham mesaj inceleme ve log analizi s\u00fcre\u00e7lerini standartla\u015ft\u0131rmak faydal\u0131d\u0131r. MX1Mail \u00fczerinde e-posta ak\u0131\u015f\u0131yla ilgili sorunlar\u0131 incelerken de ayn\u0131 y\u00f6ntemle (header + g\u00f6vde + hop analizi) hangi a\u015famada d\u00f6n\u00fc\u015f\u00fcm ya\u015fand\u0131\u011f\u0131n\u0131 tespit ederek kal\u0131c\u0131 aksiyon plan\u0131 olu\u015fturabilirsiniz.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>E-posta g\u00f6vdesindeki T\u00fcrk\u00e7e karakter bozulmalar\u0131n\u0131n k\u00f6k nedenlerini anlay\u0131n: 7bit\/8bit fark\u0131, 8BITMIME, MIME charset ve quoted-printable\/base64 kodlamalar\u0131 ile kal\u0131c\u0131 te\u015fhis ad\u0131mlar\u0131.<\/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":[520,226,277],"class_list":["post-198","post","type-post","status-publish","format-standard","hentry","category-e-posta-altyapisi","tag-mime","tag-smtp","tag-teslim-edilebilirlik"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/198","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=198"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/198\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=198"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=198"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}