{"id":1864,"date":"2026-07-30T10:13:24","date_gmt":"2026-07-30T07:13:24","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1864"},"modified":"2026-08-03T10:32:23","modified_gmt":"2026-08-03T10:32:23","slug":"smtp-25-465-ve-587-portlarindan-hangisi-wordpress-icin-dogru","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/smtp-25-465-ve-587-portlarindan-hangisi-wordpress-icin-dogru\/","title":{"rendered":"SMTP 25, 465 ve 587 Portlar\u0131ndan Hangisi WordPress \u0130\u00e7in Do\u011fru?"},"content":{"rendered":"

Bir teknisyen \u015fifreleme modunu de\u011fi\u015ftirmeden 25, 465 ve 587 portlar\u0131n\u0131 s\u0131rayla deniyor. Her deneme farkl\u0131 bir nedenle ba\u015far\u0131s\u0131z oluyor; fakat hi\u00e7biri sa\u011flay\u0131c\u0131n\u0131n WordPress i\u00e7in hangi ayar\u0131 destekledi\u011fini g\u00f6stermiyor.<\/p>\n

Host ad\u0131, port ve TLS modu tek bir yap\u0131land\u0131rma olarak ele al\u0131nmal\u0131d\u0131r. Yaln\u0131z port numaras\u0131na bakarak g\u00fcvenli oturumun nas\u0131l ba\u015flayaca\u011f\u0131 anla\u015f\u0131lamaz.<\/p>\n

\n\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Bu konu ne anlama gelir?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Neden \u00f6nemlidir ve ne zaman kullan\u0131l\u0131r?<\/a><\/li>\n
  4. Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/a><\/li>\n
  5. \u0130leri teknik yol<\/a><\/li>\n
  6. Riskler, s\u0131k hatalar, yedekleme ve geri alma<\/a><\/li>\n
  7. AIOWS nas\u0131l yard\u0131mc\u0131 olur? AIOWS SMTP Y\u00f6neticisi<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    Bu konu ne anlama gelir?<\/h2>\n

    587 portu \u00e7o\u011funlukla STARTTLS kullanan kimlik do\u011frulamal\u0131 g\u00f6nderim i\u00e7in tercih edilir. 465 portunda TLS genellikle ba\u011flant\u0131 ba\u015flarken devreye girer. 25 portu ise daha \u00e7ok posta sunucular\u0131 aras\u0131ndaki aktar\u0131m veya sa\u011flay\u0131c\u0131n\u0131n \u00f6zel relay hizmeti i\u00e7indir ve hosting firmalar\u0131 taraf\u0131ndan s\u0131k\u00e7a engellenir.<\/p>\n

    Do\u011fru bilgi sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel belgesindedir. A\u011f eri\u015fimi, TLS ba\u011flant\u0131s\u0131, kimlik do\u011frulama, g\u00f6nderen yetkisi ve teslimat ayr\u0131 ayr\u0131 kontrol edilmelidir.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    Sa\u011flay\u0131c\u0131 smtp.example.com:587<\/code> adresini STARTTLS ile kullanmay\u0131 istiyor. WordPress sunucusundan 587 \u00e7\u0131k\u0131\u015f\u0131 engelli. 465\u2019e ge\u00e7ildi\u011finde ise yanl\u0131\u015f host ad\u0131 nedeniyle sertifika hatas\u0131 olu\u015fuyor. \u00c7\u00f6z\u00fcm rastgele port denemek de\u011fil, belgelenen yolu a\u00e7t\u0131rmak ve do\u011fru host ad\u0131n\u0131 kullanmakt\u0131r.<\/p>\n

    Neden \u00f6nemlidir ve ne zaman kullan\u0131l\u0131r?<\/h2>\n

    Port ile \u015fifreleme modunun uyu\u015fmamas\u0131 kimlik bilgilerini riske atabilir, anla\u015f\u0131lmas\u0131 g\u00fc\u00e7 TLS hatalar\u0131 \u00fcretebilir veya WordPress\u2019i yanl\u0131\u015f relay\u2019e ba\u011flayabilir. Ba\u011flant\u0131 zaman a\u015f\u0131m\u0131na u\u011fruyorsa, kimlik do\u011frulamadan \u00f6nce TLS hatas\u0131 olu\u015fuyorsa ya da sa\u011flay\u0131c\u0131 se\u00e7ilen g\u00f6nderim hizmetini reddediyorsa bu ayr\u0131m incelenmelidir.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/h2>\n
      \n
    1. SMTP host ad\u0131n\u0131, portu, \u015fifreleme modunu ve kimlik do\u011frulama y\u00f6ntemini sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel belgesinden al\u0131n.<\/li>\n
    2. Bu ayarlar\u0131 WordPress\u2019e aynen girin.<\/li>\n
    3. Hosting ortam\u0131n\u0131n se\u00e7ilen porta giden TCP ba\u011flant\u0131lar\u0131na izin verdi\u011fini do\u011frulay\u0131n.<\/li>\n
    4. Kontroll\u00fc bir WordPress iletisi g\u00f6nderip TLS ba\u011flant\u0131s\u0131n\u0131, kimlik do\u011frulamay\u0131, sa\u011flay\u0131c\u0131 kabul\u00fcn\u00fc ve teslimat\u0131 kontrol edin.<\/li>\n
    5. Sertifika do\u011frulamas\u0131n\u0131 hi\u00e7bir a\u015famada kapatmay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri teknik yol<\/h2>\n

      DNS \u00e7\u00f6z\u00fcmlemesini, TCP ba\u011flant\u0131s\u0131n\u0131, TLS handshake\u2019ini, sertifika ad\u0131n\u0131 ve zincirini, SMTP kar\u015f\u0131lamas\u0131n\u0131, gerekiyorsa STARTTLS\u2019i, kimlik do\u011frulamay\u0131, MAIL FROM kabul\u00fcn\u00fc, sa\u011flay\u0131c\u0131 kayd\u0131n\u0131 ve teslimat\u0131 s\u0131rayla izleyin. Sonu\u00e7lar de\u011fi\u015fiyorsa IPv4 ve IPv6 yollar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n. Kimlik bilgileri temizlenmi\u015f ba\u011flant\u0131 kayd\u0131, firewall zaman a\u015f\u0131m\u0131n\u0131 TLS veya SMTP hatas\u0131ndan ay\u0131r\u0131r.<\/p>\n

      Riskler, s\u0131k hatalar, yedekleme ve geri alma<\/h2>\n

      Sertifika do\u011frulamas\u0131n\u0131 kapatmay\u0131n, kimlik bilgilerini \u015fifrelenmemi\u015f ba\u011flant\u0131 \u00fczerinden g\u00f6ndermeyin ve 25 portunu otomatik olarak g\u00f6nderim portu saymay\u0131n. H\u0131zl\u0131 ve tekrarl\u0131 port denemeleri sa\u011flay\u0131c\u0131n\u0131n g\u00fcvenlik \u00f6nlemlerini tetikleyebilir. Yeni ayar TLS g\u00fcvenli\u011fini d\u00fc\u015f\u00fcr\u00fcr veya postay\u0131 keserse son belgelenmi\u015f yap\u0131land\u0131rmaya d\u00f6n\u00fcn.<\/p>\n

      \n

      AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n

      AIOWS SMTP Y\u00f6neticisi<\/h2>\n

      AIOWS SMTP Y\u00f6neticisi, WordPress taraf\u0131ndaki host ad\u0131, port, \u015fifreleme ve kimlik do\u011frulama ayarlar\u0131n\u0131 birlikte g\u00f6rmeyi sa\u011flar. Kontroll\u00fc testler ve tan\u0131 bilgileri ba\u011flant\u0131, TLS, kimlik do\u011frulama ve sa\u011flay\u0131c\u0131 hatalar\u0131n\u0131 ay\u0131rmaya yard\u0131mc\u0131 olur.<\/p>\n

      Sa\u011flay\u0131c\u0131n\u0131n belgeledi\u011fi ayarlar\u0131 kullan\u0131n ve ard\u0131ndan WordPress\u2019in olu\u015fturdu\u011fu ger\u00e7ek bir iletiyi s\u0131nay\u0131n. TCP ba\u011flant\u0131s\u0131n\u0131n kurulmas\u0131 tek ba\u015f\u0131na yeterli de\u011fildir; sertifika do\u011frulanmal\u0131, kimlik do\u011frulama tamamlanmal\u0131 ve sa\u011flay\u0131c\u0131 g\u00f6ndereni kabul etmelidir.<\/p>\n

      AIOWS, hosting firmas\u0131n\u0131n engelledi\u011fi portu a\u00e7amaz, sa\u011flay\u0131c\u0131n\u0131n sertifikas\u0131n\u0131 d\u00fczeltemez ve relay politikas\u0131n\u0131 a\u015famaz. Bu katmanlar\u0131 ilgili hosting firmas\u0131 veya posta hizmeti d\u00fczeltmelidir. TLS do\u011frulamas\u0131n\u0131 kapatmak g\u00fcvenli bir \u00e7\u00f6z\u00fcm de\u011fildir.<\/p>\n

      AIOWS SMTP Y\u00f6neticisi’ni inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n

      \u0130lgili AIOWS yaz\u0131lar\u0131<\/h2>\n