{"id":200,"date":"2026-10-26T17:01:37","date_gmt":"2026-10-26T14:01:37","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/sieve-server-side-e-posta-filtre-kurallari-nedir\/"},"modified":"2026-10-26T17:01:37","modified_gmt":"2026-10-26T14:01:37","slug":"sieve-server-side-e-posta-filtre-kurallari-nedir","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/sieve-server-side-e-posta-filtre-kurallari-nedir\/","title":{"rendered":"Sieve (Server-Side) E-Posta Filtre Kurallar\u0131 Nedir? Kurumsal Mail Ak\u0131\u015f\u0131nda G\u00fcvenli ve Tutarl\u0131 Otomasyon Rehberi"},"content":{"rendered":"<h2>Sieve nedir ve neden \u201cserver-side\u201d filtreleme denir?<\/h2>\n<p>Sieve, e-postalar posta kutunuza teslim edilmeden veya teslim s\u0131ras\u0131nda \u00e7al\u0131\u015ft\u0131r\u0131lan, sunucu tarafl\u0131 kural setlerini tan\u0131mlamak i\u00e7in kullan\u0131lan bir filtreleme dilidir. \u201cServer-side\u201d denmesinin nedeni, kurallar\u0131n Outlook, mobil uygulama veya webmail gibi bir istemcide de\u011fil; mail sunucusunun \u00fczerinde, merkezi bi\u00e7imde uygulanmas\u0131d\u0131r. Bu yakla\u015f\u0131m \u00f6zellikle kurumsal yap\u0131larda \u00f6nemlidir \u00e7\u00fcnk\u00fc kullan\u0131c\u0131 bilgisayar\u0131n\u0131 kapatsa bile kurallar \u00e7al\u0131\u015fmaya devam eder, farkl\u0131 cihazlar aras\u0131nda tutarl\u0131l\u0131k sa\u011flar ve operasyonel standartlar\u0131 uygulamay\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>Sieve\u2019in temel amac\u0131, gelen e-postay\u0131 belirli ko\u015fullara g\u00f6re s\u0131n\u0131fland\u0131rmak ve otomatik aksiyon almakt\u0131r. Bu aksiyonlar; belirli bir klas\u00f6re ta\u015f\u0131ma, etiket\/flag ekleme, iletme, otomatik yan\u0131t, reddetme veya belirli t\u00fcr mesajlar\u0131 \u00f6zel i\u015f ak\u0131\u015flar\u0131na y\u00f6nlendirme gibi se\u00e7enekleri i\u00e7erebilir. Her ortamda ayn\u0131 \u00f6zellik seti bulunmayabilir; bu y\u00fczden Sieve\u2019i \u201cmant\u0131k\u201d olarak d\u00fc\u015f\u00fcnmek daha do\u011frudur: Mesaj \u00f6zelliklerine bak, ko\u015fulu de\u011ferlendir, eylemi uygula.<\/p>\n<h2>\u0130stemci kurallar\u0131 ile Sieve kurallar\u0131 aras\u0131ndaki fark<\/h2>\n<p>Pek \u00e7ok \u015firkette kullan\u0131c\u0131lar Outlook veya ba\u015fka bir istemci i\u00e7inde kurallar tan\u0131mlar. Bu kurallar pratik olsa da kurumsal \u00f6l\u00e7ekte baz\u0131 riskler ve tutars\u0131zl\u0131klar do\u011furabilir. Sieve\u2019in avantaj\u0131n\u0131 anlamak i\u00e7in iki yakla\u015f\u0131m\u0131 kar\u015f\u0131la\u015ft\u0131ral\u0131m.<\/p>\n<ul>\n<li><strong>\u00c7al\u0131\u015fma yeri:<\/strong> \u0130stemci kurallar\u0131 kullan\u0131c\u0131 cihaz\u0131nda veya o istemci oturumunda \u00e7al\u0131\u015f\u0131r. Sieve kurallar\u0131 sunucuda \u00e7al\u0131\u015f\u0131r.<\/li>\n<li><strong>S\u00fcreklilik:<\/strong> Kullan\u0131c\u0131n\u0131n cihaz\u0131 kapal\u0131yken istemci kural\u0131 \u00e7al\u0131\u015fmayabilir. Sieve, 7\/24 \u00e7al\u0131\u015f\u0131r.<\/li>\n<li><strong>Tutarl\u0131l\u0131k:<\/strong> Kullan\u0131c\u0131 telefonunda ba\u015fka, bilgisayar\u0131nda ba\u015fka davran\u0131\u015f ya\u015fayabilir. Sieve tek bir merkezden uygulan\u0131r.<\/li>\n<li><strong>Operasyonel kontrol:<\/strong> \u0130stemci kurallar\u0131 \u00e7o\u011fu zaman ki\u015finin tercihlerine b\u0131rak\u0131l\u0131r. Sieve, IT\u2019nin \u015fablonlar ve standartlar olu\u015fturmas\u0131na daha uygundur.<\/li>\n<li><strong>Sorun giderme:<\/strong> \u0130stemci kurallar\u0131nda sorun, cihaz\/istemci baz\u0131nda da\u011f\u0131l\u0131r. Sieve taraf\u0131nda kural setini merkezi \u015fekilde incelemek genellikle daha sistematiktir.<\/li>\n<\/ul>\n<p>Bu farklar, \u00f6zellikle \u00e7ok cihazl\u0131 \u00e7al\u0131\u015fma d\u00fczeninde (uzaktan \u00e7al\u0131\u015fma, mobil kullan\u0131m) ve rol bazl\u0131 posta kutular\u0131nda (support@, info@ gibi) belirginle\u015fir.<\/p>\n<h2>Sieve hangi e-posta otomasyon senaryolar\u0131nda i\u015fe yarar?<\/h2>\n<p>Sieve; \u201cdaha az manuel i\u015f, daha d\u00fczenli inbox, daha h\u0131zl\u0131 aksiyon\u201d hedeflerine hizmet eden bir yap\u0131 ta\u015f\u0131d\u0131r. A\u015fa\u011f\u0131daki senaryolar, tipik kurumsal kullan\u0131m \u00f6rnekleridir.<\/p>\n<h3>1) Gelen kutusunu otomatik s\u0131n\u0131fland\u0131rma<\/h3>\n<p>Fatura, s\u00f6zle\u015fme, insan kaynaklar\u0131 veya belirli tedarik\u00e7i e-postalar\u0131 gibi mesajlar\u0131n otomatik olarak ilgili klas\u00f6rlere ta\u015f\u0131nmas\u0131, hem kullan\u0131c\u0131 verimlili\u011fini art\u0131r\u0131r hem de kritik mesajlar\u0131n g\u00f6zden ka\u00e7mas\u0131n\u0131 azalt\u0131r. Buradaki p\u00fcf nokta; konu sat\u0131r\u0131na (Subject) veya g\u00f6nderen ad\u0131na (From) a\u015f\u0131r\u0131 g\u00fcvenmek yerine, daha tutarl\u0131 sinyallerden yararlanmakt\u0131r (\u00f6r. belirli bir g\u00f6nderen adresi, belirli domain, belirli header).<\/p>\n<h3>2) Role-based kutular\u0131n d\u00fczenlenmesi (destek\/sat\u0131\u015f)<\/h3>\n<p>support@ gibi kutularda kategori veya \u00fcr\u00fcn bazl\u0131 ay\u0131rma yap\u0131labilir. \u00d6rne\u011fin belirli anahtar kelimeler ya da belirli al\u0131c\u0131 adreslerine g\u00f6re farkl\u0131 klas\u00f6rlere y\u00f6nlendirme, ekip i\u00e7inde triage s\u00fcresini k\u0131salt\u0131r. Burada hedef \u201ckimin bakaca\u011f\u0131\u201d karar\u0131n\u0131 otomatikle\u015ftirmek de\u011fil; mesaj\u0131 do\u011fru ba\u011flama d\u00fc\u015f\u00fcrerek i\u015f ak\u0131\u015f\u0131n\u0131 h\u0131zland\u0131rmakt\u0131r.<\/p>\n<h3>3) B\u00fcy\u00fck ekleri kontrol etme ve kota y\u00f6netimine destek<\/h3>\n<p>Mail sistemi tasar\u0131m\u0131nda b\u00fcy\u00fck ekler hem kota t\u00fcketimini hem de senkronizasyon y\u00fck\u00fcn\u00fc art\u0131r\u0131r. Sieve ile \u201c\u00e7ok b\u00fcy\u00fck ek i\u00e7eren mesajlar\u0131\u201d ayr\u0131 klas\u00f6re ta\u015f\u0131ma veya i\u015faretleme gibi yakla\u015f\u0131m, kullan\u0131c\u0131lar\u0131 daha kontroll\u00fc bir saklama d\u00fczenine y\u00f6nlendirebilir. Not: Mesaj\u0131 otomatik silmek veya reddetmek, operasyonel ve ileti\u015fimsel risk do\u011furabilir; bu t\u00fcr ad\u0131mlar \u015firket politikas\u0131yla netle\u015ftirilmelidir.<\/p>\n<h3>4) G\u00fcvenlik hijyeni: \u015f\u00fcpheli g\u00f6stergeleri i\u015faretleme<\/h3>\n<p>Sieve, anti-spam\/anti-phishing motorlar\u0131n\u0131n yerini tutmaz; ancak baz\u0131 basit kurumsal hijyen i\u015faretlemelerinde yard\u0131mc\u0131 olabilir. \u00d6rne\u011fin d\u0131\u015f kaynaktan gelen e-postalar\u0131 belirli bir klas\u00f6re ay\u0131rma veya belirli header\u2019lar geldi\u011finde kullan\u0131c\u0131y\u0131 uyaracak \u015fekilde etiketleme gibi uygulamalar d\u00fc\u015f\u00fcn\u00fclebilir. Burada ama\u00e7 \u201cfiltreyi Sieve\u2019e ta\u015f\u0131mak\u201d de\u011fil, mevcut g\u00fcvenlik katmanlar\u0131yla uyumlu bir otomasyon yapmakt\u0131r.<\/p>\n<h2>Sieve kurallar\u0131 hangi veriler \u00fczerinden karar verir?<\/h2>\n<p>Sieve, mesaj\u0131n farkl\u0131 par\u00e7alar\u0131na bakarak ko\u015ful olu\u015fturabilir. Kurumlar\u0131n s\u0131k kulland\u0131\u011f\u0131 kontrol noktalar\u0131 \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>Header\u2019lar:<\/strong> From, To, Cc, Subject gibi standart header\u2019lar; ayr\u0131ca Message-ID, List-ID veya baz\u0131 sistemlerin ekledi\u011fi \u00f6zel header\u2019lar.<\/li>\n<li><strong>Zarf bilgisi (envelope):<\/strong> SMTP seviyesindeki al\u0131c\u0131\/g\u00f6nderen bilgileri. Baz\u0131 durumlarda header\u2019daki From ile zarf g\u00f6ndereni farkl\u0131 olabilir.<\/li>\n<li><strong>Boyut:<\/strong> Mesaj\u0131n toplam boyutu veya belirli e\u015fikler.<\/li>\n<li><strong>Tarih\/saat:<\/strong> Mesaj zaman\u0131na ba\u011fl\u0131 kurallar (her ortam desteklemeyebilir).<\/li>\n<li><strong>\u0130\u00e7erik aramas\u0131:<\/strong> Mesaj g\u00f6vdesinde anahtar kelime arama (dikkatli kullan\u0131lmal\u0131; dil\/encoding\/format farkl\u0131l\u0131klar\u0131, yanl\u0131\u015f pozitif \u00fcretebilir).<\/li>\n<\/ul>\n<p>Kurumsal y\u00f6netimde en s\u00fcrd\u00fcr\u00fclebilir yakla\u015f\u0131m; \u201cde\u011fi\u015fmesi zor\u201d sinyalleri kullanmak ve kural\u0131 olabildi\u011fince basit tutmakt\u0131r. \u00c7ok karma\u015f\u0131k kurallar, ilk kuruldu\u011funda \u00e7al\u0131\u015fsa bile zamanla bak\u0131m maliyetini art\u0131r\u0131r.<\/p>\n<h2>G\u00fcvenlik ve y\u00f6neti\u015fim: Sieve kullan\u0131rken hangi risklere dikkat etmeli?<\/h2>\n<p>Otomasyon, yanl\u0131\u015f tasarlan\u0131rsa veri s\u0131z\u0131nt\u0131s\u0131, mesaj kayb\u0131 veya g\u00f6r\u00fcnmez teslim sorunlar\u0131 yaratabilir. Sieve taraf\u0131nda en s\u0131k kar\u015f\u0131la\u015f\u0131lan risk alanlar\u0131 a\u015fa\u011f\u0131daki gibidir.<\/p>\n<h3>Otomatik iletme (forward) ve veri kontrol\u00fc<\/h3>\n<p>Bir\u00e7ok kurum, d\u0131\u015far\u0131ya otomatik y\u00f6nlendirmeyi k\u0131s\u0131tlar veya denetler. Sunucu tarafl\u0131 bir kural iletme yapabiliyorsa, bu durum veri kayb\u0131 riskini art\u0131rabilir. Politika gere\u011fi otomatik iletmenin s\u0131n\u0131rlanmas\u0131, onaya ba\u011flanmas\u0131 veya sadece belirli hedeflere izin verilmesi tercih edilir.<\/p>\n<h3>Otomatik yan\u0131t (vacation\/auto-reply) d\u00f6ng\u00fcleri<\/h3>\n<p>\u0130ki sistemin birbirine otomatik yan\u0131t vermesi e-posta d\u00f6ng\u00fclerine yol a\u00e7abilir. Sieve\u2019de otomatik yan\u0131tlar kullan\u0131l\u0131yorsa, \u201csadece belirli ko\u015fullarda yan\u0131tla\u201d ve \u201cayn\u0131 ki\u015fiye belirli s\u00fcre i\u00e7inde tek yan\u0131t\u201d gibi s\u0131n\u0131rlamalar \u00f6nemlidir. Ayr\u0131ca mailing list gibi kaynaklara otomatik yan\u0131t g\u00f6nderilmemesi gerekir.<\/p>\n<h3>\u201cGizli\u201d s\u0131n\u0131fland\u0131rma nedeniyle ka\u00e7\u0131r\u0131lan kritik mesajlar<\/h3>\n<p>Kural\u0131n bir mesaj\u0131 fark edilmesi zor bir klas\u00f6re ta\u015f\u0131mas\u0131, kullan\u0131c\u0131n\u0131n \u00f6nemli e-postay\u0131 ka\u00e7\u0131rmas\u0131na neden olabilir. Bu nedenle kritik ak\u0131\u015flar i\u00e7in \u201cta\u015f\u0131ma + i\u015faretleme\u201d veya belirli klas\u00f6rlerin d\u00fczenli kontrol edilmesi gibi s\u00fcre\u00e7ler d\u00fc\u015f\u00fcn\u00fclmelidir.<\/p>\n<h3>Yanl\u0131\u015f pozitifler ve bak\u0131m y\u00fck\u00fc<\/h3>\n<p>Subject \u00fczerinde anahtar kelime aramak gibi k\u0131r\u0131lgan yakla\u015f\u0131mlar, zamanla \u00e7ok hata \u00fcretir. Kurallar\u0131n periyodik g\u00f6zden ge\u00e7irilmesi ve kimlerin de\u011fi\u015ftirebilece\u011finin belirlenmesi gerekir.<\/p>\n<h2>Kurumsal ortamda Sieve tasar\u0131m\u0131: Pratik bir yakla\u015f\u0131m<\/h2>\n<p>Sieve\u2019i etkin kullanmak i\u00e7in \u201cher \u015feyi otomatikle\u015ftirelim\u201d yakla\u015f\u0131m\u0131 yerine, a\u015famal\u0131 ve \u00f6l\u00e7\u00fclebilir bir plan daha iyi sonu\u00e7 verir.<\/p>\n<ol>\n<li><strong>Hedefi tan\u0131mlay\u0131n:<\/strong> Ama\u00e7 inbox s\u0131f\u0131rlamak m\u0131, s\u0131n\u0131fland\u0131rma m\u0131, g\u00fcvenlik i\u015faretleme mi? Her hedef farkl\u0131 kural seti gerektirir.<\/li>\n<li><strong>En kritik 3-5 kural\u0131 se\u00e7in:<\/strong> En \u00e7ok zaman kazand\u0131ran veya en \u00e7ok risk azaltan kurallarla ba\u015flay\u0131n.<\/li>\n<li><strong>Kural \u00e7ak\u0131\u015fmalar\u0131n\u0131 tasarlay\u0131n:<\/strong> Bir mesaj birden fazla ko\u015fula uyuyorsa hangi kural \u00f6nce \u00e7al\u0131\u015facak? \u201c\u0130lk e\u015fle\u015fen kazan\u0131r\u201d mant\u0131\u011f\u0131 baz\u0131 ortamlarda ge\u00e7erlidir.<\/li>\n<li><strong>Geri d\u00f6n\u00fc\u015f plan\u0131 olu\u015fturun:<\/strong> Bir kural sorun \u00e7\u0131kar\u0131rsa h\u0131zl\u0131ca devre d\u0131\u015f\u0131 b\u0131rakma veya eski s\u00fcr\u00fcme d\u00f6nme s\u00fcreci olmal\u0131.<\/li>\n<li><strong>G\u00f6zden ge\u00e7irme takvimi belirleyin:<\/strong> \u00dc\u00e7 ayda bir, alt\u0131 ayda bir kural setini sadele\u015ftirmek uzun vadede b\u00fcy\u00fck fark yarat\u0131r.<\/li>\n<\/ol>\n<h2>Kullan\u0131c\u0131 deneyimi: IT ve ekipler nas\u0131l birlikte \u00e7al\u0131\u015fmal\u0131?<\/h2>\n<p>Sieve kurallar\u0131n\u0131n ba\u015far\u0131l\u0131 olmas\u0131n\u0131n anahtar\u0131, teknik do\u011fruluk kadar operasyonel uyumdur. IT ekibi, kullan\u0131c\u0131lar\u0131n g\u00fcnl\u00fck i\u015f ak\u0131\u015f\u0131n\u0131 anlamadan kural yazarsa; sonu\u00e7 ya a\u015f\u0131r\u0131 agresif filtreleme ya da hi\u00e7 kullan\u0131lmayan bir d\u00fczen olabilir. En iyi pratikler \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>\u015eablonlar olu\u015fturun:<\/strong> Departman bazl\u0131 (finans, sat\u0131\u015f, destek) \u00f6rnek kural setleriyle ba\u015flay\u0131n.<\/li>\n<li><strong>\u0130stisna y\u00f6netimini netle\u015ftirin:<\/strong> Kullan\u0131c\u0131 \u201cbu g\u00f6nderen hep gelen kutusunda kals\u0131n\u201d dedi\u011finde nas\u0131l uygulanacak?<\/li>\n<li><strong>G\u00f6r\u00fcn\u00fcrl\u00fck sa\u011flay\u0131n:<\/strong> Kurallar\u0131n ne yapt\u0131\u011f\u0131n\u0131 kullan\u0131c\u0131ya anlatan k\u0131sa bir rehber, destek taleplerini azalt\u0131r.<\/li>\n<\/ul>\n<h2>Sonu\u00e7: Sieve ile daha tutarl\u0131 mailbox y\u00f6netimi<\/h2>\n<p>Sieve, do\u011fru kullan\u0131ld\u0131\u011f\u0131nda kurumsal e-posta y\u00f6netiminde tutarl\u0131l\u0131k ve s\u00fcrd\u00fcr\u00fclebilir otomasyon sa\u011flar. \u0130stemciye ba\u011f\u0131ml\u0131 kurallar\u0131n yaratt\u0131\u011f\u0131 \u201ccihazdan cihaza de\u011fi\u015fen davran\u0131\u015f\u201d sorununu azalt\u0131r, rol bazl\u0131 posta kutular\u0131nda d\u00fczeni g\u00fc\u00e7lendirir ve belirli g\u00fcvenlik hijyeni ad\u0131mlar\u0131n\u0131 destekleyebilir. Ancak her otomasyon gibi; politika, denetim ve bak\u0131m plan\u0131 olmadan risk \u00fcretme potansiyeli vard\u0131r.<\/p>\n<p>E\u011fer \u015firketinizde posta kutular\u0131n\u0131 daha d\u00fczenli y\u00f6netmek, kullan\u0131c\u0131 kurallar\u0131n\u0131 merkezile\u015ftirmek veya departman bazl\u0131 standartlar olu\u015fturmak istiyorsan\u0131z, kulland\u0131\u011f\u0131n\u0131z e-posta platformunun sunucu tarafl\u0131 filtreleme yakla\u015f\u0131m\u0131n\u0131 ve y\u00f6netim imkanlar\u0131n\u0131 de\u011ferlendirmeniz faydal\u0131 olur. MX1Mail gibi kurumsal e-posta hizmetlerinde de hedef, filtreleme ve mailbox y\u00f6netimini g\u00fcvenli ve \u00f6ng\u00f6r\u00fclebilir bir operasyon haline getirmektir.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sieve filtreleme nedir, istemci kurallar\u0131ndan fark\u0131 ne, hangi senaryolarda tercih edilir ve kurumsal e-posta y\u00f6netiminde nas\u0131l g\u00fcvenli \u015fekilde kullan\u0131l\u0131r?<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[188],"tags":[529,114,531],"class_list":["post-200","post","type-post","status-publish","format-standard","hentry","category-e-posta-yonetimi","tag-e-posta-filtreleme","tag-e-posta-guvenligi","tag-mailbox-yonetimi"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/200","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=200"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/200\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}