{"id":125,"date":"2026-10-08T09:01:24","date_gmt":"2026-10-08T06:01:24","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/smtp-submission-port-587-465-farklari\/"},"modified":"2026-10-08T09:01:24","modified_gmt":"2026-10-08T06:01:24","slug":"smtp-submission-port-587-465-farklari","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/smtp-submission-port-587-465-farklari\/","title":{"rendered":"SMTP Submission Nedir? Port 587 ve 465 Aras\u0131ndaki Farklar ve Do\u011fru Ayar"},"content":{"rendered":"<h2>SMTP submission ne demektir?<\/h2>\n<p>\u015eirket e-postalar\u0131nda \u201cSMTP\u201d genellikle iki farkl\u0131 i\u015fi ifade eder: Sunucular\u0131n birbirine e-posta teslim etti\u011fi SMTP trafi\u011fi ve kullan\u0131c\u0131lar\u0131n (Outlook, telefon, uygulama, CRM, yaz\u0131c\u0131, web sitesi formu gibi) e-posta g\u00f6ndermek i\u00e7in sunucuya ba\u011fland\u0131\u011f\u0131 \u201csubmission\u201d trafi\u011fi. SMTP submission, bir kullan\u0131c\u0131n\u0131n veya uygulaman\u0131n kimlik do\u011frulama yaparak (kullan\u0131c\u0131 ad\u0131\/parola gibi) e-posta g\u00f6ndermesidir. Bu ayr\u0131m \u00f6nemlidir \u00e7\u00fcnk\u00fc submission taraf\u0131nda g\u00fcvenlik beklentileri daha y\u00fcksektir: Kimlik do\u011frulama zorunlulu\u011fu, \u015fifreli ba\u011flant\u0131 kullan\u0131m\u0131 ve k\u00f6t\u00fcye kullan\u0131m\u0131n engellenmesi gibi.<\/p>\n<p>Bir\u00e7ok teslim edilebilirlik ve g\u00fcvenlik sorununun k\u00f6k\u00fc, kullan\u0131c\u0131lar\u0131n yanl\u0131\u015f porta ba\u011flanmas\u0131, TLS\u2019in do\u011fru ba\u015flat\u0131lamamas\u0131 veya sunucunun \u201ca\u00e7\u0131k relay\u201d gibi riskli bir \u015fekilde yap\u0131land\u0131r\u0131lmas\u0131d\u0131r. Bu nedenle 587 ve 465 portlar\u0131n\u0131n ne i\u015fe yarad\u0131\u011f\u0131n\u0131 netle\u015ftirmek, hem IT ekipleri hem de profesyonel e-posta kullan\u0131c\u0131lar\u0131 i\u00e7in kal\u0131c\u0131 bir kazan\u0131md\u0131r.<\/p>\n<h2>Port 587 ve port 465: Temel fark nedir?<\/h2>\n<p>Port 587, modern e-posta mimarisinde SMTP submission i\u00e7in \u00f6nerilen standart porttur. Bu portta ba\u011flant\u0131 genellikle d\u00fcz ba\u015flar ve ard\u0131ndan STARTTLS komutuyla TLS\u2019e y\u00fckseltilir. Port 465 ise \u201cimplicit TLS\u201d yakla\u015f\u0131m\u0131yla \u00e7al\u0131\u015f\u0131r: Ba\u011flant\u0131 en ba\u015ftan itibaren TLS ile \u015fifreli olarak kurulur. \u0130kisi de pratikte g\u00fcvenli g\u00f6nderim amac\u0131yla kullan\u0131l\u0131r; ancak davran\u0131\u015f bi\u00e7imleri ve uyumluluk detaylar\u0131 farkl\u0131d\u0131r.<\/p>\n<h3>Port 587 (Submission + STARTTLS)<\/h3>\n<ul>\n<li><strong>Kullan\u0131m amac\u0131:<\/strong> \u0130stemciden sunucuya kimlik do\u011frulamal\u0131 e-posta g\u00f6nderimi.<\/li>\n<li><strong>\u015eifreleme modeli:<\/strong> Ba\u011flant\u0131 kurulur, ard\u0131ndan STARTTLS ile \u015fifreleme ba\u015flat\u0131l\u0131r.<\/li>\n<li><strong>Avantaj\u0131:<\/strong> Standart ve yayg\u0131n; kurumsal politikalarda \u201cTLS zorunlu\u201d kural\u0131 kolay uygulan\u0131r.<\/li>\n<li><strong>Dikkat edilmesi gereken:<\/strong> \u0130stemci STARTTLS\u2019i desteklemeli ve \u201cTLS kullan\u201d se\u00e7ene\u011fi do\u011fru i\u015faretlenmelidir.<\/li>\n<\/ul>\n<h3>Port 465 (SMTPS + Implicit TLS)<\/h3>\n<ul>\n<li><strong>Kullan\u0131m amac\u0131:<\/strong> \u0130stemciden sunucuya \u015fifreli e-posta g\u00f6nderimi (pratikte submission).<\/li>\n<li><strong>\u015eifreleme modeli:<\/strong> TLS, ba\u011flant\u0131n\u0131n ilk an\u0131ndan itibaren aktiftir.<\/li>\n<li><strong>Avantaj\u0131:<\/strong> Baz\u0131 a\u011flarda STARTTLS engellenebildi\u011finde veya istemci davran\u0131\u015flar\u0131 tutars\u0131z oldu\u011funda daha \u201cnet\u201d bir TLS kurulumu sa\u011flayabilir.<\/li>\n<li><strong>Dikkat edilmesi gereken:<\/strong> \u0130stemcide genellikle \u201cSSL\/TLS\u201d se\u00e7ilmelidir; \u201cSTARTTLS\u201d se\u00e7ilirse ba\u011flant\u0131 ba\u015far\u0131s\u0131z olabilir.<\/li>\n<\/ul>\n<h2>Neden do\u011fru port se\u00e7imi \u015firketler i\u00e7in kritiktir?<\/h2>\n<p>Yanl\u0131\u015f port veya yanl\u0131\u015f TLS se\u00e7imi sadece ba\u011flant\u0131 hatas\u0131 \u00fcretmez; bazen daha sinsi sonu\u00e7lar do\u011furur. \u00d6rne\u011fin kullan\u0131c\u0131, e-posta g\u00f6ndermeyi ba\u015faramad\u0131\u011f\u0131 i\u00e7in webmail d\u0131\u015f\u0131na \u00e7\u0131kar, farkl\u0131 ve kontrols\u00fcz bir y\u00f6ntemle (ki\u015fisel e-posta, \u00fc\u00e7\u00fcnc\u00fc taraf uygulama) i\u015f ak\u0131\u015f\u0131n\u0131 s\u00fcrd\u00fcrmeye \u00e7al\u0131\u015f\u0131r. Bu da veri y\u00f6netimi, denetim ve kurumsal ileti\u015fim a\u00e7\u0131s\u0131ndan risk yaratabilir.<\/p>\n<p>Ayr\u0131ca yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f g\u00f6nderim, sunucunun kimlik do\u011frulama olmadan iletim yapmas\u0131na (a\u00e7\u0131k relay) yol a\u00e7acak \u015fekilde hatal\u0131 kural\/port kullan\u0131m\u0131n\u0131 tetikleyebilir. A\u00e7\u0131k relay do\u011frudan spam suistimaline, IP itibar\u0131n\u0131n d\u00fc\u015fmesine ve e-postalar\u0131n spam\u2019e d\u00fc\u015fmesine kadar uzanan zincirleme etkiler yaratabilir.<\/p>\n<h2>Hangi senaryoda 587, hangi senaryoda 465 tercih edilmeli?<\/h2>\n<p>Genel kural olarak, kurumsal istemci g\u00f6nderimlerinde \u00f6nce 587 tercih edilir. 587 hem dok\u00fcmantasyonlarda hem de modern istemcilerde \u201csubmission\u201d se\u00e7ene\u011fi olarak beklenen yakla\u015f\u0131md\u0131r. 465 ise \u00f6zellikle baz\u0131 eski istemcilerde veya a\u011f ko\u015fullar\u0131nda daha sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131 i\u00e7in ikinci se\u00e7enek olarak de\u011ferlendirilebilir.<\/p>\n<h3>587\u2019yi tercih edin (\u00f6nerilen)<\/h3>\n<ul>\n<li>Outlook, Apple Mail, Thunderbird gibi modern istemciler kullan\u0131l\u0131yorsa<\/li>\n<li>Mobil cihazlarda \u201cSTARTTLS\/TLS\u201d se\u00e7enekleri net bir \u015fekilde sunuluyorsa<\/li>\n<li>\u015eirket i\u00e7inde standardizasyon hedefleniyorsa (tek dok\u00fcman, tek ayar)<\/li>\n<li>Kimlik do\u011frulama ve TLS kullan\u0131m\u0131n\u0131 politika haline getirmek isteniyorsa<\/li>\n<\/ul>\n<h3>465\u2019i de\u011ferlendirin<\/h3>\n<ul>\n<li>\u0130stemci veya cihaz STARTTLS ile sorun \u00e7\u0131kar\u0131yor ve ba\u011flant\u0131 karars\u0131zsa<\/li>\n<li>Baz\u0131 a\u011flarda STARTTLS pazarl\u0131\u011f\u0131 (upgrade) kesintiye u\u011fruyorsa<\/li>\n<li>Uygulama yaln\u0131zca \u201cSSL\/TLS\u201d se\u00e7ene\u011fiyle port 465\u2019te d\u00fczg\u00fcn \u00e7al\u0131\u015f\u0131yorsa<\/li>\n<\/ul>\n<h2>En s\u0131k yap\u0131lan yanl\u0131\u015flar (ve sonu\u00e7lar\u0131)<\/h2>\n<h3>1) Yanl\u0131\u015f TLS se\u00e7imi<\/h3>\n<p>587 kullan\u0131rken istemcide \u201cSSL\/TLS\u201d se\u00e7mek bazen ba\u011flant\u0131n\u0131n kurulamamas\u0131na neden olur; 587\u2019de \u00e7o\u011fu kurulum \u201cSTARTTLS\u201d veya \u201cTLS (STARTTLS)\u201d \u015feklindedir. 465\u2019te ise tam tersi g\u00f6r\u00fcl\u00fcr: \u201cSSL\/TLS\u201d gerekir, STARTTLS se\u00e7ilirse hatayla kar\u015f\u0131la\u015f\u0131l\u0131r.<\/p>\n<h3>2) Kimlik do\u011frulamas\u0131n\u0131 kapal\u0131 b\u0131rakmak<\/h3>\n<p>Submission portlar\u0131 i\u00e7in kimlik do\u011frulama neredeyse her zaman zorunludur. \u201cSunucum kimlik do\u011frulamas\u0131 gerektiriyor\u201d benzeri se\u00e7enek kapal\u0131 kal\u0131rsa, sunucu g\u00f6nderimi reddedebilir veya istemci s\u00fcrekli parola sorarak kullan\u0131c\u0131 deneyimini bozar.<\/p>\n<h3>3) G\u00f6nderen adresi ile oturum a\u00e7ma hesab\u0131n\u0131n uyumsuzlu\u011fu<\/h3>\n<p>Bir\u00e7ok sistem, g\u00fcvenlik ve suistimali \u00f6nlemek i\u00e7in \u201cFrom\u201d adresinin, oturum a\u00e7an hesapla veya izinli alias\/da\u011f\u0131t\u0131m kurgusuyla uyumlu olmas\u0131n\u0131 bekler. Kullan\u0131c\u0131 farkl\u0131 bir g\u00f6nderici adresi se\u00e7ti\u011finde g\u00f6nderim reddedilebilir veya al\u0131c\u0131 taraf\u0131nda g\u00fcven sinyalleri zay\u0131flayabilir.<\/p>\n<h3>4) A\u011f g\u00fcvenlik cihazlar\u0131nda yanl\u0131\u015f kural<\/h3>\n<p>\u015eirket a\u011f\u0131nda outbound kurallar\u0131nda 587\/465 engellenmi\u015f olabilir. Kullan\u0131c\u0131lar bu durumda rastgele portlara y\u00f6nelir ya da ge\u00e7ici \u00e7\u00f6z\u00fcmler \u00fcretir. IT ekipleri i\u00e7in do\u011fru yakla\u015f\u0131m, hangi portlar\u0131n izinli oldu\u011funu netle\u015ftirmek ve bunu u\u00e7 kullan\u0131c\u0131 dok\u00fcman\u0131na yans\u0131tmakt\u0131r.<\/p>\n<h2>Do\u011fru istemci ayar\u0131 i\u00e7in pratik kontrol listesi<\/h2>\n<p>A\u015fa\u011f\u0131daki kontrol listesi, istemciden ba\u011f\u0131ms\u0131z olarak do\u011fru submission kurgusunu do\u011frulaman\u0131za yard\u0131mc\u0131 olur:<\/p>\n<ol>\n<li><strong>Sunucu ad\u0131:<\/strong> Sa\u011flay\u0131c\u0131n\u0131z\u0131n verdi\u011fi SMTP sunucu ad\u0131n\u0131 kullan\u0131n (\u00f6r. mail alan ad\u0131n\u0131z veya sa\u011flanan host ad\u0131).<\/li>\n<li><strong>Port:<\/strong> \u00d6ncelik 587; gerekirse 465.<\/li>\n<li><strong>\u015eifreleme:<\/strong> 587 i\u00e7in STARTTLS\/TLS; 465 i\u00e7in SSL\/TLS (implicit).<\/li>\n<li><strong>Kimlik do\u011frulama:<\/strong> A\u00e7\u0131k olmal\u0131. Kullan\u0131c\u0131 ad\u0131 genellikle tam e-posta adresidir.<\/li>\n<li><strong>Parola:<\/strong> G\u00fcncel ve do\u011fru. Parola de\u011fi\u015ftiyse t\u00fcm cihazlarda g\u00fcncelleyin.<\/li>\n<li><strong>G\u00f6nderen adresi:<\/strong> Kullan\u0131c\u0131n\u0131n yetkili oldu\u011fu adres\/alias ile g\u00f6nderin.<\/li>\n<li><strong>Test:<\/strong> \u015eirket d\u0131\u015f\u0131 bir adrese deneme g\u00f6nderimi yap\u0131n ve gecikme\/bounce var m\u0131 kontrol edin.<\/li>\n<\/ol>\n<h2>Teslim edilebilirlik a\u00e7\u0131s\u0131ndan port se\u00e7imi bir \u201csihirli \u00e7\u00f6z\u00fcm\u201d de\u011fildir<\/h2>\n<p>587 veya 465 kullanmak, tek ba\u015f\u0131na e-postalar\u0131n inbox\u2019a d\u00fc\u015fece\u011fi anlam\u0131na gelmez. Teslim edilebilirlik daha geni\u015f bir resimdir: SPF\/DKIM\/DMARC do\u011frulamas\u0131, alan ad\u0131 ve IP itibar\u0131, i\u00e7erik kalitesi, g\u00f6nderim hacmi ve al\u0131c\u0131lar\u0131n etkile\u015fimi gibi fakt\u00f6rler rol oynar. Ancak do\u011fru submission yap\u0131land\u0131rmas\u0131, en temel noktay\u0131 sa\u011flar: G\u00f6nderimin g\u00fcvenli, kimli\u011fi do\u011frulanm\u0131\u015f ve tutarl\u0131 \u015fekilde yap\u0131lmas\u0131.<\/p>\n<h2>Uygulamalar ve cihazlar i\u00e7in \u00f6zel notlar<\/h2>\n<h3>\u00c7ok fonksiyonlu yaz\u0131c\u0131lar ve eski cihazlar<\/h3>\n<p>Yaz\u0131c\u0131, taray\u0131c\u0131 veya eski uygulamalar bazen STARTTLS\u2019i desteklemez. B\u00f6yle bir durumda 465 ile implicit TLS destekleniyorsa tercih edilebilir. Hi\u00e7 TLS desteklemeyen cihazlarda ise IT ekipleri, riskleri de\u011ferlendirerek ayr\u0131 bir \u00e7\u00f6z\u00fcm tasarlamal\u0131 (\u00f6rne\u011fin g\u00fcvenli bir i\u00e7 aktar\u0131c\u0131 \u00fczerinden g\u00f6nderim) ve cihaz\u0131 internetten do\u011frudan \u00e7\u0131karmamay\u0131 d\u00fc\u015f\u00fcnmelidir.<\/p>\n<h3>Web siteleri ve uygulamalar<\/h3>\n<p>Bir web sitesi formu, uygulama sunucusu veya CRM entegrasyonu \u00fczerinden e-posta g\u00f6nderirken de ayn\u0131 prensip ge\u00e7erlidir: Kimlik do\u011frulamal\u0131 submission ve TLS. Uygulama taraf\u0131nda hata g\u00fcnl\u00fckleri (log) incelenmeli; \u201cTLS handshake failed\u201d, \u201cauthentication failed\u201d gibi hatalar genellikle port\/\u015fifreleme uyumsuzlu\u011funu i\u015faret eder.<\/p>\n<h2>Sonu\u00e7: Standartla\u015ft\u0131r\u0131n, dok\u00fcmante edin, d\u00fczenli test edin<\/h2>\n<p>Kurumsal e-posta operasyonlar\u0131nda k\u00fc\u00e7\u00fck g\u00f6r\u00fcnen istemci ayarlar\u0131, b\u00fcy\u00fck destek y\u00fck\u00fc ve g\u00fcvenlik riski do\u011furabilir. En iyi yakla\u015f\u0131m; \u015firket i\u00e7inde 587 + STARTTLS\u2019yi varsay\u0131lan olarak standardize etmek, 465\u2019i uyumluluk alternatifi olarak tan\u0131mlamak, kimlik do\u011frulama ve TLS\u2019i zorunlu k\u0131lmak ve de\u011fi\u015fikliklerden sonra d\u00fczenli g\u00f6nderim testleri yapmakt\u0131r.<\/p>\n<p>MX1Mail gibi profesyonel bir i\u015f e-posta platformuna ge\u00e7erken veya mevcut kurulumunuzu iyile\u015ftirirken, kullan\u0131c\u0131 dok\u00fcmanlar\u0131n\u0131z\u0131 bu port\/\u015fifreleme mant\u0131\u011f\u0131yla g\u00fcncellemek; helpdesk taleplerini azalt\u0131r, g\u00f6nderim sorunlar\u0131n\u0131 h\u0131zla te\u015fhis etmenizi sa\u011flar ve g\u00fcvenli g\u00f6nderim al\u0131\u015fkanl\u0131\u011f\u0131n\u0131 kurum geneline yayar.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kurumsal e-posta g\u00f6nderiminde SMTP submission mant\u0131\u011f\u0131n\u0131, 587 ile 465 aras\u0131ndaki farklar\u0131, TLS se\u00e7eneklerini ve do\u011fru istemci ayarlar\u0131n\u0131 ad\u0131m ad\u0131m \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":[296,226,231],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-e-posta-altyapisi","tag-e-posta-istemcisi-ayarlari","tag-smtp","tag-tls"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/125","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=125"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}