{"id":1852,"date":"2026-07-26T10:40:16","date_gmt":"2026-07-26T07:40:16","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1852"},"modified":"2026-08-03T10:32:22","modified_gmt":"2026-08-03T10:32:22","slug":"wordpress-e-posta-teslimati-icin-spf-nasil-ayarlanir","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-e-posta-teslimati-icin-spf-nasil-ayarlanir\/","title":{"rendered":"WordPress E-posta G\u00f6nderimi i\u00e7in SPF Ayarlama"},"content":{"rendered":"

Bir \u015firket WordPress i\u00e7in yeni bir i\u015flem e-postas\u0131 sa\u011flay\u0131c\u0131s\u0131 eklerken ikinci SPF kayd\u0131n\u0131 yay\u0131ml\u0131yor. Baz\u0131 al\u0131c\u0131lar art\u0131k kal\u0131c\u0131 SPF hatas\u0131 veriyor. Ekip ise yaln\u0131z g\u00f6r\u00fcnen From<\/code> adresine bak\u0131yor ve sa\u011flay\u0131c\u0131n\u0131n farkl\u0131 Return-Path domainini g\u00f6zden ka\u00e7\u0131r\u0131yor.<\/p>\n

Do\u011fru kurulum SMTP envelope kimli\u011fiyle ba\u015flar. Bu domain ad\u0131na e-posta g\u00f6nderen b\u00fct\u00fcn me\u015fru hizmetleri listeleyin, gerekli kaynaklar\u0131 tek politikada birle\u015ftirin ve sonucu gelen iletinin ba\u015fl\u0131klar\u0131nda do\u011frulay\u0131n.<\/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

    Sender Policy Framework (SPF), belirli bir SMTP MAIL FROM<\/code> domaini ad\u0131na hangi sistemlerin e-posta g\u00f6nderebilece\u011fini belirten DNS politikas\u0131d\u0131r. Al\u0131c\u0131 sunucu ba\u011flant\u0131 kuran IP’yi envelope domainindeki SPF kayd\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131r; kullan\u0131labilir MAIL FROM kimli\u011fi yoksa HELO domainini de\u011ferlendirebilir.<\/p>\n

    SPF iletiyi imzalamaz ve okuyucunun g\u00f6rd\u00fc\u011f\u00fc From<\/code> adresini tek ba\u015f\u0131na do\u011frulamaz. DMARC, SPF sonucunu ancak do\u011frulanan envelope domaini g\u00f6r\u00fcnen From domainiyle hizal\u0131ysa kullanabilir.<\/p>\n

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

    Ana domainde Microsoft 365 i\u00e7in mevcut bir SPF kayd\u0131 bulunuyor. WordPress sa\u011flay\u0131c\u0131s\u0131 eklenirken gerekli include<\/code>, ayr\u0131 bir SPF TXT kayd\u0131 olarak yay\u0131mlan\u0131yor. \u0130ki politika g\u00f6ren al\u0131c\u0131lar permerror<\/code> sonucu d\u00f6nd\u00fcrebiliyor.<\/p>\n

    DNS sorumlusu \u00f6nce sa\u011flay\u0131c\u0131n\u0131n hangi Return-Path domainini kulland\u0131\u011f\u0131n\u0131 do\u011fruluyor. \u015eirket domaini de\u011ferlendiriliyorsa gerekli include mevcut politikaya ekleniyor. Sa\u011flay\u0131c\u0131 kendi domainini kullan\u0131yorsa yaln\u0131z g\u00f6r\u00fcnen From adresi nedeniyle \u015firket kayd\u0131 de\u011fi\u015ftirilmiyor. Karar\u0131 test iletisinin ba\u015fl\u0131klar\u0131 veriyor.<\/p>\n

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

    SPF, al\u0131c\u0131 sunucular\u0131n envelope domaini i\u00e7in yetkili g\u00f6nderim altyap\u0131s\u0131n\u0131 yetkisiz kaynaklardan ay\u0131rmas\u0131na yard\u0131mc\u0131 olur. Eksik politika me\u015fru iletileri etkileyebilir; gere\u011finden geni\u015f politika ise art\u0131k kullan\u0131lmayan sistemlere g\u00f6nderim yetkisi verir.<\/p>\n

    WordPress ayn\u0131 domaini kurumsal posta, destek masas\u0131, e-ticaret sistemi, pazarlama platformu veya relay ile payla\u015fabilir. Son all<\/code> niteleyicisini s\u0131k\u0131la\u015ft\u0131rmadan \u00f6nce ayn\u0131 envelope domainini kullanan b\u00fct\u00fcn kaynaklar bilinmelidir.<\/p>\n

    Kurulu\u015f ilgili DNS’i y\u00f6netiyor ve g\u00f6nderen envanterini g\u00fcncel tutabiliyorsa SPF yap\u0131land\u0131r\u0131n. Return-Path domainini sa\u011flay\u0131c\u0131 y\u00f6netiyorsa onun g\u00fcncel dok\u00fcman\u0131n\u0131 izleyin; g\u00f6r\u00fcnen From domainine ilgisiz kay\u0131t eklemek \u00e7\u00f6z\u00fcm de\u011fildir.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/h2>\n
      \n
    1. Kontroll\u00fc bir WordPress e-postas\u0131 g\u00f6nderin; ger\u00e7ekten de\u011ferlendirilen domaini bulmak i\u00e7in Return-Path<\/code>, Received-SPF<\/code> ve Authentication-Results<\/code> ba\u015fl\u0131klar\u0131n\u0131 inceleyin.<\/li>\n
    2. Bu domain ad\u0131na g\u00f6nderim yapan b\u00fct\u00fcn yetkili hizmetleri, IPv4 ve IPv6 adreslerini, relay’leri ve sa\u011flay\u0131c\u0131 include<\/code> mekanizmalar\u0131n\u0131 listeleyin.<\/li>\n
    3. Yetkili DNS’teki g\u00fcncel TXT kay\u0131tlar\u0131n\u0131 okuyun. v=spf1<\/code> ile ba\u015flayan tek bir SPF politikas\u0131 tutun; ikinci kay\u0131t a\u00e7mak yerine gerekli mekanizmalar\u0131 mevcut kay\u0131tta birle\u015ftirin.<\/li>\n
    4. Eski kaynaklar\u0131 ancak sorumlu ekip art\u0131k kullan\u0131lmad\u0131\u011f\u0131n\u0131 onaylad\u0131ktan sonra \u00e7\u0131kar\u0131n. Son all<\/code> niteleyicisini bilin\u00e7li se\u00e7in.<\/li>\n
    5. Yetkili DNS’i ve birden fazla resolver’\u0131 sorgulay\u0131n, kalan her kaynaktan e-posta g\u00f6nderin. SPF sonucuyla DMARC hizas\u0131n\u0131 ayr\u0131 ayr\u0131 kontrol edin.<\/li>\n<\/ol>\n

      \u0130leri teknik yol<\/h2>\n

      \u0130\u00e7 i\u00e7e include<\/code> ve redirect<\/code> zincirlerini a\u00e7\u0131p DNS sorgusu olu\u015fturan b\u00fct\u00fcn mekanizmalar\u0131 SPF lookup s\u0131n\u0131r\u0131na g\u00f6re say\u0131n. Bo\u015f sonu\u00e7lar\u0131, sa\u011flay\u0131c\u0131n\u0131n y\u00f6netti\u011fi ba\u011f\u0131ml\u0131l\u0131klar\u0131, IPv6 yetkisini, makrolar\u0131 ve alt domainleri inceleyin. K\u0131sa g\u00f6r\u00fcnen kay\u0131t bile \u00fc\u00e7\u00fcnc\u00fc taraflar nedeniyle s\u0131n\u0131r\u0131 a\u015fabilir.<\/p>\n

      Her d\u0131\u015f ba\u011f\u0131ml\u0131l\u0131k i\u00e7in sorumlu ki\u015fiyi, amac\u0131, son inceleme tarihini ve kald\u0131rma ko\u015fulunu kaydedin. Yetkisiz bir kaynaktan negatif test de yap\u0131lmal\u0131d\u0131r; ancak ger\u00e7ek m\u00fc\u015fteri domainini taklit etmeyen kontroll\u00fc bir ortam kullan\u0131n.<\/p>\n

      Sa\u011flay\u0131c\u0131 de\u011fi\u015fikli\u011fi, \u015firket birle\u015fmesi, destek masas\u0131 ge\u00e7i\u015fi veya yeni pazarlama arac\u0131 sonras\u0131nda politikay\u0131 yeniden g\u00f6zden ge\u00e7irin. \u00dc\u00e7\u00fcnc\u00fc taraf, \u015firketin ana TXT kayd\u0131 de\u011fi\u015fmeden kendi include i\u00e7eri\u011fini de\u011fi\u015ftirebilir.<\/p>\n

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

      Ayn\u0131 DNS ad\u0131 i\u00e7in birden fazla SPF politikas\u0131 yay\u0131mlamay\u0131n, belgelenmemi\u015f sa\u011flay\u0131c\u0131 IP aral\u0131\u011f\u0131n\u0131 kopyalamay\u0131n, eski g\u00f6ndericileri yetkili b\u0131rakmay\u0131n ve kullan\u0131m d\u0131\u015f\u0131 ptr<\/code> mekanizmas\u0131n\u0131 eklemeyin. Eksiksiz envanter olmadan do\u011frudan kat\u0131 hata niteleyicisine ge\u00e7mek me\u015fru e-postalar\u0131 engelleyebilir.<\/p>\n

      De\u011fi\u015fiklikten \u00f6nce mevcut DNS de\u011ferini ve sorumlusunu kaydedin; TTL ile yay\u0131lma s\u00fcresini planlay\u0131n. Kullan\u0131lan kaynaklar ba\u015far\u0131s\u0131z olursa, yetkili DNS sunucular\u0131 farkl\u0131 yan\u0131t verirse, lookup s\u0131n\u0131r\u0131 a\u015f\u0131l\u0131rsa veya yanl\u0131\u015f domain de\u011ferlendirilirse \u00f6nceki tek politikaya d\u00f6n\u00fcn ve envanteri d\u00fczeltin.<\/p>\n

      \n

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

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

      AIOWS SMTP Y\u00f6neticisi, SPF haz\u0131rlan\u0131rken WordPress taraf\u0131ndaki SMTP sunucusunu, g\u00f6nderen kimli\u011fini ve kontroll\u00fc testi g\u00f6r\u00fcn\u00fcr tutar. Yap\u0131land\u0131r\u0131lan yoldan g\u00f6nderilen test iletisinin ba\u015fl\u0131klar\u0131 ger\u00e7ek Return-Path de\u011ferini ve al\u0131c\u0131n\u0131n de\u011ferlendirdi\u011fi SPF domainini g\u00f6sterir.<\/p>\n

      Bu ba\u015fl\u0131klar\u0131 sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel dok\u00fcman\u0131yla ve yetkili DNS kayd\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n. Ayn\u0131 g\u00f6nderim yolunu kullanan ger\u00e7ek bir WordPress bildirimiyle testi tekrarlay\u0131n; genel test e-postas\u0131 her form, sipari\u015f veya hesap iletisinin ayn\u0131 ayar\u0131 kulland\u0131\u011f\u0131n\u0131 kan\u0131tlamaz.<\/p>\n

      AIOWS DNS kayd\u0131 yay\u0131mlayamaz veya de\u011fi\u015ftiremez, sa\u011flay\u0131c\u0131n\u0131n SPF include kayd\u0131n\u0131 y\u00f6netemez ve yetkisiz kayna\u011fa g\u00f6nderim izni veremez. Domainler farkl\u0131ysa SPF pass sonucu DMARC hizas\u0131 da olu\u015fturmaz. DNS y\u00f6netimi, g\u00f6nderen envanteri ve politika incelemesi mod\u00fcl\u00fcn d\u0131\u015f\u0131ndad\u0131r.<\/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