{"id":1855,"date":"2026-07-26T14:50:52","date_gmt":"2026-07-26T11:50:52","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1855"},"modified":"2026-08-03T10:32:22","modified_gmt":"2026-08-03T10:32:22","slug":"wordpress-e-postalari-icin-dkim-nasil-ayarlanir","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-e-postalari-icin-dkim-nasil-ayarlanir\/","title":{"rendered":"WordPress E-postalar\u0131 i\u00e7in DKIM Ayarlama"},"content":{"rendered":"

Yeni WordPress posta sa\u011flay\u0131c\u0131s\u0131nda DKIM a\u00e7\u0131k g\u00f6r\u00fcn\u00fcyor, ancak gelen iletilerin ba\u015fl\u0131\u011f\u0131nda dkim=fail<\/code> yaz\u0131yor. DNS’te eski selector h\u00e2l\u00e2 duruyor, yeni a\u00e7\u0131k anahtar eksik kopyalanm\u0131\u015f ve ger\u00e7ek imzada hangi domainin kullan\u0131ld\u0131\u011f\u0131 kontrol edilmemi\u015f.<\/p>\n

DKIM’in \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 sa\u011flay\u0131c\u0131 panelindeki anahtar de\u011fil, teslim edilen ileti kan\u0131tlar. A\u00e7\u0131k selector kayd\u0131n\u0131 eksiksiz yay\u0131mlay\u0131n, \u00f6zel anahtar\u0131 imzalayan hizmette tutun ve kurulumu tamamlamadan \u00f6nce imza domainiyle selector de\u011ferini ba\u015fl\u0131klardan okuyun.<\/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

    DomainKeys Identified Mail (DKIM), se\u00e7ilen e-posta ba\u015fl\u0131klar\u0131yla ileti g\u00f6vdesine kriptografik imza ekler. \u00d6zel anahtar g\u00f6nderim hizmetinde kal\u0131r. Al\u0131c\u0131, DKIM-Signature<\/code> i\u00e7indeki imza domainini (d=<\/code>) ve selector de\u011ferini (s=<\/code>) okuyup a\u00e7\u0131k anahtar\u0131 DNS’ten al\u0131r.<\/p>\n

    Ge\u00e7erli imza, imzalanan i\u00e7eri\u011fin aktar\u0131m s\u0131ras\u0131nda de\u011fi\u015fmedi\u011fini ve g\u00f6nderenin e\u015fle\u015fen \u00f6zel anahtara sahip oldu\u011funu g\u00f6sterir. Ancak DMARC i\u00e7in bu yeterli de\u011fildir; d=<\/code> domaini, okuyucunun g\u00f6rd\u00fc\u011f\u00fc From<\/code> domainiyle de hizal\u0131 olmal\u0131d\u0131r.<\/p>\n

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

    Sa\u011flay\u0131c\u0131 de\u011fi\u015fikli\u011finden sonra y\u00f6netici uzun DKIM anahtar\u0131n\u0131 DNS’e yap\u0131\u015ft\u0131r\u0131rken sat\u0131r sonundaki baz\u0131 karakterleri kaybediyor. Sa\u011flay\u0131c\u0131 yeni selector ile imzalamaya ba\u015flad\u0131\u011f\u0131 i\u00e7in al\u0131c\u0131lar bozuk a\u00e7\u0131k anahtar\u0131 buluyor ve dkim=fail<\/code> sonucu \u00fcretiyor.<\/p>\n

    DNS de\u011feri sa\u011flay\u0131c\u0131n\u0131n verdi\u011fi bi\u00e7imde yeniden yay\u0131mlan\u0131yor. Yetkili DNS sunucular\u0131 ayn\u0131 yan\u0131t\u0131 vermeye ba\u015flad\u0131\u011f\u0131nda yeni WordPress iletisinde beklenen d=<\/code> ve s=<\/code> de\u011ferleriyle dkim=pass<\/code> g\u00f6r\u00fcl\u00fcyor. Gecikmi\u015f iletiler i\u00e7in eski selector belgelenmi\u015f ge\u00e7i\u015f s\u00fcresi boyunca korunuyor.<\/p>\n

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

    DKIM, imzalanm\u0131\u015f i\u00e7eri\u011fin b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc korur ve al\u0131c\u0131 sistemlere itibar ile DMARC de\u011ferlendirmesinde kullan\u0131lacak sabit bir domain kimli\u011fi sa\u011flar. SMTP g\u00f6nderimi ba\u015far\u0131l\u0131 olsa bile eksik, ge\u00e7ersiz veya hizas\u0131z imza g\u00fcveni azaltabilir.<\/p>\n

    Farkl\u0131 WordPress olaylar\u0131 ba\u015fka sa\u011flay\u0131c\u0131, g\u00f6nderim ak\u0131\u015f\u0131 veya g\u00f6nderen kimli\u011fi kullanabilir. Genel test e-postas\u0131n\u0131n ge\u00e7mesi; parola s\u0131f\u0131rlama, form, sipari\u015f ve toplu bildirimlerin ayn\u0131 domainle imzaland\u0131\u011f\u0131n\u0131 kan\u0131tlamaz.<\/p>\n

    Sa\u011flay\u0131c\u0131ya ait ya da devredilmi\u015f bir imza domaini ve selector yenileme plan\u0131 bulunan b\u00fct\u00fcn d\u00fczenli canl\u0131 g\u00f6nderim ak\u0131\u015flar\u0131nda DKIM kullan\u0131n.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/h2>\n
      \n
    1. Posta sa\u011flay\u0131c\u0131s\u0131n\u0131, g\u00f6r\u00fcnen From domainini, beklenen d=<\/code> domainini, selector de\u011ferini, DNS sorumlusunu ve anahtar yenileme sorumlusunu kaydedin.<\/li>\n
    2. Sa\u011flay\u0131c\u0131n\u0131n g\u00fcncel DKIM kayd\u0131n\u0131 olu\u015fturun veya al\u0131n. TXT de\u011ferini ya da CNAME y\u00f6nlendirmesini istenen selector ad\u0131nda eksiksiz yay\u0131mlay\u0131n; \u00f6zel anahtar\u0131 asla DNS’e koymay\u0131n.<\/li>\n
    3. Selector kayd\u0131n\u0131 yetkili DNS sunucular\u0131ndan sorgulay\u0131n ve t\u00fcm\u00fcn\u00fcn do\u011fru de\u011feri d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n.<\/li>\n
    4. \u0130mzalamay\u0131 sa\u011flay\u0131c\u0131n\u0131n tarifine g\u00f6re a\u00e7\u0131n. Kontroll\u00fc WordPress e-postas\u0131 g\u00f6nderip ham DKIM-Signature<\/code> ve Authentication-Results<\/code> ba\u015fl\u0131klar\u0131n\u0131 inceleyin.<\/li>\n
    5. dkim=pass<\/code> sonucunu, beklenen d=<\/code> ve s=<\/code> de\u011ferlerini ve DMARC hizas\u0131n\u0131 do\u011frulay\u0131n. Birden fazla kritik WordPress bildirimini s\u0131nay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri teknik yol<\/h2>\n

      Sa\u011flay\u0131c\u0131n\u0131n istedi\u011fi bi\u00e7ime g\u00f6re TXT par\u00e7alar\u0131n\u0131 ve t\u0131rnaklar\u0131 ya da CNAME hedefini kontrol edin. Canonicalization y\u00f6ntemini, imzalanan ba\u015fl\u0131klar\u0131, varsa body-length etiketini, anahtar g\u00fcc\u00fcn\u00fc, TTL’yi ve posta listesi veya g\u00fcvenlik arac\u0131n\u0131n i\u00e7erikte yapt\u0131\u011f\u0131 de\u011fi\u015fiklikleri inceleyin.<\/p>\n

      Birbirinden ba\u011f\u0131ms\u0131z hizmetler ve ortamlar i\u00e7in farkl\u0131 selector kullan\u0131n. Anahtar yenilerken yeni a\u00e7\u0131k anahtar\u0131, sa\u011flay\u0131c\u0131 onunla imzalamaya ba\u015flamadan \u00f6nce yay\u0131mlay\u0131n. Eski selector kayd\u0131n\u0131, olas\u0131 en uzun ileti gecikmesi ve DNS \u00f6nbellek s\u00fcresi bitene kadar tutun; kald\u0131rmadan \u00f6nce yeni iletilerin art\u0131k eski selector ile imzalanmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n

      Her \u00f6nemli g\u00f6nderim ak\u0131\u015f\u0131 i\u00e7in g\u00f6r\u00fcnen From domainini, d=<\/code>, s=<\/code>, algoritmay\u0131 ve al\u0131c\u0131 sonucunu i\u00e7eren tam ba\u015fl\u0131k \u00f6rne\u011fi saklay\u0131n. Sa\u011flay\u0131c\u0131n\u0131n kendi domaininde al\u0131nan DKIM pass ge\u00e7erli olabilir, ancak DMARC hizas\u0131 sa\u011flamayabilir.<\/p>\n

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

      \u00d6zel imza anahtar\u0131n\u0131 WordPress’e, DNS’e, loglara, destek kay\u0131tlar\u0131na veya ekran g\u00f6r\u00fcnt\u00fclerine koymay\u0131n. Kuyruk bo\u015falmadan eski selector kayd\u0131n\u0131 silmeyin, ilgisiz hizmetlerde ayn\u0131 selector’\u0131 kullanmay\u0131n ve her dkim=pass<\/code> sonucunu g\u00f6r\u00fcnen From domaininin do\u011fruland\u0131\u011f\u0131 \u015feklinde yorumlamay\u0131n.<\/p>\n

      Yenilemeden \u00f6nce eski selector kay\u0131tlar\u0131n\u0131, sa\u011flay\u0131c\u0131 ayar\u0131n\u0131, TTL’yi ve etkinle\u015ftirme zaman\u0131n\u0131 saklay\u0131n. Yetkili DNS yan\u0131tlar\u0131 farkl\u0131ysa, imza ba\u015far\u0131s\u0131zsa, beklenmeyen domain imzal\u0131yorsa veya kritik bildirimler imzas\u0131z kal\u0131yorsa son do\u011frulanm\u0131\u015f selector’a d\u00f6n\u00fcn ve onun a\u00e7\u0131k anahtar\u0131n\u0131 eri\u015filebilir tutun.<\/p>\n

      \n

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

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

      AIOWS SMTP Y\u00f6neticisi, DKIM yap\u0131land\u0131r\u0131l\u0131rken WordPress taraf\u0131ndaki sa\u011flay\u0131c\u0131 yolunu, g\u00f6nderen kimli\u011fini ve kontroll\u00fc testi g\u00f6r\u00fcn\u00fcr tutar. Teslim edilen test e-postas\u0131nda hangi hizmetin imza att\u0131\u011f\u0131 ve hangi d=<\/code> ile s=<\/code> de\u011ferlerinin kullan\u0131ld\u0131\u011f\u0131 incelenebilir.<\/p>\n

      Ayn\u0131 yoldan g\u00f6nderilen, WordPress’in \u00fcretti\u011fi ger\u00e7ek bildirimlerle kontrol\u00fc tekrarlay\u0131n. Ham ba\u015fl\u0131klar\u0131 sa\u011flay\u0131c\u0131 ayar\u0131 ve yetkili selector kayd\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n. Kimlik bilgilerini ve \u00f6zel anahtar\u0131 WordPress i\u00e7eri\u011fi, loglar ve destek notlar\u0131n\u0131n d\u0131\u015f\u0131nda tutun.<\/p>\n

      AIOWS sa\u011flay\u0131c\u0131n\u0131n DKIM \u00f6zel anahtar\u0131n\u0131 olu\u015fturmaz, DNS selector kayd\u0131n\u0131 yay\u0131mlamaz, anahtar yenilemesini y\u00f6netmez ve d\u0131\u015f posta ak\u0131\u015flar\u0131n\u0131n ayn\u0131 imzay\u0131 kullanmas\u0131n\u0131 sa\u011flayamaz. \u0130mza domainiyle g\u00f6r\u00fcnen From domaini farkl\u0131ysa DMARC hizas\u0131 da olu\u015fturamaz. Bu g\u00f6revler posta sa\u011flay\u0131c\u0131s\u0131 ve DNS sorumlusuna aittir.<\/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