{"id":196,"date":"2026-10-25T17:03:51","date_gmt":"2026-10-25T14:03:51","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/smtp-tarpitting-nedir-anti-spam-savunmasi\/"},"modified":"2026-10-25T17:03:51","modified_gmt":"2026-10-25T14:03:51","slug":"smtp-tarpitting-nedir-anti-spam-savunmasi","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/smtp-tarpitting-nedir-anti-spam-savunmasi\/","title":{"rendered":"SMTP Tarpitting Nedir? Anti-Spam Savunmas\u0131 Olarak Nas\u0131l \u00c7al\u0131\u015f\u0131r, Ne Zaman \u0130\u015fe Yarar ve Ne Zaman Zarar Verebilir?"},"content":{"rendered":"<h2>SMTP tarpitting nedir?<\/h2>\n<p>SMTP tarpitting, mail sunucusunun baz\u0131 SMTP oturumlar\u0131n\u0131 bilin\u00e7li olarak yava\u015flatmas\u0131d\u0131r. Ama\u00e7, \u00f6zellikle otomatik spam botlar\u0131n\u0131n ve k\u00f6t\u00fc yap\u0131land\u0131r\u0131lm\u0131\u015f toplu g\u00f6ndericilerin ayn\u0131 s\u00fcre i\u00e7inde g\u00f6nderebilece\u011fi mesaj say\u0131s\u0131n\u0131 d\u00fc\u015f\u00fcrmek ve sistem kaynaklar\u0131n\u0131 daha verimli kullanmakt\u0131r. \u201cTarpit\u201d benzetmesi, sald\u0131rgan trafi\u011fin yap\u0131\u015fkan bir zeminde ilerleyememesi fikrinden gelir: Ba\u011flant\u0131 tamamen kesilmez; ancak yan\u0131tlar geciktirilir, i\u015flem ad\u0131mlar\u0131 aras\u0131na beklemeler eklenir.<\/p>\n<p>Tarpitting bir \u201cengelleme\u201d tekni\u011fi de\u011fildir; daha \u00e7ok h\u0131z d\u00fc\u015f\u00fcrme tekni\u011fidir. Bu nedenle do\u011fru uyguland\u0131\u011f\u0131nda RBL engeli gibi sert sonu\u00e7lar \u00fcretmeden spam hacmini azaltmaya katk\u0131 sa\u011flar. Yanl\u0131\u015f uyguland\u0131\u011f\u0131nda ise me\u015fru g\u00f6ndericilerde gecikme, time-out ve teslimat sorunlar\u0131na yol a\u00e7abilir.<\/p>\n<h2>Tarpitting hangi problemi \u00e7\u00f6zer?<\/h2>\n<p>SMTP taraf\u0131nda en pahal\u0131 kaynaklar ba\u011flant\u0131 say\u0131s\u0131, e\u015fzamanl\u0131 oturum, CPU ve disk I\/O gibi bile\u015fenlerdir. Spam botlar\u0131 genellikle \u00e7ok say\u0131da k\u0131sa ba\u011flant\u0131 a\u00e7arak, hatal\u0131 komutlar g\u00f6ndererek veya al\u0131c\u0131lar\u0131 tek tek deneyerek (directory harvest \/ recipient probing) sunucuyu zorlar. Tarpitting bu t\u00fcr davran\u0131\u015flarda sald\u0131rgana \u201czaman maliyeti\u201d y\u00fckleyerek:<\/p>\n<ul>\n<li><strong>Deneme ba\u015f\u0131na verimi d\u00fc\u015f\u00fcr\u00fcr:<\/strong> Ayn\u0131 IP\u2019nin bir saatte deneyebilece\u011fi al\u0131c\u0131 say\u0131s\u0131 azal\u0131r.<\/li>\n<li><strong>Kaynak t\u00fcketimini dengeler:<\/strong> Sunucu bir sald\u0131r\u0131 dalgas\u0131nda bile daha kontroll\u00fc \u00e7al\u0131\u015f\u0131r.<\/li>\n<li><strong>Di\u011fer savunmalara zaman kazand\u0131r\u0131r:<\/strong> Rate limit, greylisting, RBL kontrolleri, anomali tespiti gibi katmanlar daha etkili hale gelir.<\/li>\n<\/ul>\n<p>\u00d6nemli nokta: Tarpitting her spam t\u00fcr\u00fcne \u00e7\u00f6z\u00fcm de\u011fildir. \u00d6rne\u011fin iyi itibar kazanm\u0131\u015f ama ele ge\u00e7irilmi\u015f bir hesaptan gelen yetkili SMTP submission trafi\u011finde tarpitting\u2019in yeri farkl\u0131d\u0131r; burada daha \u00e7ok kimlik do\u011frulama politikalar\u0131, anomali tespiti ve g\u00f6nderim limitleri devreye girmelidir.<\/p>\n<h2>SMTP ak\u0131\u015f\u0131nda nerede uygulan\u0131r?<\/h2>\n<p>Tarpitting farkl\u0131 a\u015famalarda uygulanabilir ve se\u00e7ilen nokta, hem etkisini hem de yan etkilerini belirler.<\/p>\n<h3>1) Ba\u011flant\u0131 a\u00e7\u0131l\u0131\u015f\u0131nda (connect banner geciktirme)<\/h3>\n<p>Sunucu TCP ba\u011flant\u0131s\u0131 kurulduktan sonra SMTP banner\u2019\u0131n\u0131 (220) bilin\u00e7li geciktirebilir. Baz\u0131 botlar sab\u0131rs\u0131zd\u0131r; k\u0131sa time-out de\u011ferleri nedeniyle d\u00fc\u015febilir. Ancak me\u015fru MTA\u2019lar genellikle daha toleransl\u0131d\u0131r. Yine de gecikme \u00e7ok y\u00fcksekse, g\u00f6nderen taraf \u201cconnection timed out\u201d ya\u015fayabilir ve tekrar denemeler artabilir.<\/p>\n<h3>2) HELO\/EHLO sonras\u0131 geciktirme<\/h3>\n<p>Sunucu EHLO\/HELO\u2019yu ald\u0131ktan sonra yan\u0131t\u0131 geciktirebilir. Bu, protokole daha uygun ve genelde daha g\u00fcvenli bir noktad\u0131r. Ayr\u0131ca \u201c\u00e7ok h\u0131zl\u0131 konu\u015fan\u201d istemcileri tespit etmek i\u00e7in de kullan\u0131labilir.<\/p>\n<h3>3) RCPT TO a\u015famas\u0131nda geciktirme (al\u0131c\u0131 ke\u015ffine kar\u015f\u0131)<\/h3>\n<p>Recipient probing (\u00e7ok say\u0131da farkl\u0131 al\u0131c\u0131 deneme) RCPT TO a\u015famas\u0131nda ger\u00e7ekle\u015fir. Bu a\u015famada gecikme eklemek, sald\u0131rgana do\u011frudan maliyet bindirir. Ancak burada dikkat gerekir: B\u00fcy\u00fck kurumlar\u0131n MTA\u2019lar\u0131 tek ba\u011flant\u0131da birden \u00e7ok al\u0131c\u0131 deneyebilir. Yanl\u0131\u015f kural, ger\u00e7ek toplu mailleri yava\u015flatabilir.<\/p>\n<h3>4) Hata yan\u0131tlar\u0131nda geciktirme (\u00f6zellikle 5xx)<\/h3>\n<p>\u00d6rne\u011fin ge\u00e7ersiz al\u0131c\u0131ya \u201c550 no such user\u201d d\u00f6nmeden \u00f6nce k\u0131sa bir gecikme koymak, adres hasad\u0131 yapan botlar\u0131n h\u0131z\u0131n\u0131 keser. Bu y\u00f6ntem \u00f6zellikle etkilidir \u00e7\u00fcnk\u00fc botlar genellikle \u00e7ok say\u0131da \u201cyoklama\u201d yapar. Me\u015fru MTA\u2019lar i\u00e7in etkisi daha s\u0131n\u0131rl\u0131d\u0131r; ge\u00e7ersiz al\u0131c\u0131 zaten ba\u015far\u0131s\u0131zd\u0131r.<\/p>\n<h2>Tarpitting ile rate limiting aras\u0131ndaki fark<\/h2>\n<p>Rate limiting, belirli bir IP\/kullan\u0131c\u0131 i\u00e7in saniyede\/dakikada izin verilen ba\u011flant\u0131, oturum veya al\u0131c\u0131 say\u0131s\u0131na s\u0131n\u0131r koyar ve e\u015fik a\u015f\u0131l\u0131nca genelde 4xx\/5xx d\u00f6ner. Tarpitting ise s\u0131n\u0131r\u0131 a\u015fmadan \u00f6nce \u201cyava\u015flat\u0131r\u201d. Pratikte birlikte kullan\u0131l\u0131rlar:<\/p>\n<ul>\n<li><strong>Tarpitting<\/strong> d\u00fc\u015f\u00fck yo\u011funluklu ama s\u00fcrekli k\u00f6t\u00fc davran\u0131\u015f\u0131 yava\u015flat\u0131r.<\/li>\n<li><strong>Rate limiting<\/strong> ani patlamalar\u0131 ve k\u00f6t\u00fcye kullan\u0131m dalgalar\u0131n\u0131 keser.<\/li>\n<\/ul>\n<p>\u00d6rn. d\u00fc\u015f\u00fck gecikmeli tarpitting + daha net e\u015fiklerle rate limiting, tek ba\u015f\u0131na a\u011f\u0131r tarpitting\u2019den daha az yan etki \u00fcretir.<\/p>\n<h2>Ne zaman i\u015fe yarar? Tipik kullan\u0131m senaryolar\u0131<\/h2>\n<h3>Ge\u00e7ersiz al\u0131c\u0131 oran\u0131 y\u00fcksek IP\u2019ler<\/h3>\n<p>Bir g\u00f6nderen IP k\u0131sa s\u00fcrede \u00e7ok say\u0131da olmayan al\u0131c\u0131 deniyorsa, bu genellikle tarama veya hatal\u0131 liste i\u015faretidir. Bu durumda tarpitting, sald\u0131r\u0131n\u0131n h\u0131z\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcrken \u201ctam engel\u201d koymadan davran\u0131\u015f de\u011fi\u015fikli\u011fi i\u00e7in bask\u0131 olu\u015fturur.<\/p>\n<h3>Komut hatas\u0131 yapan otomasyonlar<\/h3>\n<p>Yanl\u0131\u015f SMTP komut s\u0131ras\u0131, hatal\u0131 PIPELINING kullan\u0131m\u0131 veya a\u015f\u0131r\u0131 h\u0131zl\u0131 komut g\u00f6nderen istemciler, tarpitting ile disipline edilebilir. Bu, protokol d\u0131\u015f\u0131 otomasyonlar\u0131n sunucuya y\u00fck bindirmesini azalt\u0131r.<\/p>\n<h3>RBL\/itibar sinyalleriyle tetiklenen yava\u015flatma<\/h3>\n<p>\u0130tibar d\u00fc\u015f\u00fck IP\u2019lere veya yeni g\u00f6r\u00fclen kaynaklara daha fazla gecikme uygulamak, iyi itibar\/whitelist\u2019teki kaynaklar\u0131 ise etkilememek m\u00fcmk\u00fcnd\u00fcr. Burada ama\u00e7, \u201cherkese ayn\u0131 muamele\u201d yerine risk temelli davranmakt\u0131r.<\/p>\n<h2>Ne zaman zarar verebilir? Yan etkiler ve teslimat riskleri<\/h2>\n<h3>Gecikme birikimi ve time-out<\/h3>\n<p>SMTP\u2019de her ad\u0131m i\u00e7in g\u00f6nderen tarafta time-out de\u011ferleri vard\u0131r. \u00c7ok agresif tarpitting, g\u00f6nderen MTA\u2019n\u0131n oturumu d\u00fc\u015f\u00fcrmesine ve mesaj\u0131 \u201cdeferred\u201d durumuna almas\u0131na yol a\u00e7abilir. Bu da al\u0131c\u0131 taraf\u0131nda gecikmeli teslimat demektir. \u00d6zellikle kritik i\u015f e-postalar\u0131nda dakikalar bile \u00f6nemli olabilir.<\/p>\n<h3>Geri deneme trafi\u011finin artmas\u0131<\/h3>\n<p>Yava\u015flat\u0131lan veya ge\u00e7ici hataya d\u00fc\u015fen g\u00f6nderimler tekrar denenece\u011fi i\u00e7in, toplam ba\u011flant\u0131 say\u0131s\u0131 artabilir. Bu paradoksal bir \u015fekilde sunucu y\u00fck\u00fcn\u00fc y\u00fckseltebilir. Bu y\u00fczden tarpitting gecikmeleri k\u0131sa ve hedefli olmal\u0131d\u0131r.<\/p>\n<h3>Me\u015fru toplu g\u00f6nderimlerde performans d\u00fc\u015f\u00fc\u015f\u00fc<\/h3>\n<p>Bankalar, ERP\/CRM sistemleri veya kurumsal bildirim altyap\u0131lar\u0131 k\u0131sa s\u00fcrede \u00e7ok say\u0131da al\u0131c\u0131ya mail g\u00f6nderebilir. Kurallar RCPT TO baz\u0131nda \u00e7ok sertse, bu t\u00fcr g\u00f6nderimler yava\u015flayabilir. Bu y\u00fczden bilinen g\u00f6nderici IP\u2019leri veya do\u011frulanm\u0131\u015f yollar i\u00e7in istisnalar planlanmal\u0131d\u0131r.<\/p>\n<h3>Yanl\u0131\u015f te\u015fhis: Sorun spam de\u011fil yap\u0131land\u0131rma olabilir<\/h3>\n<p>\u00d6rne\u011fin bir i\u015f orta\u011f\u0131n\u0131z\u0131n mail sunucusu yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015fsa ve s\u00fcrekli hata \u00fcretiyorsa, tarpitting semptomu saklayabilir. Burada do\u011fru yakla\u015f\u0131m, \u00f6nce log analiziyle k\u00f6k nedeni bulmak, gerekirse kar\u015f\u0131 tarafla d\u00fczeltme plan\u0131 yapmakt\u0131r.<\/p>\n<h2>Pratik bir tarpitting politikas\u0131 nas\u0131l tasarlan\u0131r?<\/h2>\n<h3>1) Hedefi netle\u015ftirin<\/h3>\n<p>Hedefiniz al\u0131c\u0131 ke\u015ffini yava\u015flatmak m\u0131, botlar\u0131 elemek mi, yoksa genel y\u00fck m\u00fc? Hedefe g\u00f6re en do\u011fru a\u015famada uygulars\u0131n\u0131z. \u00c7o\u011fu i\u015fletme i\u00e7in \u201cge\u00e7ersiz al\u0131c\u0131 ve protokol d\u0131\u015f\u0131 davran\u0131\u015f\u201d odakl\u0131 tarpitting daha g\u00fcvenlidir.<\/p>\n<h3>2) K\u0131sa gecikmelerle ba\u015flay\u0131n<\/h3>\n<p>\u0130lk a\u015famada saniyeler mertebesinde, k\u00fc\u00e7\u00fck gecikmeler daha uygundur. Gereksiz yere uzun beklemeler, me\u015fru trafi\u011fi de bozar. Gecikmeyi artt\u0131rmak yerine, tekrar eden k\u00f6t\u00fc davran\u0131\u015fta kademeli artt\u0131r\u0131m daha sa\u011fl\u0131kl\u0131d\u0131r.<\/p>\n<h3>3) Sinyal bazl\u0131 tetikleyin<\/h3>\n<p>Tarpitting\u2019i \u201cher ba\u011flant\u0131ya\u201d uygulamak yerine a\u015fa\u011f\u0131daki sinyallerle tetiklemek tipik olarak daha iyi sonu\u00e7 verir:<\/p>\n<ul>\n<li>Belirli s\u00fcrede y\u00fcksek say\u0131da ge\u00e7ersiz al\u0131c\u0131 denemesi<\/li>\n<li>HELO\/EHLO format\u0131 anormal veya bo\u015f<\/li>\n<li>Komutlar\u0131 \u00e7ok h\u0131zl\u0131 g\u00f6nderme, PIPELINING\u2019\u0131 yanl\u0131\u015f kullanma<\/li>\n<li>Yeni g\u00f6r\u00fclen IP\u2019ler (dikkatli ve k\u0131sa gecikmelerle)<\/li>\n<\/ul>\n<h3>4) \u0130stisna (whitelist) yakla\u015f\u0131m\u0131n\u0131 y\u00f6netin<\/h3>\n<p>\u0130\u015f ortaklar\u0131n\u0131z\u0131n, uygulama sunucular\u0131n\u0131z\u0131n veya kritik bildirim sistemlerinizin g\u00f6nderici IP\u2019leri belirliyse, bu kaynaklar\u0131 tarpitting\u2019ten muaf tutmak gecikme riskini azalt\u0131r. Ancak whitelist\u2019i \u201csonsuz g\u00fcven\u201d olarak g\u00f6rmeyin; bu IP\u2019ler ele ge\u00e7irilirse risk b\u00fcy\u00fcr. Whitelist\u2019e ra\u011fmen makul rate limit\u2019ler b\u0131rakmak iyi bir denge sa\u011flar.<\/p>\n<h3>5) \u00d6l\u00e7\u00fcn ve geri al\u0131nabilir tasarlay\u0131n<\/h3>\n<p>Her de\u011fi\u015fiklikte \u015fu metrikleri takip edin: ba\u011flant\u0131 say\u0131s\u0131, deferred oran\u0131, teslimat gecikmesi, ge\u00e7ersiz al\u0131c\u0131 oran\u0131 ve \u015fikayet\/geri d\u00f6n\u00fc\u015fler. Tarpitting ayarlar\u0131, geri al\u0131nabilir ve h\u0131zl\u0131 revize edilebilir olmal\u0131d\u0131r.<\/p>\n<h2>Tarpitting, greylisting ve 4xx stratejileri birlikte nas\u0131l d\u00fc\u015f\u00fcn\u00fcl\u00fcr?<\/h2>\n<p>Greylisting ge\u00e7ici 4xx ile g\u00f6ndereni tekrar denemeye zorlar; tarpitting ise oturum i\u00e7ini yava\u015flat\u0131r. Birlikte yanl\u0131\u015f kurgulan\u0131rsa gecikme katlan\u0131r. Genel prensip:<\/p>\n<ul>\n<li>Greylisting kullan\u0131l\u0131yorsa tarpitting\u2019i daha hafif tutun.<\/li>\n<li>Tarpitting\u2019i daha \u00e7ok \u201cge\u00e7ersiz al\u0131c\u0131\/protokol hatas\u0131\u201d gibi net k\u00f6t\u00fc sinyallere ba\u011flay\u0131n.<\/li>\n<li>\u0130\u015f kritik ak\u0131\u015flar i\u00e7in gereksiz 4xx \u00fcretmekten ka\u00e7\u0131n\u0131n; gecikme yerine hedefli engel veya istisna daha iyi olabilir.<\/li>\n<\/ul>\n<h2>Sonu\u00e7: Do\u011fru dozda, do\u011fru yerde<\/h2>\n<p>SMTP tarpitting, spam ve bot trafi\u011fine kar\u015f\u0131 etkili bir \u201cs\u00fcrt\u00fcnme\u201d mekanizmas\u0131d\u0131r: Tek ba\u015f\u0131na mucize de\u011fildir, fakat do\u011fru sinyallerle, k\u0131sa gecikmelerle ve iyi izleme ile uyguland\u0131\u011f\u0131nda anti-spam savunma katman\u0131n\u0131za de\u011fer katar. En kritik nokta, me\u015fru g\u00f6ndericilerin teslimat\u0131n\u0131 riske atmayacak \u015fekilde hedefli ve \u00f6l\u00e7\u00fcl\u00fc kullanmakt\u0131r.<\/p>\n<p>Mail altyap\u0131n\u0131z\u0131 y\u00f6netirken tarpitting gibi davran\u0131\u015fsal kontrolleri; SPF\/DKIM\/DMARC, rate limiting, log analizi ve kullan\u0131c\u0131 g\u00fcvenli\u011fi politikalar\u0131yla birlikte ele almak daha dengeli sonu\u00e7 verir. MX1Mail gibi kurumsal e-posta hizmetlerinde de ama\u00e7, g\u00fcvenlik ve teslim edilebilirlik dengesini koruyarak operasyonel y\u00fck\u00fc azaltacak do\u011fru politikalar\u0131 uygulamakt\u0131r.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SMTP tarpitting\u2019in spam g\u00f6nderenleri yava\u015flatma mant\u0131\u011f\u0131n\u0131, hangi a\u015famalarda uygulanaca\u011f\u0131n\u0131, yanl\u0131\u015f ayarlar\u0131n teslimata etkisini ve pratik politika \u00f6nerilerini \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[391,226,277],"class_list":["post-196","post","type-post","status-publish","format-standard","hentry","category-e-posta-guvenligi","tag-anti-spam","tag-smtp","tag-teslim-edilebilirlik"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/comments?post=196"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/196\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=196"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=196"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}