{"id":1819,"date":"2026-07-15T13:22:43","date_gmt":"2026-07-15T10:22:43","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1819"},"modified":"2026-08-03T02:25:45","modified_gmt":"2026-08-03T02:25:45","slug":"wordpress-smtp-535-kimlik-dogrulama-hatasi-nasil-cozulur","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-smtp-535-kimlik-dogrulama-hatasi-nasil-cozulur\/","title":{"rendered":"WordPress SMTP 535 Kimlik Do\u011frulama Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?"},"content":{"rendered":"

WordPress posta sunucusuna ula\u015f\u0131yor, ancak y\u00f6netici normal posta kutusu parolas\u0131n\u0131 girdi\u011finde 535 yan\u0131t\u0131 al\u0131yor. Hesap asl\u0131nda uygulama parolas\u0131 veya OAuth istiyor; sa\u011flay\u0131c\u0131 da belirli bir oturum a\u00e7ma kimli\u011fi bekliyor.<\/p>\n

535 kodu sorunun kimlik do\u011frulama a\u015famas\u0131nda oldu\u011funu g\u00f6sterir. \u00c7\u00f6z\u00fcm; rastgele port, parola ve zaman a\u015f\u0131m\u0131 denemelerine de\u011fil, sa\u011flay\u0131c\u0131n\u0131n verdi\u011fi tam yan\u0131ta dayanmal\u0131d\u0131r.<\/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

    SMTP 535, istemci posta sunucusuna ba\u011flan\u0131p oturum a\u00e7may\u0131 denedikten sonra gelen kimlik do\u011frulama reddidir. DNS ve temel a\u011f yolu, SMTP yan\u0131t\u0131 al\u0131nacak kadar \u00e7al\u0131\u015fm\u0131\u015ft\u0131r.<\/p>\n

    Neden; yanl\u0131\u015f kullan\u0131c\u0131 ad\u0131 veya parola, kapal\u0131 temel kimlik do\u011frulama, gereken uygulama parolas\u0131, s\u00fcresi dolmu\u015f OAuth izni, engellenmi\u015f posta kutusu, kapal\u0131 SMTP AUTH ya da hesab\u0131n kullanamad\u0131\u011f\u0131 g\u00f6nderen adresi olabilir.<\/p>\n

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

    Bir Microsoft 365 posta kutusunda web oturumu a\u00e7\u0131labiliyor, fakat SMTP AUTH kapal\u0131 oldu\u011fu i\u00e7in WordPress 535 al\u0131yor. Ba\u015fka bir sitede Google, g\u00fcvenlik politikas\u0131 OAuth veya uygulama parolas\u0131 istedi\u011finden normal hesap parolas\u0131n\u0131 reddediyor.<\/p>\n

    Her iki durumda da portu de\u011fi\u015ftirmek i\u015fe yaramaz. Y\u00f6netici geni\u015fletilmi\u015f durum kodunu ve zaman\u0131 eksiksiz kaydedip sa\u011flay\u0131c\u0131n\u0131n g\u00fcvenlik olay\u0131n\u0131 inceler; ard\u0131ndan ilgili hesap i\u00e7in desteklenen kimlik do\u011frulama y\u00f6ntemini kurar.<\/p>\n

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

    Bu yolu yaln\u0131z sunucu kimlik do\u011frulama s\u0131ras\u0131nda 535 d\u00f6nd\u00fcrd\u00fc\u011f\u00fcnde kullan\u0131n. Ba\u011flant\u0131 zaman a\u015f\u0131m\u0131, sertifika hatas\u0131, oturum sonras\u0131 g\u00f6nderen reddi, h\u0131z s\u0131n\u0131r\u0131 ve al\u0131c\u0131 teslimat sorunu farkl\u0131 a\u015famalard\u0131r.<\/p>\n

    Ba\u015far\u0131l\u0131 oturum a\u00e7ma da teslimat\u0131n kan\u0131t\u0131 de\u011fildir. \u00d6nce sa\u011flay\u0131c\u0131n\u0131n iletiyi kabul etti\u011fini, ard\u0131ndan kontroll\u00fc test posta kutusundaki sonucu ayr\u0131 ayr\u0131 do\u011frulay\u0131n.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/h2>\n
      \n
    1. 535 yan\u0131t\u0131n\u0131n tamam\u0131n\u0131, geni\u015fletilmi\u015f kodu ve zaman\u0131 kaydedin. Logu saklamadan veya payla\u015fmadan \u00f6nce parola ve token\u2019lar\u0131 \u00e7\u0131kar\u0131n.<\/li>\n
    2. SMTP hostunu, portu, TLS modunu, kimlik do\u011frulama y\u00f6ntemini, kullan\u0131c\u0131 ad\u0131 bi\u00e7imini, hesap durumunu ve izinli From adresini do\u011frulay\u0131n.<\/li>\n
    3. Sa\u011flay\u0131c\u0131n\u0131n OAuth, uygulama parolas\u0131 veya a\u00e7\u0131k SMTP AUTH izni isteyip istemedi\u011fini kontrol edin. M\u00fcmk\u00fcnse y\u00f6netilen bir hizmet hesab\u0131 kullan\u0131n.<\/li>\n
    4. Her testte yaln\u0131z bir kimlik ya da politika ayar\u0131n\u0131 de\u011fi\u015ftirin ve denemeyi sa\u011flay\u0131c\u0131n\u0131n oturum a\u00e7ma olay\u0131yla e\u015fle\u015ftirin.<\/li>\n
    5. Parola s\u0131f\u0131rlama veya form g\u00f6nderimi gibi ger\u00e7ek bir WordPress olay\u0131n\u0131 tetikleyin; sa\u011flay\u0131c\u0131 kabul\u00fcn\u00fc ve al\u0131c\u0131 sonucunu ayr\u0131 ayr\u0131 inceleyin.<\/li>\n<\/ol>\n

      \u0130leri teknik yol<\/h2>\n

      Reddin AUTH LOGIN<\/code>, AUTH PLAIN<\/code>, XOAUTH2<\/code> veya sa\u011flay\u0131c\u0131 API ak\u0131\u015f\u0131nda m\u0131 olu\u015ftu\u011funu belirleyin. SMTP zaman\u0131n\u0131 tenant g\u00fcvenlik loglar\u0131, OAuth izni, posta kutusu lisans\u0131 ve g\u00f6nderen yetkileriyle kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n

      Hesap sorumlusunu, yenileme veya yeniden ba\u011flama yolunu, izinli alias\u2019lar\u0131, ba\u015far\u0131l\u0131 ileti kimli\u011fini ve ayr\u0131nt\u0131l\u0131 debug\u2019\u0131n kapat\u0131ld\u0131\u011f\u0131 tarihi kaydedin. Tan\u0131 s\u0131ras\u0131nda a\u00e7\u0131\u011fa \u00e7\u0131kan eri\u015fim bilgilerini yenileyin.<\/p>\n

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

      Parola ve token\u2019lar\u0131 log, ekran g\u00f6r\u00fcnt\u00fcs\u00fc, destek kayd\u0131 veya d\u0131\u015fa aktar\u0131ma koymay\u0131n. Tekrar tekrar parola denemek hesab\u0131 kilitleyebilir; MFA\u2019y\u0131 zay\u0131flatmak veya eski kimlik do\u011frulamay\u0131 kurum genelinde a\u00e7mak daha b\u00fcy\u00fck g\u00fcvenlik riski yarat\u0131r.<\/p>\n

      Posta kutusuyla alias\u2019\u0131 kar\u0131\u015ft\u0131rmay\u0131n ve her 535 yan\u0131t\u0131n\u0131 ayn\u0131 sa\u011flay\u0131c\u0131 politikas\u0131 sanmay\u0131n. Kontroll\u00fc ak\u0131\u015f ya da kar\u015f\u0131la\u015ft\u0131rma testi bozulursa daha \u00f6nce \u00e7al\u0131\u015fan 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, desteklenen WordPress g\u00f6nderen ayarlar\u0131n\u0131, kontroll\u00fc test sonucunu, loglar\u0131, yeniden deneme bilgisini ve g\u00f6nderen uyumunu tek ak\u0131\u015fta tutar. Se\u00e7ili sa\u011flay\u0131c\u0131 yolunu do\u011frulamak ve maskelenmi\u015f 535 yan\u0131t\u0131n\u0131 ilgili zamanla birlikte incelemek i\u00e7in kullan\u0131n.<\/p>\n

      Eri\u015fim bilgilerini yaln\u0131z korumal\u0131 ayarlara girin; log ve ekran g\u00f6r\u00fcnt\u00fclerinde g\u00f6stermeyin. Sa\u011flay\u0131c\u0131n\u0131n onaylad\u0131\u011f\u0131 kimli\u011fi ve y\u00f6ntemi yap\u0131land\u0131r\u0131n, From adresini bu hesab\u0131n yetkileriyle e\u015fle\u015ftirin ve WordPress olay\u0131n\u0131 sa\u011flay\u0131c\u0131n\u0131n g\u00fcvenlik ya da ileti kayd\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n

      SMTP Y\u00f6neticisi tenant g\u00fcvenlik politikas\u0131n\u0131, posta kutusu lisans\u0131n\u0131, DNS\u2019i, sa\u011flay\u0131c\u0131 itibar\u0131n\u0131 veya al\u0131c\u0131n\u0131n filtre karar\u0131n\u0131 de\u011fi\u015ftiremez. Oturum a\u00e7ma ba\u015far\u0131l\u0131 olduktan sonra ayn\u0131 ger\u00e7ek WordPress olay\u0131n\u0131 yeniden tetikleyin; sa\u011flay\u0131c\u0131 kabul\u00fcyle al\u0131c\u0131 sonucunu ayr\u0131 do\u011frulay\u0131n. Sorumluyu, y\u00f6ntemi, politika de\u011fi\u015fikli\u011fini, ileti kimli\u011fini ve yenileme yolunu belgeleyin.<\/p>\n

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

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