{"id":1148,"date":"2026-03-13T15:25:13","date_gmt":"2026-03-13T12:25:13","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1148"},"modified":"2026-09-12T17:14:03","modified_gmt":"2026-09-12T14:14:03","slug":"wordpress-smtp-ayarlari","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-smtp-ayarlari\/","title":{"rendered":"WordPress SMTP Ayarlar\u0131: Sunucu, Port ve Kurulum Rehberi"},"content":{"rendered":"

WordPress kutudan \u00e7\u0131kt\u0131\u011f\u0131 haliyle e-posta g\u00f6nderemez. Daha do\u011frusu g\u00f6ndermeyi dener, ama denemesi \u00e7o\u011fu sunucuda ya sessizce ba\u015far\u0131s\u0131z olur ya da mesaj spam klas\u00f6r\u00fcne d\u00fc\u015fer. WordPress SMTP ayarlar\u0131<\/strong> bu zincirin son halkas\u0131n\u0131 de\u011fi\u015ftirir: mesaj art\u0131k sunucunun yerel g\u00f6nderim yaz\u0131l\u0131m\u0131ndan de\u011fil, kimli\u011fi do\u011frulanm\u0131\u015f ger\u00e7ek bir posta sunucusundan \u00e7\u0131kar.<\/p>\n

Bu rehberde \u00f6nce sorunun nereden \u00e7\u0131kt\u0131\u011f\u0131n\u0131, sonra sa\u011flay\u0131c\u0131 baz\u0131nda ger\u00e7ek sunucu ve port de\u011ferlerini, ard\u0131ndan ayarlar\u0131n do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kan\u0131tlayan bir do\u011frulama y\u00f6ntemini bulacaks\u0131n\u0131z.<\/p>\n

\n\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. WordPress mail’i neden gitmez<\/a><\/li>\n
  2. WordPress SMTP ayarlar\u0131 i\u00e7in sunucu ve port tablosu<\/a><\/li>\n
  3. WordPress SMTP ayarlar\u0131n\u0131 girmeden \u00f6nce<\/a><\/li>\n
  4. WordPress SMTP ayarlar\u0131 ad\u0131m ad\u0131m<\/a><\/li>\n
  5. Do\u011frulama: ger\u00e7ekten \u00e7al\u0131\u015f\u0131yor mu<\/a><\/li>\n
  6. \u00c7al\u0131\u015fmad\u0131ysa<\/a><\/li>\n
  7. AIOWS SMTP Y\u00f6neticisi<\/a><\/li>\n
  8. S\u0131k sorulanlar<\/a><\/li>\n
  9. Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    WordPress mail’i neden gitmez<\/h2>\n

    WordPress bir e-posta g\u00f6nderece\u011finde wp_mail()<\/code> fonksiyonunu \u00e7a\u011f\u0131r\u0131r. Bu fonksiyon arka planda PHPMailer k\u00fct\u00fcphanesini kullan\u0131r ve PHPMailer da varsay\u0131lan olarak PHP’nin mail()<\/code> fonksiyonuna teslim eder. mail()<\/code> ise mesaj\u0131 sunucudaki yerel g\u00f6nderim yaz\u0131l\u0131m\u0131na b\u0131rak\u0131r.<\/p>\n

    Bu zincirde iki k\u0131r\u0131lma noktas\u0131 var.<\/p>\n

    Birincisi:<\/strong> payla\u015f\u0131ml\u0131 bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131lar\u0131n\u0131n \u00e7o\u011fu mail()<\/code> fonksiyonunu kapat\u0131r ya da giden 25 numaral\u0131 portu engeller. Spam g\u00f6nderimini \u00f6nlemek i\u00e7in yap\u0131lan bu k\u0131s\u0131tlama, me\u015fru site e-postalar\u0131n\u0131 da durdurur. Bu durumda WordPress “g\u00f6nderildi” der, hi\u00e7bir \u015fey gitmez.<\/p>\n

    \u0130kincisi, daha sinsi olan\u0131:<\/strong> mail()<\/code> \u00e7al\u0131\u015ft\u0131\u011f\u0131nda bile mesaj kimlik do\u011frulamas\u0131 olmadan g\u00f6nderilir. Al\u0131c\u0131 sunucu, mesaj\u0131n alan ad\u0131n\u0131z ad\u0131na g\u00f6nderilmeye yetkili oldu\u011funu do\u011frulayamaz. SPF ve DKIM kay\u0131tlar\u0131 e\u015fle\u015fmez, Return-Path adresi tutmaz, ve mesaj ya spam klas\u00f6r\u00fcne d\u00fc\u015fer ya da tamamen reddedilir.<\/p>\n

    WordPress SMTP ayarlar\u0131 bu son ad\u0131m\u0131 de\u011fi\u015ftirir. PHPMailer art\u0131k yerel g\u00f6nderim yaz\u0131l\u0131m\u0131na teslim etmez; ger\u00e7ek bir posta sunucusuna kimlik bilgileriyle ba\u011flan\u0131r ve mesaj\u0131 oradan g\u00f6nderir. Mesaj art\u0131k kimli\u011fi do\u011frulanm\u0131\u015f bir kaynaktan \u00e7\u0131kar.<\/p>\n

    WordPress SMTP ayarlar\u0131 i\u00e7in sunucu ve port tablosu<\/h2>\n

    WordPress SMTP ayarlar\u0131 d\u00f6rt de\u011fer ister: sunucu ad\u0131, port, \u015fifreleme t\u00fcr\u00fc ve kimlik do\u011frulama y\u00f6ntemi. Bu d\u00f6rd\u00fc birbirine ba\u011fl\u0131d\u0131r \u2014 port ile \u015fifrelemeyi yanl\u0131\u015f e\u015fle\u015ftirmek en s\u0131k yap\u0131lan hatad\u0131r.<\/p>\n

    \n\n\n\n\n\n\n\n\n\n\n\n
    Sa\u011flay\u0131c\u0131<\/th>\nSunucu<\/th>\nPort<\/th>\n\u015eifreleme<\/th>\nKimlik do\u011frulama<\/th>\n<\/tr>\n<\/thead>\n
    Gmail (ki\u015fisel)<\/td>\nsmtp.gmail.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nUygulama \u015fifresi<\/td>\n<\/tr>\n
    Gmail (ki\u015fisel)<\/td>\nsmtp.gmail.com<\/code><\/td>\n465<\/td>\nSSL\/TLS<\/td>\nUygulama \u015fifresi<\/td>\n<\/tr>\n
    Google Workspace<\/td>\nsmtp.gmail.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nUygulama \u015fifresi veya OAuth<\/td>\n<\/tr>\n
    Microsoft 365<\/td>\nsmtp.office365.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nOAuth 2.0 \u00f6nerilir, SMTP AUTH a\u00e7\u0131k olmal\u0131<\/td>\n<\/tr>\n
    Yandex<\/td>\nsmtp.yandex.com<\/code><\/td>\n465<\/td>\nSSL\/TLS<\/td>\nUygulama \u015fifresi (zorunlu), kullan\u0131c\u0131 ad\u0131 @ \u00f6ncesi<\/td>\n<\/tr>\n
    Payla\u015f\u0131ml\u0131 hosting<\/td>\nmail.alanadiniz.com<\/code><\/td>\n465<\/td>\nSSL\/TLS<\/td>\nPosta kutusu kimlik bilgileri<\/td>\n<\/tr>\n
    Payla\u015f\u0131ml\u0131 hosting<\/td>\nmail.alanadiniz.com<\/code><\/td>\n587<\/td>\nSTARTTLS<\/td>\nPosta kutusu kimlik bilgileri<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Payla\u015f\u0131ml\u0131 hosting sat\u0131r\u0131 hakk\u0131nda:<\/strong> Natro, Turhost ve Bluehost gibi cPanel tabanl\u0131 sa\u011flay\u0131c\u0131larda mail.alanadiniz.com<\/code> kal\u0131b\u0131 ge\u00e7erlidir. Kesin de\u011ferleri cPanel’de E-posta Hesaplar\u0131 \u2192 Ba\u011flan \u2192 Posta \u0130stemcisini Yap\u0131land\u0131r<\/strong> ekran\u0131nda g\u00f6rebilirsiniz; oradaki de\u011ferler sizin sunucunuz i\u00e7in do\u011frudur. GoDaddy payla\u015f\u0131ml\u0131 planlar\u0131nda bu kal\u0131p her zaman \u00e7al\u0131\u015fmaz, kendi r\u00f6le sunucusunu kulland\u0131r\u0131r.<\/p>\n

    Port 25 tabloda neden yok:<\/strong> 25 numaral\u0131 port sunucular aras\u0131 teslimat i\u00e7in kullan\u0131l\u0131r ve bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131lar\u0131n\u0131n \u00e7o\u011fu giden 25 trafi\u011fini engeller. Site e-postas\u0131 g\u00f6ndermek i\u00e7in 587 veya 465 kullan\u0131l\u0131r.<\/p>\n

    Microsoft 365’te 465 yok.<\/strong> Microsoft istemci g\u00f6nderimi i\u00e7in yaln\u0131zca 587 ve STARTTLS kabul eder. Cihaz\u0131n\u0131z 465 ile ba\u011flanmaya \u00e7al\u0131\u015f\u0131yorsa hi\u00e7 ba\u011flanamaz.<\/p>\n

    Microsoft 365’te kimlik do\u011frulama de\u011fi\u015fiyor.<\/strong> Microsoft, SMTP g\u00f6nderimi i\u00e7in uygulama \u015fifresiyle ba\u011flanmay\u0131 kademeli olarak kald\u0131r\u0131yor; yerine OAuth 2.0 geliyor. Kapat\u0131ld\u0131\u011f\u0131nda gelen hata \u015fudur:<\/p>\n

    550 5.7.30 Basic authentication is not supported for Client Submission<\/code><\/pre>\n
    Bu hatay\u0131 al\u0131yorsan\u0131z \u015fifre yanl\u0131\u015f de\u011fil, y\u00f6ntem art\u0131k kabul edilmiyor. G\u00fcncel takvimi Microsoft’un kendi duyurusundan kontrol edin; tarih birka\u00e7 kez ertelendi.<\/p>\n
    Yandex’te kullan\u0131c\u0131 ad\u0131 farkl\u0131.<\/strong> Di\u011fer sa\u011flay\u0131c\u0131larda tam e-posta adresi yaz\u0131l\u0131r, Yandex’te yaln\u0131zca @ i\u015faretinden \u00f6nceki k\u0131s\u0131m. ornek@yandex.com<\/code> i\u00e7in kullan\u0131c\u0131 ad\u0131 ornek<\/code> olur.<\/p>\n
    Yandex ayr\u0131ca iki \u00f6n ko\u015ful ister: webmail ayarlar\u0131nda E-posta istemcileri<\/strong> b\u00f6l\u00fcm\u00fcnden hem IMAP eri\u015fimini hem “Uygulama \u015fifreleri ve OAuth belirte\u00e7leri” se\u00e7ene\u011fini a\u00e7man\u0131z gerekir. Uygulama \u015fifresi id.yandex.com\/security<\/code> adresinden \u00fcretilir, bir kez g\u00f6sterilir ve etkinle\u015fmesi birka\u00e7 saat alabilir.<\/p>\n
    Rusya d\u0131\u015f\u0131ndan ba\u011flan\u0131yorsan\u0131z smtp.yandex.com<\/code> yerine smtp.ya.ru<\/code> daha g\u00fcvenilir \u00e7al\u0131\u015f\u0131r.<\/p>\n
    587 mi 465 mi:<\/strong> ikisi de do\u011frudur, fark\u0131 \u015fifrelemenin ne zaman ba\u015flad\u0131\u011f\u0131d\u0131r. 587 d\u00fcz ba\u011flant\u0131 a\u00e7ar ve STARTTLS komutuyla \u015fifrelemeye ge\u00e7er. 465 ba\u011flant\u0131n\u0131n ilk bayt\u0131ndan itibaren \u015fifrelidir. Sa\u011flay\u0131c\u0131n\u0131z hangisini belgeliyorsa onu kullan\u0131n; ikisi de destekleniyorsa 587 daha yayg\u0131nd\u0131r.<\/p>\n
    \n\"WordPress
    \u00c7apraz e\u015fle\u015fme ba\u011flant\u0131y\u0131 kopar\u0131r \u2014 en s\u0131k yap\u0131lan hata budur.<\/figcaption><\/figure>\n
    WordPress SMTP ayarlar\u0131n\u0131 girmeden \u00f6nce<\/h2>\n
    Mevcut ayarlar\u0131 not edin.<\/strong> Halihaz\u0131rda bir SMTP eklentisi kuruluysa, sunucu, port ve g\u00f6nderen adresi alanlar\u0131n\u0131n ekran g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc al\u0131n. Yeni ayar \u00e7al\u0131\u015fmazsa geri d\u00f6nebilirsiniz.<\/p>\n
    Uygulama \u015fifresi olu\u015fturun.<\/strong> Gmail, Microsoft 365 ve Yandex hesap \u015fifrenizle SMTP ba\u011flant\u0131s\u0131 kabul etmez. Ayr\u0131 bir uygulama \u015fifresi \u00fcretmeniz gerekir ve bunun i\u00e7in hesapta iki ad\u0131ml\u0131 do\u011frulaman\u0131n a\u00e7\u0131k olmas\u0131 \u015fartt\u0131r.<\/p>\n
    Gmail’de: Google Hesab\u0131 \u2192 G\u00fcvenlik \u2192 \u0130ki Ad\u0131ml\u0131 Do\u011frulama \u2192 Uygulama \u015fifreleri.<\/p>\n
    \n\"WordPress
    \u015eifre bir kez g\u00f6sterilir; kaydetmeden pencereyi kapatmay\u0131n.<\/figcaption><\/figure>\n
    Yandex’te: Hesap ayarlar\u0131 \u2192 G\u00fcvenlik \u2192 Uygulama \u015fifreleri, ayr\u0131ca posta ayarlar\u0131nda “Di\u011fer uygulamalardan eri\u015fim” se\u00e7ene\u011finin a\u00e7\u0131k olmas\u0131 gerekir.<\/p>\n
    G\u00f6nderen adresini belirleyin.<\/strong> Bu adres, kimlik do\u011frulamas\u0131 yapt\u0131\u011f\u0131n\u0131z posta kutusuyla ayn\u0131 alan ad\u0131nda olmal\u0131d\u0131r. bilgi@alanadiniz.com<\/code> ile ba\u011flan\u0131p noreply@baskaalanadi.com<\/code> adresinden g\u00f6ndermeye \u00e7al\u0131\u015fmak reddedilme sebebidir.<\/p>\n
    WordPress SMTP ayarlar\u0131 ad\u0131m ad\u0131m<\/h2>\n
    Hangi SMTP eklentisini kullan\u0131rsan\u0131z kullan\u0131n, alanlar ayn\u0131d\u0131r.<\/p>\n
    Sunucu (Host):<\/strong> tablodaki de\u011fer, \u00f6rne\u011fin smtp.gmail.com<\/code>.<\/p>\n
    Port:<\/strong> 587 veya 465.<\/p>\n
    \u015eifreleme:<\/strong> 587 i\u00e7in STARTTLS, 465 i\u00e7in SSL\/TLS. Bu e\u015fle\u015fmeyi yanl\u0131\u015f yapmak “ba\u011flant\u0131 zaman a\u015f\u0131m\u0131” ya da “sertifika hatas\u0131” olarak geri d\u00f6ner.<\/p>\n
    Kimlik do\u011frulama:<\/strong> a\u00e7\u0131k.<\/p>\n
    Kullan\u0131c\u0131 ad\u0131:<\/strong> genellikle tam e-posta adresiniz. Baz\u0131 hosting sa\u011flay\u0131c\u0131lar\u0131 farkl\u0131 bir kullan\u0131c\u0131 ad\u0131 kal\u0131b\u0131 kullan\u0131r; cPanel’deki yap\u0131land\u0131rma ekran\u0131 do\u011frusunu g\u00f6sterir.<\/p>\n
    \u015eifre:<\/strong> uygulama \u015fifresi. Hesap \u015fifresi de\u011fil.<\/p>\n
    G\u00f6nderen adresi (From):<\/strong> kimlik do\u011frulad\u0131\u011f\u0131n\u0131z posta kutusunun adresi.<\/p>\n
    G\u00f6nderen ad\u0131 (From Name):<\/strong> site ad\u0131n\u0131z. Ziyaret\u00e7inin gelen kutusunda g\u00f6rece\u011fi isim budur.<\/p>\n
    Kaydedin, sonra do\u011frulamaya ge\u00e7in. Kaydetmek \u00e7al\u0131\u015ft\u0131\u011f\u0131 anlam\u0131na gelmez.<\/p>\n
    Do\u011frulama: ger\u00e7ekten \u00e7al\u0131\u015f\u0131yor mu<\/h2>\n
    Test e-postas\u0131 g\u00f6ndermek yeterli de\u011fil. D\u00f6rt kontrol\u00fcn d\u00f6rd\u00fc de ge\u00e7meli.<\/p>\n
    \n\n\n\n\n\n\n\n\n
    Kontrol<\/th>\nNas\u0131l yap\u0131l\u0131r<\/th>\nBeklenen<\/th>\n<\/tr>\n<\/thead>\n
    Test e-postas\u0131 gidiyor mu<\/td>\nEklentinin test arac\u0131ndan kendinize g\u00f6nderin<\/td>\nHata mesaj\u0131 yok<\/td>\n<\/tr>\n
    Gelen kutusuna m\u0131 d\u00fc\u015f\u00fcyor<\/td>\nSpam klas\u00f6r\u00fcn\u00fc de kontrol edin<\/td>\nGelen kutusu<\/td>\n<\/tr>\n
    Ger\u00e7ekten SMTP’den mi \u00e7\u0131k\u0131yor<\/td>\nGelen mesajda kayna\u011f\u0131 g\u00f6r\u00fcnt\u00fcleyin, Received:<\/code> sat\u0131rlar\u0131na bak\u0131n<\/td>\nSunucu ad\u0131n\u0131z g\u00f6r\u00fcnmeli<\/td>\n<\/tr>\n
    Yanl\u0131\u015f \u015fifre reddediliyor mu<\/strong><\/td>\n\u015eifre alan\u0131na kasten yanl\u0131\u015f bir de\u011fer girin, tekrar test edin<\/td>\nTest BA\u015eARISIZ olmal\u0131<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    D\u00f6rd\u00fcnc\u00fc kontrol en \u00f6nemlisi ve en \u00e7ok atlanan. Yanl\u0131\u015f \u015fifreyle test h\u00e2l\u00e2 “ba\u015far\u0131l\u0131” diyorsa, WordPress SMTP ayarlar\u0131 devreye girmiyor demektir \u2014 eklenti sessizce eski mail()<\/code> yoluna d\u00fc\u015fm\u00fc\u015ft\u00fcr. Kontrolden sonra do\u011fru \u015fifreyi geri girmeyi unutmay\u0131n.<\/p>\n
    Sadece test arac\u0131na g\u00fcvenmeyin. Ger\u00e7ek bir olay\u0131 da deneyin: bir ileti\u015fim formu g\u00f6nderin ya da parola s\u0131f\u0131rlama isteyin. Test e-postas\u0131 \u00e7al\u0131\u015f\u0131p form e-postalar\u0131n\u0131n \u00e7al\u0131\u015fmamas\u0131<\/a> ayr\u0131 ve yayg\u0131n bir sorundur; sebebi genellikle formun ziyaret\u00e7i adresini g\u00f6nderen alan\u0131na koymas\u0131d\u0131r.<\/p>\n
    \u00c7al\u0131\u015fmad\u0131ysa<\/h2>\n
    WordPress SMTP ayarlar\u0131 kaydedildi\u011fi halde sonu\u00e7 de\u011fi\u015fmediyse, s\u0131rayla bunlara bak\u0131n.<\/p>\n
    Ba\u011flant\u0131 zaman a\u015f\u0131m\u0131 veya reddedildi.<\/strong> Bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131n\u0131z giden portu engelliyor olabilir. 587 \u00e7al\u0131\u015fm\u0131yorsa 465’i deneyin. \u0130kisi de \u00e7al\u0131\u015fm\u0131yorsa sa\u011flay\u0131c\u0131n\u0131za giden SMTP trafi\u011finin a\u00e7\u0131k olup olmad\u0131\u011f\u0131n\u0131 sorun. Ayr\u0131nt\u0131l\u0131 te\u015fhis i\u00e7in SMTP ba\u011flant\u0131 hatas\u0131 rehberine<\/a> bak\u0131n.<\/p>\n
    535 kimlik do\u011frulama hatas\u0131.<\/strong> \u015eifre yanl\u0131\u015f ya da hesap \u015fifresi kullan\u0131lm\u0131\u015f. Uygulama \u015fifresi \u00fcretin. Microsoft 365’te ayr\u0131ca SMTP AUTH ayar\u0131n\u0131n posta kutusu i\u00e7in a\u00e7\u0131k olmas\u0131 gerekir; kurumsal kirac\u0131larda varsay\u0131lan olarak kapal\u0131d\u0131r.<\/p>\n
    Sertifika hatas\u0131.<\/strong> Port ve \u015fifreleme e\u015fle\u015fmesi yanl\u0131\u015f. 465’e STARTTLS ya da 587’ye SSL\/TLS se\u00e7mi\u015f olabilirsiniz. Do\u011frulamay\u0131 kapatan se\u00e7ene\u011fi kullanmay\u0131n; sorunu gizler, \u00e7\u00f6zmez.<\/p>\n
    Mesaj gidiyor ama spam’e d\u00fc\u015f\u00fcyor.<\/strong> SMTP tek ba\u015f\u0131na yeterli de\u011fil. Alan ad\u0131n\u0131z i\u00e7in e-postalar\u0131n\u0131z\u0131n spam’e d\u00fc\u015fmesini \u00f6nleyen DNS kay\u0131tlar\u0131n\u0131n<\/a> tan\u0131ml\u0131 olmas\u0131 gerekir.<\/p>\n
    \n
    AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n
    AIOWS SMTP Y\u00f6neticisi<\/h2>\n
    Yukar\u0131daki de\u011ferleri elle girmek zor de\u011fil, ama Gmail ve Microsoft 365’te OAuth kullanmak istedi\u011finizde i\u015f b\u00fcy\u00fcr. Google Cloud Console’da proje olu\u015fturmak, izin ekran\u0131n\u0131 yap\u0131land\u0131rmak, kimlik bilgisi \u00fcretmek, y\u00f6nlendirme URI’si tan\u0131mlamak ve yetkilendirme ak\u0131\u015f\u0131n\u0131 tamamlamak gerekir. Onbe\u015f ad\u0131m, ve her m\u00fc\u015fteride ba\u015ftan.<\/p>\n
    AIOWS SMTP Y\u00f6neticisi’ndeki EasyConnect bu ak\u0131\u015f\u0131 tek ba\u011flant\u0131ya indirir: Google veya Microsoft hesab\u0131n\u0131z\u0131 se\u00e7ersiniz, izni onaylars\u0131n\u0131z, ba\u011flant\u0131 kurulur. Konsol yap\u0131land\u0131rmas\u0131, anahtar kopyalama ve URI ayar\u0131 gerekmez.<\/p>\n
    \n\"AIOWS
    Sa\u011flay\u0131c\u0131 kartlar\u0131 sunucu, port ve \u015fifrelemeyi birlikte g\u00f6sterir; se\u00e7ti\u011finizde alanlar otomatik dolar.<\/figcaption><\/figure>\n
    Mod\u00fcl on \u00fc\u00e7 sa\u011flay\u0131c\u0131 \u00f6n ayar\u0131 ta\u015f\u0131r: Gmail, Outlook ve Office 365, Yahoo, Zoho, SendGrid, Mailgun, Amazon SES, Brevo, SparkPost, Postmark, Yandex, payla\u015f\u0131ml\u0131 hosting ve elle giri\u015f i\u00e7in \u00d6zel SMTP Sunucusu. Kart se\u00e7ildi\u011finde sunucu, port ve \u015fifreleme birlikte gelir, yani bu makaledeki e\u015fle\u015fme hatas\u0131 ba\u015ftan \u00f6nlenir.<\/p>\n
    Payla\u015f\u0131ml\u0131 hosting \u00f6n ayar\u0131 sunucu ad\u0131n\u0131 sitenizin alan ad\u0131ndan t\u00fcretir \u2014 mail.alanadiniz.com<\/code> bi\u00e7iminde haz\u0131r gelir. Yandex kart\u0131 ise iki \u00f6n ko\u015fulu kendi \u00fczerinde yazar: kullan\u0131c\u0131 ad\u0131 @ \u00f6ncesi k\u0131s\u0131md\u0131r ve uygulama \u015fifresi zorunludur.<\/p>\n
    Bir davran\u0131\u015f\u0131 bilin:<\/strong> EasyConnect etkinken elle girdi\u011finiz SMTP ayarlar\u0131 korunur ama kullan\u0131lmaz. Elle ayar girip sonu\u00e7 alam\u0131yorsan\u0131z sebebi bu olabilir; mod\u00fcl aray\u00fcz\u00fc de bunu ayr\u0131ca belirtir.<\/p>\n
    Test arac\u0131 yap\u0131land\u0131rman\u0131n her par\u00e7as\u0131n\u0131 ayr\u0131 ayr\u0131 do\u011frular ve ba\u015far\u0131s\u0131z olursa hatan\u0131n hangi a\u015famada olu\u015ftu\u011funu s\u00f6yler \u2014 DNS \u00e7\u00f6z\u00fcmlemesi, ba\u011flant\u0131, TLS el s\u0131k\u0131\u015fmas\u0131 ya da kimlik do\u011frulama. Sunucunun kendi yan\u0131t sat\u0131r\u0131 da g\u00f6r\u00fcn\u00fcr; kimlik bilgileri hi\u00e7bir zaman g\u00f6sterilmez.<\/p>\n
    S\u0131n\u0131rlar\u0131 a\u00e7\u0131k olsun:<\/strong> mod\u00fcl, bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131n\u0131z\u0131n engelledi\u011fi bir portu a\u00e7amaz, alan ad\u0131n\u0131z\u0131n SPF veya DKIM kay\u0131tlar\u0131n\u0131 sizin yerinize DNS’e yazamaz ve Microsoft 365 kirac\u0131n\u0131zda kapal\u0131 olan SMTP AUTH ayar\u0131n\u0131 de\u011fi\u015ftiremez. Bu \u00fc\u00e7\u00fc sizin ya da sa\u011flay\u0131c\u0131n\u0131z\u0131n m\u00fcdahalesini gerektirir.<\/p>\n
    AIOWS SMTP Y\u00f6neticisi’ni inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n
    S\u0131k sorulanlar<\/h2>\n
    WordPress SMTP ayarlar\u0131 yapmak zorunda m\u0131y\u0131m?<\/strong> WordPress’in kendi g\u00f6nderim yolu kimlik do\u011frulamas\u0131 yapmad\u0131\u011f\u0131 i\u00e7in mesajlar\u0131n\u0131z ya gitmez ya spam’e d\u00fc\u015fer. SMTP, e-postalar\u0131n g\u00fcvenilir bi\u00e7imde teslim edilmesinin standart yoludur.<\/p>\n
    Hesap \u015fifremi kullanabilir miyim?<\/strong> Gmail, Microsoft 365 ve Yandex kabul etmez. Uygulama \u015fifresi \u00fcretmeniz gerekir ve bunun i\u00e7in iki ad\u0131ml\u0131 do\u011frulaman\u0131n a\u00e7\u0131k olmas\u0131 \u015fartt\u0131r.<\/p>\n
    587 mi 465 mi se\u00e7meliyim?<\/strong> Sa\u011flay\u0131c\u0131n\u0131z hangisini belgeliyorsa onu. \u0130kisi de destekleniyorsa 587 daha yayg\u0131nd\u0131r. \u00d6nemli olan port ile \u015fifreleme t\u00fcr\u00fcn\u00fc do\u011fru e\u015fle\u015ftirmek.<\/p>\n
    Gmail ile g\u00fcnde ka\u00e7 e-posta g\u00f6nderebilirim?<\/strong> Ki\u015fisel Gmail hesaplar\u0131n\u0131n g\u00fcnl\u00fck g\u00f6nderim s\u0131n\u0131r\u0131 vard\u0131r. Yo\u011fun g\u00f6nderim yapan siteler i\u00e7in i\u015flemsel e-posta sa\u011flay\u0131c\u0131lar\u0131 daha uygundur.<\/p>\n
    SMTP ayarlad\u0131m ama h\u00e2l\u00e2 spam’e d\u00fc\u015f\u00fcyor.<\/strong> SMTP teslimat\u0131 sa\u011flar, itibar\u0131 de\u011fil. Alan ad\u0131n\u0131z i\u00e7in SPF ve DKIM kay\u0131tlar\u0131n\u0131 tan\u0131mlaman\u0131z gerekir.<\/p>\n
    Test e-postas\u0131 gidiyor, form e-postalar\u0131 gitmiyor.<\/strong> Form eklentisi genellikle ziyaret\u00e7inin adresini g\u00f6nderen alan\u0131na koyar ve bu kimlik do\u011frulamas\u0131yla \u00e7ak\u0131\u015f\u0131r. G\u00f6nderen adresi sitenizin alan ad\u0131nda olmal\u0131, ziyaret\u00e7inin adresi Reply-To alan\u0131na yaz\u0131lmal\u0131d\u0131r.<\/p>\n
    Kaynaklar<\/h2>\n