{"id":173,"date":"2026-10-20T09:01:09","date_gmt":"2026-10-20T06:01:09","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/kurumsal-e-postada-gonderim-limitleri-anti-abuse-rate-limit-recipient-limit\/"},"modified":"2026-10-20T09:01:09","modified_gmt":"2026-10-20T06:01:09","slug":"kurumsal-e-postada-gonderim-limitleri-anti-abuse-rate-limit-recipient-limit","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/kurumsal-e-postada-gonderim-limitleri-anti-abuse-rate-limit-recipient-limit\/","title":{"rendered":"Kurumsal E-Postada G\u00f6nderim Limitleri ve Anti-Abuse Tasar\u0131m\u0131: Rate Limit, Recipient Limit ve Anomali Tespiti"},"content":{"rendered":"<h2>G\u00f6nderim limitleri neden bir \u201cg\u00fcvenlik\u201d konusudur?<\/h2>\n<p>Kurumsal e-posta altyap\u0131s\u0131nda g\u00fcvenlik denince akla \u00e7o\u011fu zaman kimlik do\u011frulama, MFA, TLS veya zararl\u0131 ek analizi gelir. Ancak pratikte en \u00e7ok hasar\u0131 olu\u015fturan senaryolardan biri, ele ge\u00e7irilmi\u015f bir hesab\u0131n veya yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f bir uygulaman\u0131n k\u0131sa s\u00fcrede \u00e7ok say\u0131da e-posta g\u00f6ndermesidir. Bu durum yaln\u0131zca spam \u015fikayetlerine ve itibar kayb\u0131na yol a\u00e7maz; ayn\u0131 zamanda sistem kaynaklar\u0131n\u0131 t\u00fcketir, kuyruklar\u0131 \u015fi\u015firir, di\u011fer kullan\u0131c\u0131lar\u0131n normal trafi\u011fini yava\u015flat\u0131r ve alan ad\u0131n\u0131z\u0131n teslim edilebilirli\u011fini uzun s\u00fcre olumsuz etkileyebilir.<\/p>\n<p>Bu y\u00fczden g\u00f6nderim limitleri (rate limit, recipient limit, mesaj boyutu limiti, e\u015fzamanl\u0131 ba\u011flant\u0131 limiti gibi) \u201canti-abuse\u201d tasar\u0131m\u0131n\u0131n temel par\u00e7alar\u0131d\u0131r. Do\u011fru uyguland\u0131\u011f\u0131nda, ger\u00e7ek kullan\u0131c\u0131lar\u0131n i\u015f ak\u0131\u015f\u0131n\u0131 bozmadan ola\u011fan d\u0131\u015f\u0131 davran\u0131\u015flar\u0131 s\u0131n\u0131rlar, olay\u0131n etkisini k\u00fc\u00e7\u00fclt\u00fcr ve m\u00fcdahale i\u00e7in zaman kazand\u0131r\u0131r.<\/p>\n<h2>Temel kavramlar: Ne t\u00fcr limitlerden bahsediyoruz?<\/h2>\n<h3>Rate limit (g\u00f6nderim h\u0131z\u0131 limiti)<\/h3>\n<p>Belirli bir s\u00fcre penceresinde (\u00f6r. dakika\/saat\/g\u00fcn) g\u00f6nderilebilecek mesaj say\u0131s\u0131n\u0131 s\u0131n\u0131rlar. Rate limit, en \u00e7ok \u201chesap ele ge\u00e7irildi ve spam bas\u0131yor\u201d senaryosunda i\u015fe yarar. Limit \u00e7ok d\u00fc\u015f\u00fck olursa sat\u0131\u015f, destek veya yo\u011fun yaz\u0131\u015fma yapan ekipler etkilenir; \u00e7ok y\u00fcksek olursa koruma etkisi azal\u0131r.<\/p>\n<h3>Recipient limit (al\u0131c\u0131 say\u0131s\u0131 limiti)<\/h3>\n<p>Bir e-postan\u0131n toplam al\u0131c\u0131 say\u0131s\u0131n\u0131 (To+Cc+Bcc) veya belirli bir s\u00fcre i\u00e7inde toplam benzersiz al\u0131c\u0131 say\u0131s\u0131n\u0131 s\u0131n\u0131rlar. Bu limit, hem yanl\u0131\u015fl\u0131kla y\u00fczlerce ki\u015fiye giden hatal\u0131 toplu g\u00f6nderimleri hem de spam davran\u0131\u015f\u0131n\u0131 azalt\u0131r. Ayr\u0131ca da\u011f\u0131t\u0131m listeleri (mailing list) ve grup adresleri bu limitleri dolayl\u0131 bi\u00e7imde a\u015fabilece\u011fi i\u00e7in, de\u011ferlendirme yap\u0131l\u0131rken bu t\u00fcr adreslerin nas\u0131l \u00e7\u00f6z\u00fcmlendi\u011fi (expand) dikkate al\u0131nmal\u0131d\u0131r.<\/p>\n<h3>Concurrency limit (e\u015fzamanl\u0131 ba\u011flant\u0131\/oturum limiti)<\/h3>\n<p>Ayn\u0131 kullan\u0131c\u0131, ayn\u0131 IP veya ayn\u0131 uygulama i\u00e7in ayn\u0131 anda a\u00e7\u0131labilecek SMTP oturumu say\u0131s\u0131n\u0131 s\u0131n\u0131rlar. Botlar ve k\u00f6t\u00fc niyetli otomasyonlar genellikle paralel ba\u011flant\u0131larla hacmi art\u0131rmaya \u00e7al\u0131\u015f\u0131r. Bu limit sistem kaynaklar\u0131n\u0131 korur.<\/p>\n<h3>Message size ve attachment limitleri<\/h3>\n<p>Bu limitlerin ana hedefi suistimal olmasa da, veri s\u0131z\u0131nt\u0131s\u0131 riskini ve servis kalitesi sorunlar\u0131n\u0131 azalt\u0131r. \u00c7ok b\u00fcy\u00fck ekler kuyruklar\u0131 b\u00fcy\u00fct\u00fcr ve tekrar denemelerde bant geni\u015fli\u011fini t\u00fcketir. \u015eirket i\u00e7inde dosya payla\u015f\u0131m\u0131 ve ba\u011flant\u0131 (link) yakla\u015f\u0131m\u0131 te\u015fvik edilerek e-posta daha verimli hale getirilebilir.<\/p>\n<h2>Limit tasar\u0131m\u0131: Tek bir say\u0131 herkese uymaz<\/h2>\n<p>Limitleri \u201cher kullan\u0131c\u0131ya ayn\u0131\u201d \u015feklinde tan\u0131mlamak kolayd\u0131r ama genellikle do\u011fru de\u011fildir. \u0130yi bir anti-abuse tasar\u0131m\u0131, farkl\u0131 kullan\u0131c\u0131 tiplerinin farkl\u0131 davran\u0131\u015flar\u0131n\u0131 kabul eder.<\/p>\n<h3>Persona bazl\u0131 yakla\u015f\u0131m<\/h3>\n<ul>\n<li><strong>Standart kullan\u0131c\u0131lar:<\/strong> Normal yaz\u0131\u015fma hacmi, g\u00fcn i\u00e7inde dalgalan\u0131r. Orta seviyede rate limit ve al\u0131c\u0131 limiti \u00e7o\u011funlukla yeterlidir.<\/li>\n<li><strong>Destek\/\u00e7a\u011fr\u0131 merkezi:<\/strong> \u00c7ok say\u0131da d\u0131\u015f m\u00fc\u015fteriye yan\u0131t verebilir. Burada limitler daha y\u00fcksek olmal\u0131; ancak anomali tespiti daha hassas \u00e7al\u0131\u015fmal\u0131d\u0131r.<\/li>\n<li><strong>Sat\u0131\u015f ekipleri:<\/strong> Bazen kampanya benzeri y\u00fcksek hacimler g\u00f6r\u00fclebilir. Pazarlama ama\u00e7l\u0131 toplu g\u00f6nderim ile bire bir sat\u0131\u015f yaz\u0131\u015fmas\u0131n\u0131 ay\u0131rmak, alan ad\u0131 itibar\u0131n\u0131 korumaya yard\u0131mc\u0131 olur.<\/li>\n<li><strong>Uygulama\/cihaz hesaplar\u0131:<\/strong> Web sitesi bildirimleri, ERP\/CRM uyar\u0131lar\u0131, yaz\u0131c\u0131\/scan-to-mail gibi kaynaklar. Bu hesaplara \u00f6zel ve daha dar kapsaml\u0131 limitler, ayr\u0131ca IP k\u0131s\u0131tlamas\u0131 gibi ek \u00f6nlemler uygundur.<\/li>\n<\/ul>\n<h3>Zaman penceresi se\u00e7imi<\/h3>\n<p>Sadece \u201cg\u00fcnl\u00fck limit\u201d koymak \u00e7o\u011fu zaman ge\u00e7 fark ettirir. K\u0131sa pencere (dakika\/15 dakika) patlamalar\u0131 yakalar, uzun pencere (saat\/g\u00fcn) s\u00fcrekli suistimali s\u0131n\u0131rlar. Pratikte katmanl\u0131 yakla\u015f\u0131m kullan\u0131l\u0131r: k\u0131sa pencere + saatlik + g\u00fcnl\u00fck.<\/p>\n<h2>Yanl\u0131\u015f pozitifleri azaltma: \u0130\u015f ak\u0131\u015f\u0131 bozulmas\u0131n<\/h2>\n<p>G\u00f6nderim limitlerinin en b\u00fcy\u00fck riski, me\u015fru i\u015f s\u00fcre\u00e7lerini engellemesidir. Bu riski azaltmak i\u00e7in limitler \u201csert duvar\u201d gibi de\u011fil, kademeli frene basan bir sistem gibi tasarlanabilir.<\/p>\n<h3>Kademeli yapt\u0131r\u0131mlar<\/h3>\n<ul>\n<li><strong>Uyar\u0131 e\u015fi\u011fi:<\/strong> Kullan\u0131c\u0131 yakla\u015f\u0131nca bilgilendirme veya admin bildirimleri.<\/li>\n<li><strong>Ge\u00e7ici yava\u015flatma:<\/strong> H\u0131z limiti a\u015f\u0131l\u0131nca her mesaj\u0131 reddetmek yerine k\u0131sa s\u00fcreli geciktirme (throttling).<\/li>\n<li><strong>Ge\u00e7ici blok:<\/strong> Belirli bir s\u00fcre g\u00f6nderimi durdurup olay incelemesi i\u00e7in zaman kazanma.<\/li>\n<\/ul>\n<h3>Whitelist\/istisna y\u00f6netimi<\/h3>\n<p>\u0130stisnalar mutlaka kay\u0131t alt\u0131na al\u0131nmal\u0131 ve periyodik g\u00f6zden ge\u00e7irilmelidir. \u201cBir kere a\u00e7t\u0131k\u201d yakla\u015f\u0131m\u0131, uzun vadede g\u00fcvenlik a\u00e7\u0131\u011f\u0131na d\u00f6n\u00fc\u015f\u00fcr. \u0130stisna verilen hesaplar\u0131n parolas\u0131, eri\u015fim \u015fekli ve kaynak IP\u2019leri daha s\u0131k\u0131 takip edilmelidir.<\/p>\n<h2>Anomali tespiti: Limitlerden daha ak\u0131ll\u0131 bir katman<\/h2>\n<p>Limitler iyi bir ba\u015flang\u0131\u00e7t\u0131r; ancak sald\u0131rganlar limitlere tak\u0131lmayacak \u015fekilde \u201cdaha yava\u015f\u201d spam g\u00f6nderebilir. Bu nedenle anomali tespiti, davran\u0131\u015f de\u011fi\u015fimlerini yakalamaya odaklan\u0131r.<\/p>\n<h3>Takip edilebilecek pratik sinyaller<\/h3>\n<ul>\n<li><strong>Yeni \u00fclke\/ASN\/IP\u2019den giri\u015f ve hemen ard\u0131ndan y\u00fcksek g\u00f6nderim:<\/strong> Hesap ele ge\u00e7irilmesi g\u00f6stergesi olabilir.<\/li>\n<li><strong>Al\u0131c\u0131 \u00e7e\u015fitlili\u011finde ani art\u0131\u015f:<\/strong> Kullan\u0131c\u0131 normalde az say\u0131da ki\u015fiyle yaz\u0131\u015f\u0131rken birden y\u00fczlerce benzersiz al\u0131c\u0131ya g\u00f6nderim yapmas\u0131.<\/li>\n<li><strong>Bounce oran\u0131nda y\u00fckseli\u015f:<\/strong> Ge\u00e7ersiz adreslere g\u00f6nderim, liste denemesi veya spam belirtisi olabilir.<\/li>\n<li><strong>\u015eikayet\/abuse sinyallerinin art\u0131\u015f\u0131:<\/strong> Kullan\u0131c\u0131dan kaynakl\u0131 i\u00e7erik veya hesap suistimali.<\/li>\n<li><strong>G\u00f6nderim saatlerinde ola\u011fand\u0131\u015f\u0131 kayma:<\/strong> Mesai d\u0131\u015f\u0131 saatlerde y\u00fcksek hacim.<\/li>\n<\/ul>\n<h3>Basit e\u015fikler + operasyonel s\u00fcre\u00e7<\/h3>\n<p>Anomali tespitinde her zaman karma\u015f\u0131k makine \u00f6\u011frenmesi gerekmez. Bir\u00e7ok KOB\u0130 i\u00e7in basit e\u015fikler ve iyi bir operasyonel s\u00fcre\u00e7 yeterlidir: olay kayd\u0131 a\u00e7ma, kullan\u0131c\u0131 do\u011frulama, parolay\u0131 s\u0131f\u0131rlama, istemci oturumlar\u0131n\u0131 sonland\u0131rma, gerekirse ge\u00e7ici g\u00f6nderim k\u0131s\u0131t\u0131 uygulama.<\/p>\n<h2>Uygulama hesaplar\u0131 ve cihazlar: En s\u0131k unutulan risk alan\u0131<\/h2>\n<p>Kurumsal ortamlarda \u201cno-reply@\u201d, \u201cscanner@\u201d veya bir uygulama SMTP hesab\u0131 genellikle uzun s\u00fcre ayn\u0131 parolayla kal\u0131r, payla\u015f\u0131l\u0131r ve bir\u00e7ok sistemde kay\u0131tl\u0131d\u0131r. Bu hesaplar ele ge\u00e7irilirse h\u0131zl\u0131 \u015fekilde suistimal edilebilir.<\/p>\n<h3>\u0130yi uygulamalar<\/h3>\n<ul>\n<li><strong>Ayr\u0131 hesap kullan\u0131m\u0131:<\/strong> \u0130nsan kullan\u0131c\u0131yla uygulama hesab\u0131n\u0131 ay\u0131r\u0131n.<\/li>\n<li><strong>Kaynak IP k\u0131s\u0131tlamas\u0131:<\/strong> Sadece ilgili sunucu\/cihazdan g\u00f6nderime izin verin.<\/li>\n<li><strong>Daha d\u00fc\u015f\u00fck limitler:<\/strong> Uygulaman\u0131n normal hacmini \u00f6l\u00e7\u00fcp biraz \u00fczerinde limit tan\u0131mlay\u0131n.<\/li>\n<li><strong>D\u00fczenli parola rotasyonu:<\/strong> De\u011fi\u015fiklik sonras\u0131 t\u00fcm ba\u011f\u0131ml\u0131 sistemlerin g\u00fcncellendi\u011finden emin olun.<\/li>\n<\/ul>\n<h2>\u0130tibar ve teslim edilebilirlik a\u00e7\u0131s\u0131ndan etkisi<\/h2>\n<p>Bir alan ad\u0131 veya IP \u00fczerinden aniden spam benzeri trafik \u00e7\u0131kmas\u0131, al\u0131c\u0131 sistemlerde g\u00fcven kayb\u0131na yol a\u00e7abilir. Sonu\u00e7lar genellikle \u015funlard\u0131r: spam klas\u00f6r\u00fcne d\u00fc\u015fme, ge\u00e7ici 4xx ertelemeleri, baz\u0131 al\u0131c\u0131larda kal\u0131c\u0131 5xx retleri ve uzun s\u00fcreli itibar toparlama ihtiyac\u0131. Bu y\u00fczden limitler, yaln\u0131zca \u201ci\u00e7 g\u00fcvenlik\u201d de\u011fil, ayn\u0131 zamanda teslim edilebilirlik y\u00f6netimidir.<\/p>\n<h2>Ad\u0131m ad\u0131m \u00f6rnek bir limit stratejisi (genel \u00e7er\u00e7eve)<\/h2>\n<ol>\n<li><strong>Mevcut trafi\u011fi \u00f6l\u00e7\u00fcn:<\/strong> Kullan\u0131c\u0131 ba\u015f\u0131na saatlik\/g\u00fcnl\u00fck g\u00f6nderim, en yo\u011fun ekipler, uygulama hesaplar\u0131.<\/li>\n<li><strong>Persona gruplar\u0131 \u00e7\u0131kar\u0131n:<\/strong> Standart, destek, sat\u0131\u015f, uygulama\/c\u0130haz.<\/li>\n<li><strong>Katmanl\u0131 e\u015fikler belirleyin:<\/strong> K\u0131sa pencere + saatlik + g\u00fcnl\u00fck; ayr\u0131ca al\u0131c\u0131 limiti ekleyin.<\/li>\n<li><strong>Kademeli yapt\u0131r\u0131m\u0131 se\u00e7in:<\/strong> Uyar\u0131, throttling, ge\u00e7ici blok.<\/li>\n<li><strong>\u0130zleme ve alarm kurun:<\/strong> Bounce art\u0131\u015f\u0131, benzersiz al\u0131c\u0131 art\u0131\u015f\u0131, ola\u011fand\u0131\u015f\u0131 saat.<\/li>\n<li><strong>\u0130stisnalar\u0131 y\u00f6netin:<\/strong> Zaman s\u0131n\u0131rl\u0131 ve gerek\u00e7eli istisnalar.<\/li>\n<li><strong>Olay m\u00fcdahale ak\u0131\u015f\u0131 yaz\u0131n:<\/strong> Kim onaylar, nas\u0131l do\u011frulan\u0131r, hangi ad\u0131mlar at\u0131l\u0131r.<\/li>\n<\/ol>\n<h2>Sonu\u00e7: G\u00fcvenlik, s\u00fcreklilik ve kullan\u0131c\u0131 deneyimi dengesini kurmak<\/h2>\n<p>G\u00f6nderim limitleri ve anomali tespiti, tek ba\u015f\u0131na \u201cspam engelleme\u201d de\u011fildir; kurumun e-posta s\u00fcreklili\u011fini koruyan bir emniyet kemeridir. Ama\u00e7, ola\u011fan d\u0131\u015f\u0131 bir durumda hasar\u0131 b\u00fcy\u00fcmeden s\u0131n\u0131rlamak ve ekibin olaya kontroll\u00fc \u015fekilde m\u00fcdahale edebilmesini sa\u011flamakt\u0131r.<\/p>\n<p>Kurumsal e-posta altyap\u0131n\u0131z\u0131 planlarken, kulland\u0131\u011f\u0131n\u0131z platformun y\u00f6netim taraf\u0131nda bu t\u00fcr limitlerin ve izleme pratiklerinin operasyonel olarak s\u00fcrd\u00fcr\u00fclebilir olmas\u0131na dikkat edin. MX1Mail \u00fczerinde de e-posta y\u00f6neti\u015fimi yakla\u015f\u0131m\u0131n\u0131z\u0131 belirlerken, hesap tiplerine g\u00f6re politika uygulama ve d\u00fczenli g\u00f6zden ge\u00e7irme al\u0131\u015fkanl\u0131\u011f\u0131 edinmek, uzun vadede teslim edilebilirlik ve g\u00fcvenlik a\u00e7\u0131s\u0131ndan de\u011fer sa\u011flar.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kurumsal e-posta altyap\u0131s\u0131nda spam\/bot kaynakl\u0131 suistimali azaltmak i\u00e7in g\u00f6nderim h\u0131z\u0131, al\u0131c\u0131 limiti ve anomali tespitini nas\u0131l tasarlayaca\u011f\u0131n\u0131z\u0131 \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,281,159],"class_list":["post-173","post","type-post","status-publish","format-standard","hentry","category-e-posta-guvenligi","tag-anti-spam","tag-deliverability","tag-e-posta-yonetimi"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/173","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=173"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/173\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}