{"id":4572,"date":"2026-02-05T22:14:16","date_gmt":"2026-02-05T19:14:16","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/vps-uzerinde-postfix-ve-dovecot-optimizasyonu-ile-yuksek-hacimli-transactional-e-posta\/"},"modified":"2026-02-05T22:14:16","modified_gmt":"2026-02-05T19:14:16","slug":"vps-uzerinde-postfix-ve-dovecot-optimizasyonu-ile-yuksek-hacimli-transactional-e-posta","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/vps-uzerinde-postfix-ve-dovecot-optimizasyonu-ile-yuksek-hacimli-transactional-e-posta\/","title":{"rendered":"VPS \u00dczerinde Postfix ve Dovecot Optimizasyonu ile Y\u00fcksek Hacimli Transactional E\u2011Posta"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Transactional_EPosta_Icin_Postfix_Dovecot_Kombinasyonunu_Dogru_Kurmak\"><span class=\"toc_number toc_depth_1\">1<\/span> Transactional E\u2011Posta \u0130\u00e7in Postfix + Dovecot Kombinasyonunu Do\u011fru Kurmak<\/a><\/li><li><a href=\"#Mimariyi_Dogru_Tanimlamak_Transactional_EPosta_Sunucusundan_Beklentiler\"><span class=\"toc_number toc_depth_1\">2<\/span> Mimariyi Do\u011fru Tan\u0131mlamak: Transactional E\u2011Posta Sunucusundan Beklentiler<\/a><\/li><li><a href=\"#VPS_Kaynak_Planlama_ve_Altyapi_Gereksinimleri\"><span class=\"toc_number toc_depth_1\">3<\/span> VPS Kaynak Planlama ve Altyap\u0131 Gereksinimleri<\/a><ul><li><a href=\"#IP_rDNS_IPv6_ve_Ag_Tarafi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> IP, rDNS, IPv6 ve A\u011f Taraf\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Postfix_Optimizasyonu_Kuyruk_Concurrency_ve_Rate_Limit_Dengesi\"><span class=\"toc_number toc_depth_1\">4<\/span> Postfix Optimizasyonu: Kuyruk, Concurrency ve Rate Limit Dengesi<\/a><ul><li><a href=\"#Temel_Postfix_Parametreleri\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Temel Postfix Parametreleri<\/a><\/li><li><a href=\"#mastercf_ile_Ozel_Outbound_Servisleri\"><span class=\"toc_number toc_depth_2\">4.2<\/span> master.cf ile \u00d6zel Outbound Servisleri<\/a><\/li><li><a href=\"#Ek_Teslim_Edilebilirlik_Ayarlari\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Ek Teslim Edilebilirlik Ayarlar\u0131<\/a><\/li><li><a href=\"#IP_Isitma_ve_Concurrency\"><span class=\"toc_number toc_depth_2\">4.4<\/span> IP Is\u0131tma ve Concurrency<\/a><\/li><\/ul><\/li><li><a href=\"#Dovecot_Optimizasyonu_IMAPPOP_Performansi_ve_Kaynak_Kullanimi\"><span class=\"toc_number toc_depth_1\">5<\/span> Dovecot Optimizasyonu: IMAP\/POP Performans\u0131 ve Kaynak Kullan\u0131m\u0131<\/a><ul><li><a href=\"#Genel_Dovecot_Ayarlari\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Genel Dovecot Ayarlar\u0131<\/a><\/li><li><a href=\"#Indeksler_ve_Performans\"><span class=\"toc_number toc_depth_2\">5.2<\/span> \u0130ndeksler ve Performans<\/a><\/li><li><a href=\"#Guvenlik_ve_Sifreleme\"><span class=\"toc_number toc_depth_2\">5.3<\/span> G\u00fcvenlik ve \u015eifreleme<\/a><\/li><\/ul><\/li><li><a href=\"#Teslim_Edilebilirlik_SPF_DKIM_DMARC_TLS_ve_Politika_Katmani\"><span class=\"toc_number toc_depth_1\">6<\/span> Teslim Edilebilirlik: SPF, DKIM, DMARC, TLS ve Politika Katman\u0131<\/a><ul><li><a href=\"#MTASTS_TLSRPT_ve_Ileri_Seviye_Katmanlar\"><span class=\"toc_number toc_depth_2\">6.1<\/span> MTA\u2011STS, TLS\u2011RPT ve \u0130leri Seviye Katmanlar<\/a><\/li><li><a href=\"#Spam_Klasorunu_Onlemek\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Spam Klas\u00f6r\u00fcn\u00fc \u00d6nlemek<\/a><\/li><\/ul><\/li><li><a href=\"#Izleme_Log_Analizi_ve_Hata_Yonetimi\"><span class=\"toc_number toc_depth_1\">7<\/span> \u0130zleme, Log Analizi ve Hata Y\u00f6netimi<\/a><ul><li><a href=\"#Postfix_Kuyruk_Yonetimi\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Postfix Kuyruk Y\u00f6netimi<\/a><\/li><li><a href=\"#Dovecot_Loglari_ve_Kullanici_Deneyimi\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Dovecot Loglar\u0131 ve Kullan\u0131c\u0131 Deneyimi<\/a><\/li><li><a href=\"#Merkezi_Loglama_ve_Alarm\"><span class=\"toc_number toc_depth_2\">7.3<\/span> Merkezi Loglama ve Alarm<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Tarafinda_Tipik_Bir_Kurulum_Senaryosu\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost Taraf\u0131nda Tipik Bir Kurulum Senaryosu<\/a><\/li><li><a href=\"#Ozet_ve_Sonraki_Adimlar_Transactional_EPostayi_Bir_Urun_Gibi_Yonetin\"><span class=\"toc_number toc_depth_1\">9<\/span> \u00d6zet ve Sonraki Ad\u0131mlar: Transactional E\u2011Postay\u0131 Bir \u00dcr\u00fcn Gibi Y\u00f6netin<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Transactional_EPosta_Icin_Postfix_Dovecot_Kombinasyonunu_Dogru_Kurmak\">Transactional E\u2011Posta \u0130\u00e7in Postfix + Dovecot Kombinasyonunu Do\u011fru Kurmak<\/span><\/h2>\n<p>\u015eifre s\u0131f\u0131rlama linkleri, sipari\u015f onaylar\u0131, fatura bildirimleri, OTP (tek kullan\u0131ml\u0131k \u015fifre) kodlar\u0131\u2026 Bunlar\u0131n hepsi <strong>transactional e\u2011posta<\/strong> kategorisine girer ve i\u015finizin kalbi gibidir. Uygulaman\u0131z sorunsuz \u00e7al\u0131\u015fsa bile bu e\u2011postalar ge\u00e7 gidiyor, spam\u2019e d\u00fc\u015f\u00fcyor veya bazen hi\u00e7 ula\u015fm\u0131yorsa kullan\u0131c\u0131 g\u00f6z\u00fcnde sisteminiz sorunlu g\u00f6r\u00fcn\u00fcr. Y\u00fcksek hacimli transactional e\u2011posta g\u00f6nderen SaaS, e\u2011ticaret veya kurumsal uygulamalarda bu y\u00fczden <strong>kendi Postfix + Dovecot altyap\u0131n\u0131z\u0131<\/strong> <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> \u00fczerinde do\u011fru kurmak ve optimize etmek kritik hale gelir.<\/p>\n<p>Bu yaz\u0131da DCHost ekibi olarak, halihaz\u0131rda mail sunucusu y\u00f6neten veya yeni kuracak geli\u015ftiriciler ve DevOps ekipleri i\u00e7in, <strong>VPS \u00fczerinde Postfix ve Dovecot optimizasyonunu<\/strong> detayl\u0131 \u015fekilde ele alaca\u011f\u0131z. Ama\u00e7; dakikada y\u00fczlerce\u2013binlerce transactional e\u2011postay\u0131 g\u00fcvenli, h\u0131zl\u0131 ve kara listeye d\u00fc\u015fmeden iletebilen, ayn\u0131 zamanda kullan\u0131c\u0131lar\u0131n IMAP\/POP3 \u00fczerinden rahat\u00e7a eri\u015febildi\u011fi, s\u00fcrd\u00fcr\u00fclebilir bir mimari kurmak. Kurulum ad\u0131mlar\u0131ndan \u00e7ok, <strong>ayarlar\u0131n mant\u0131\u011f\u0131n\u0131, kapasite planlamas\u0131n\u0131 ve teslim edilebilirlik<\/strong> taraf\u0131n\u0131 masaya yat\u0131raca\u011f\u0131z.<\/p>\n<h2><span id=\"Mimariyi_Dogru_Tanimlamak_Transactional_EPosta_Sunucusundan_Beklentiler\">Mimariyi Do\u011fru Tan\u0131mlamak: Transactional E\u2011Posta Sunucusundan Beklentiler<\/span><\/h2>\n<p>\u00d6nce ne kurdu\u011fumuzu netle\u015ftirelim. Buradaki hedef, toplu pazarlama (newsletter, kampanya) e\u2011postalar\u0131 de\u011fil; <strong>uygulaman\u0131n tetikledi\u011fi bireysel transactional mesajlar<\/strong>. Bu ayr\u0131m \u00f6nemli, \u00e7\u00fcnk\u00fc:<\/p>\n<ul>\n<li>IP itibar\u0131n\u0131z i\u00e7in transactional ve pazarlama trafi\u011fini m\u00fcmk\u00fcnse <strong>ayr\u0131 IP \/ ayr\u0131 alan ad\u0131<\/strong> \u00fczerinden \u00e7al\u0131\u015ft\u0131rman\u0131z gerekir.<\/li>\n<li>Transactional tarafta <strong>d\u00fc\u015f\u00fck gecikme<\/strong>, <strong>y\u00fcksek teslim oran\u0131<\/strong> ve <strong>tahmin edilebilir hacim<\/strong> bekleriz.<\/li>\n<li>Pazarlama taraf\u0131nda ise a\u00e7\u0131lma oranlar\u0131, abonelikten \u00e7\u0131kma linkleri ve list temizli\u011fi gibi farkl\u0131 kayg\u0131lar bask\u0131nd\u0131r.<\/li>\n<\/ul>\n<p>DCHost ortam\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ba\u015far\u0131l\u0131 mimarilerde genelde \u015fu yap\u0131 tercih ediliyor:<\/p>\n<ul>\n<li>Uygulama (\u00f6rne\u011fin WooCommerce, Laravel, SaaS paneli) bir VPS veya payla\u015f\u0131lm\u0131\u015f hosting \u00fczerinde.<\/li>\n<li>Transactional g\u00f6nderimler i\u00e7in <strong>ayr\u0131 bir VPS \u00fczerinde Postfix (MTA) + Dovecot (IMAP\/POP3)<\/strong> kurulmu\u015f durumda.<\/li>\n<li>Sending alan ad\u0131 genellikle <code>mail.example.com<\/code> ya da <code>notify.example.com<\/code> gibi <strong>ayr\u0131 bir g\u00f6nderim alan ad\u0131<\/strong> oluyor. Bu konuda detayl\u0131 bir perspektif isterseniz <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-icin-ayri-gonderim-alan-adi-kullanmak-transactional-ve-pazarlama-e-postalari-icin-dogru-domain-ve-dns-stratejisi\/\">ayr\u0131 g\u00f6nderim alan ad\u0131 kullanman\u0131n avantajlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> g\u00f6z atabilirsiniz.<\/p>\n<p>Bu yaz\u0131da odak noktam\u0131z: <strong>tek bir g\u00fc\u00e7l\u00fc VPS \u00fczerinde<\/strong> Postfix + Dovecot ikilisini hem performans, hem g\u00fcvenlik, hem de teslim edilebilirlik a\u00e7\u0131s\u0131ndan en mant\u0131kl\u0131 noktaya ta\u015f\u0131mak.<\/p>\n<h2><span id=\"VPS_Kaynak_Planlama_ve_Altyapi_Gereksinimleri\">VPS Kaynak Planlama ve Altyap\u0131 Gereksinimleri<\/span><\/h2>\n<p>Postfix ve Dovecot yaz\u0131l\u0131mlar olarak hafif g\u00f6r\u00fcn\u00fcr; ancak <strong>y\u00fcksek hacimli transactional e\u2011posta<\/strong> s\u00f6z konusu oldu\u011funda as\u0131l bask\u0131 genellikle:<\/p>\n<ul>\n<li>Disk I\/O (queue yazma\/okuma, loglar)<\/li>\n<li>Network throughput (SMTP ba\u011flant\u0131lar\u0131)<\/li>\n<li>CPU (TLS el s\u0131k\u0131\u015fmalar\u0131, spam\/vir\u00fcs filtreleri, DKIM imzalama)<\/li>\n<li>RAM (\u00e7ok say\u0131da e\u015fzamanl\u0131 Postfix\/Dovecot s\u00fcreci)<\/li>\n<\/ul>\n<p>Genel bir k\u0131lavuz olarak (transactional a\u011f\u0131rl\u0131kl\u0131, g\u00fcnde 50\u2013200 bin e\u2011posta band\u0131 i\u00e7in):<\/p>\n<ul>\n<li><strong>CPU:<\/strong> En az 4 vCPU, m\u00fcmk\u00fcnse 8 vCPU ve \u00fczeri.<\/li>\n<li><strong>RAM:<\/strong> Minimum 8 GB, spam filtresi ve DKIM imzalama gibi ek bile\u015fenlerle 16 GB daha konforlu.<\/li>\n<li><strong>Disk:<\/strong> NVMe SSD ve d\u00fc\u015f\u00fck latency \u00e7ok fark yarat\u0131r. Queue ve log\u2019lar i\u00e7in h\u0131zl\u0131 disk \u015fart.<\/li>\n<li><strong>A\u011f:<\/strong> En az 100 Mbps simetrik ba\u011flant\u0131; burst anlar\u0131nda 1 Gbps aray\u00fcz avantajl\u0131d\u0131r.<\/li>\n<\/ul>\n<p>VPS boyutland\u0131rmas\u0131 konusunda daha detayl\u0131 perspektif i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-blog-woocommerce-ve-saas-icin-kac-cpu-ne-kadar-ram\/\">WordPress, WooCommerce ve SaaS i\u00e7in CPU\/RAM planlama rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z temel prensipler, mail sunucusu i\u00e7in de b\u00fcy\u00fck oranda ge\u00e7erli.<\/p>\n<h3><span id=\"IP_rDNS_IPv6_ve_Ag_Tarafi\">IP, rDNS, IPv6 ve A\u011f Taraf\u0131<\/span><\/h3>\n<p>Y\u00fcksek hacimli transactional e\u2011postada <strong>IP itibar\u0131<\/strong> her \u015feydir. Temel gereksinimler:<\/p>\n<ul>\n<li><strong>Dedicated IPv4:<\/strong> IP\u2019nizi ba\u015fka kimseyle payla\u015fmamak, kara liste problemlerini y\u00f6netilebilir k\u0131lar.<\/li>\n<li><strong>Do\u011fru PTR (Reverse DNS):<\/strong> IP\u2019nizin PTR kayd\u0131 <code>mail.example.com<\/code> gibi FQDN ile e\u015fle\u015fmeli. Ayr\u0131nt\u0131lar i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/ptr-reverse-dns-kaydi-vps-ipniz-icin-dogru-ayar-ve-e-posta-teslimine-etkisi\/\">PTR (reverse DNS) ayarlar\u0131n\u0131 ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z yaz\u0131ya<\/a> bakabilirsiniz.<\/li>\n<li><strong>IPv6:<\/strong> B\u00fcy\u00fck sa\u011flay\u0131c\u0131lar IPv6 ile gelen mailleri de kabul ediyor. IPv6\u2019y\u0131 devreye al\u0131rken SPF, rDNS ve kara liste takibini de d\u00fc\u015f\u00fcnmek gerekir. Bu konuda <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-ile-e-posta-gonderimi-reverse-dns-spf-ve-teslim-edilebilirlik-rehberi\/\">IPv6 ile e\u2011posta g\u00f6nderimi rehberimiz<\/a> pratik bir yol haritas\u0131 sunuyor.<\/li>\n<\/ul>\n<p>Ayr\u0131ca, DCHost taraf\u0131nda sizin i\u00e7in tan\u0131mlanan \u00e7\u0131k\u0131\u015f rate limit\u2019lerini ve SMTP port politikalar\u0131n\u0131 da bilmeniz \u00f6nemli. A\u011f katman\u0131ndaki k\u0131s\u0131tlar ile Postfix taraf\u0131ndaki limitler <strong>uyumlu<\/strong> olmal\u0131.<\/p>\n<h2><span id=\"Postfix_Optimizasyonu_Kuyruk_Concurrency_ve_Rate_Limit_Dengesi\">Postfix Optimizasyonu: Kuyruk, Concurrency ve Rate Limit Dengesi<\/span><\/h2>\n<p>Postfix\u2019in g\u00fczelli\u011fi, neredeyse her davran\u0131\u015f\u0131n birka\u00e7 sat\u0131rl\u0131k ayarla ince ayar yap\u0131labilmesi. Dezavantaj\u0131 ise, yanl\u0131\u015f kombinasyonlar\u0131n <strong>hem sunucuyu yorabilmesi, hem de b\u00fcy\u00fck sa\u011flay\u0131c\u0131lar\u0131n oran limitlerine tak\u0131lman\u0131za<\/strong> neden olabilmesi.<\/p>\n<h3><span id=\"Temel_Postfix_Parametreleri\">Temel Postfix Parametreleri<\/span><\/h3>\n<p><code>\/etc\/postfix\/main.cf<\/code> i\u00e7inde transactional bir MTA i\u00e7in kritik olan baz\u0131 ayarlar:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">maximal_queue_lifetime = 2d\nbounce_queue_lifetime  = 1d\nmaximal_backoff_time   = 1h\nminimal_backoff_time   = 5m\nqueue_run_delay        = 5m\n\ndefault_process_limit              = 200\nsmtpd_client_connection_count_limit = 20\nsmtpd_client_connection_rate_limit  = 60\nanvil_rate_time_unit               = 60s\n\nsmtp_connect_timeout   = 30s\nsmtp_helo_timeout      = 15s\nsmtp_tcp_read_timeout  = 30s\nsmtp_tcp_write_timeout = 30s\n<\/code><\/pre>\n<ul>\n<li><strong>maximal_queue_lifetime:<\/strong> Ula\u015f\u0131lamayan mailleri sonsuza kadar ta\u015f\u0131may\u0131n. Transactional i\u00e7in 2 g\u00fcn \u00e7o\u011fu senaryoda yeterli.<\/li>\n<li><strong>default_process_limit:<\/strong> Postfix\u2019in ayn\u0131 anda ka\u00e7 s\u00fcre\u00e7 a\u00e7abilece\u011fini belirler. CPU ve RAM\u2019inizi a\u015fmayacak, ama SMTP taraf\u0131nda kuyru\u011fu kilitlemeyecek bir de\u011fer verin.<\/li>\n<li><strong>smtpd_client_connection_*<\/strong> parametreleri ile tek IP\u2019den gelen sald\u0131rgan ba\u011flant\u0131lar\u0131 s\u0131n\u0131rlayabilirsiniz.<\/li>\n<\/ul>\n<p>SMTP rate limit ve outbound g\u00fcvenlik taraf\u0131n\u0131 daha geni\u015f ba\u011flamda ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/paylasimli-hosting-ve-vpste-outbound-e-posta-guvenligi-ve-smtp-rate-limit-yonetimi\/\">SMTP rate limit y\u00f6netimi rehberimiz<\/a>, bu ayarlar\u0131 tasarlarken size iyi bir \u00e7er\u00e7eve sunacakt\u0131r.<\/p>\n<h3><span id=\"mastercf_ile_Ozel_Outbound_Servisleri\">master.cf ile \u00d6zel Outbound Servisleri<\/span><\/h3>\n<p>Y\u00fcksek hacimde, \u00f6zellikle de uygulama taraf\u0131nda \u00e7ok say\u0131da e\u015fzamanl\u0131 SMTP \u00e7a\u011fr\u0131s\u0131 \u00fcretildi\u011finde, <code>master.cf<\/code> \u00fczerinden <strong>\u00f6zelle\u015ftirilmi\u015f g\u00f6nderim kanallar\u0131<\/strong> tan\u0131mlamak verimlidir. \u00d6rne\u011fin transactional trafi\u011fi ayr\u0131 bir servisle y\u00f6netebilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">txn-smtp unix -      -       n       -       50      smtp\n  -o syslog_name=postfix\/txn-smtp\n  -o smtp_connection_cache_on_demand=no\n  -o smtp_connection_cache_destinations=\n  -o smtp_dns_support_level=dnssec\n<\/code><\/pre>\n<p>Uygulaman\u0131z\u0131n SMTP ayarlar\u0131na <code>127.0.0.1:2525<\/code> gibi bir port verip, master.cf\u2019de bu porta ba\u011flanan \u00f6zel bir <code>txn-smtp<\/code> servisi tan\u0131mlayarak <strong>farkl\u0131 oran limitleri ve log ayr\u0131m\u0131<\/strong> sa\u011flayabilirsiniz.<\/p>\n<h3><span id=\"Ek_Teslim_Edilebilirlik_Ayarlari\">Ek Teslim Edilebilirlik Ayarlar\u0131<\/span><\/h3>\n<p>Transactional bir MTA\u2019da a\u015fa\u011f\u0131daki ayarlar da \u00f6nemlidir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">smtp_tls_security_level        = may\nsmtp_tls_loglevel             = 1\nsmtpd_tls_security_level      = may\n\n# Bozuk HELO'lara daha toleransl\u0131 ama kontroll\u00fc yakla\u015f\u0131m\nsmtpd_helo_required           = yes\nsmtpd_helo_restrictions = \n  permit_mynetworks, \n  reject_invalid_helo_hostname, \n  reject_non_fqdn_helo_hostname, \n  permit\n\n# Geri d\u00f6n\u00fc\u015f adresleri\nlocal_header_rewrite_clients = static:all\n<\/code><\/pre>\n<p><strong>HELO\/EHLO<\/strong> kimli\u011fi, <strong>rDNS ile tutarl\u0131<\/strong> olmal\u0131. \u00d6rne\u011fin IP\u2019nizin PTR kayd\u0131 <code>mail.example.com<\/code> ise, <code>smtpd_banner<\/code> ve <code>myhostname<\/code> de bununla uyumlu olmal\u0131d\u0131r.<\/p>\n<h3><span id=\"IP_Isitma_ve_Concurrency\">IP Is\u0131tma ve Concurrency<\/span><\/h3>\n<p>Yeni bir IP\u2019yi bir anda g\u00fcnde on binlerce maile bo\u011fmak, kara liste riskini dramatik bi\u00e7imde art\u0131r\u0131r. DCHost taraf\u0131nda pek \u00e7ok m\u00fc\u015fterimizin kulland\u0131\u011f\u0131 yakla\u015f\u0131m:<\/p>\n<ul>\n<li>\u0130lk hafta g\u00fcnde birka\u00e7 bin transactional e\u2011posta ile ba\u015flamak.<\/li>\n<li>B\u00fcy\u00fck sa\u011flay\u0131c\u0131lar\u0131n (Gmail, Outlook vb.) geri d\u00f6n\u00fc\u015flerine g\u00f6re concurrency de\u011ferlerini yava\u015f yava\u015f art\u0131rmak.<\/li>\n<li>Hard bounce oran\u0131 ve rate limit hatalar\u0131n\u0131 izleyerek \u00fcst s\u0131n\u0131r\u0131 belirlemek.<\/li>\n<\/ul>\n<p>IP \u0131s\u0131tma s\u00fcre\u00e7lerini, Postfix taraf\u0131ndaki concurrency ve limit ayarlar\u0131yla birlikte ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/\">dedicated IP \u0131s\u0131tma ve e\u2011posta itibar\u0131 rehberimiz<\/a> bu mimarinin zorunlu okumas\u0131 niteli\u011finde.<\/p>\n<h2><span id=\"Dovecot_Optimizasyonu_IMAPPOP_Performansi_ve_Kaynak_Kullanimi\">Dovecot Optimizasyonu: IMAP\/POP Performans\u0131 ve Kaynak Kullan\u0131m\u0131<\/span><\/h2>\n<p>Transactional e\u2011posta altyap\u0131s\u0131nda Dovecot genellikle \u201carkaplan oyuncu\u201d gibi g\u00f6r\u00fcn\u00fcr ama:<\/p>\n<ul>\n<li>Gelen kutular\u0131n\u0131 (support@, billing@ vb.) onlarca ki\u015fi ayn\u0131 anda kullan\u0131yorsa,<\/li>\n<li>Uygulama loglar\u0131yla mail ar\u015fivlerini uzun s\u00fcre tutuyorsan\u0131z,<\/li>\n<li>POP3\/IMAP ba\u011flant\u0131 say\u0131n\u0131z y\u00fcksekse,<\/li>\n<\/ul>\n<p>Dovecot\u2019un da do\u011fru ayarlarla optimize edilmesi gerekir.<\/p>\n<h3><span id=\"Genel_Dovecot_Ayarlari\">Genel Dovecot Ayarlar\u0131<\/span><\/h3>\n<p><code>\/etc\/dovecot\/dovecot.conf<\/code> veya ilgili include dosyalar\u0131nda kontrol etmeniz gereken baz\u0131 temel ayarlar:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">protocols = imap pop3 lmtp\n\nmail_location = maildir:~\/Maildir\n\nservice imap-login {\n  inet_listener imap {\n    port = 143\n  }\n  inet_listener imaps {\n    port = 993\n    ssl = yes\n  }\n  process_min_avail = 5\n  service_count = 0\n  vsz_limit = 512M\n}\n\nservice imap {\n  process_limit = 256\n}\n\nservice auth {\n  unix_listener \/var\/spool\/postfix\/private\/auth {\n    mode = 0660\n    user = postfix\n    group = postfix\n  }\n}\n<\/code><\/pre>\n<ul>\n<li><strong>mail_location:<\/strong> Y\u00fcksek hacimli ve \u00e7ok klas\u00f6rl\u00fc yap\u0131larda <strong>Maildir<\/strong> format\u0131, e\u015fzamanl\u0131 eri\u015fim ve yedekleme i\u00e7in mbox\u2019a g\u00f6re \u00e7ok daha esnek.<\/li>\n<li><strong>process_limit:<\/strong> IMAP trafi\u011fi y\u00fcksekse bu de\u011feri CPU \u00e7ekirde\u011fi say\u0131n\u0131za g\u00f6re \u00f6l\u00e7ekleyin.<\/li>\n<li><strong>vsz_limit:<\/strong> Dovecot s\u00fcre\u00e7lerinin haf\u0131zay\u0131 \u015fi\u015firmesini engeller; ger\u00e7ek t\u00fcketimi izleyerek ayarlay\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Indeksler_ve_Performans\">\u0130ndeksler ve Performans<\/span><\/h3>\n<p>Dovecot\u2019un g\u00fc\u00e7l\u00fc taraflar\u0131ndan biri, mailler i\u00e7in <strong>ak\u0131ll\u0131 indeksleme<\/strong> yetenekleri. \u00d6zellikle \u201ct\u00fcm klas\u00f6rde ara\u201d gibi i\u015flemler yapan kullan\u0131c\u0131lar\u0131n\u0131z varsa indeksler fark yarat\u0131r. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">mail_plugins = $mail_plugins imap_quota\nmail_indexer_worker_max_open_files = 1000\n<\/code><\/pre>\n<p>Disk I\/O taraf\u0131nda sorun ya\u015f\u0131yorsan\u0131z, <strong>SSD\/NVMe disk<\/strong> ve yeterli inode planlamas\u0131 yapt\u0131\u011f\u0131n\u0131zdan emin olun. Storage taraf\u0131nda daha geni\u015f bak\u0131\u015f a\u00e7\u0131s\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-ve-buyuk-wordpress-siteleri-icin-disk-iops-ve-inode-planlama-rehberi\/\">disk, IOPS ve inode planlama rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z prensipler ayn\u0131 \u015fekilde mail depolamada da ge\u00e7erli.<\/p>\n<h3><span id=\"Guvenlik_ve_Sifreleme\">G\u00fcvenlik ve \u015eifreleme<\/span><\/h3>\n<p>Transactional mailleriniz \u00e7o\u011fu zaman ki\u015fisel veri veya finansal bilgi i\u00e7erir. Bu y\u00fczden Dovecot taraf\u0131nda:<\/p>\n<ul>\n<li><strong>IMAPS (993\/TLS) ve POP3S (995\/TLS)<\/strong> kullanmay\u0131 zorunlu hale getirin.<\/li>\n<li><code>ssl_min_protocol = TLSv1.2<\/code> ve modern \u015fifre k\u00fcmeleri ile eski, zay\u0131f protokolleri kapat\u0131n.<\/li>\n<li>Y\u00f6netim panelleri ve kritik hesaplar i\u00e7in IP k\u0131s\u0131tlama + 2FA uygulamalar\u0131n\u0131 ek bir katman olarak d\u00fc\u015f\u00fcn\u00fcn.<\/li>\n<\/ul>\n<h2><span id=\"Teslim_Edilebilirlik_SPF_DKIM_DMARC_TLS_ve_Politika_Katmani\">Teslim Edilebilirlik: SPF, DKIM, DMARC, TLS ve Politika Katman\u0131<\/span><\/h2>\n<p>Postfix ve Dovecot\u2019u ne kadar iyi optimize ederseniz edin, DNS ve e\u2011posta do\u011frulama kay\u0131tlar\u0131n\u0131z eksikse teslim edilebilirlik duvara toslar. Minimumda a\u015fa\u011f\u0131dakiler eksiksiz olmal\u0131:<\/p>\n<ul>\n<li><strong>SPF:<\/strong> Hangi sunucular\u0131n alan ad\u0131n\u0131z ad\u0131na mail g\u00f6ndermeye yetkili oldu\u011funu tan\u0131mlar.<\/li>\n<li><strong>DKIM:<\/strong> G\u00f6nderilen mailleri kriptografik olarak imzalar, i\u00e7erik b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc garanti eder.<\/li>\n<li><strong>DMARC:<\/strong> SPF\/DKIM sonu\u00e7lar\u0131na g\u00f6re al\u0131c\u0131ya nas\u0131l davranaca\u011f\u0131n\u0131 (karantinaya al, reddet vb.) s\u00f6yler.<\/li>\n<\/ul>\n<p>Bu \u00fc\u00e7l\u00fc kombinasyonu s\u0131f\u0131rdan kurmak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM ve DMARC rehberimiz<\/a> ad\u0131m ad\u0131m ilerlemenize yard\u0131mc\u0131 olur. Transactional e\u2011posta \u00f6zelinde \u00f6nerimiz:<\/p>\n<ul>\n<li>Transactional alan ad\u0131n\u0131zda SPF kayd\u0131n\u0131 m\u00fcmk\u00fcn oldu\u011funca sade tutun.<\/li>\n<li>DKIM anahtar uzunlu\u011funu en az 2048 bit kullan\u0131n.<\/li>\n<li>DMARC\u2019\u0131 \u00f6nce <code>p=none<\/code> ile ba\u015flat\u0131p raporlar\u0131 analiz edin, sonra kademeli olarak <code>quarantine<\/code> ve <code>reject<\/code> a\u015famas\u0131na ge\u00e7in.<\/li>\n<\/ul>\n<h3><span id=\"MTASTS_TLSRPT_ve_Ileri_Seviye_Katmanlar\">MTA\u2011STS, TLS\u2011RPT ve \u0130leri Seviye Katmanlar<\/span><\/h3>\n<p>B\u00fcy\u00fck sa\u011flay\u0131c\u0131larla g\u00fcvenli SMTP trafi\u011fi kurmak i\u00e7in:<\/p>\n<ul>\n<li><strong>MTA\u2011STS:<\/strong> Alan ad\u0131n\u0131z i\u00e7in TLS zorunlulu\u011fu ve kabul edilebilir MX\u2019leri tan\u0131mlar.<\/li>\n<li><strong>TLS\u2011RPT:<\/strong> \u015eifreli SMTP ba\u011flant\u0131 raporlar\u0131n\u0131 alman\u0131z\u0131 sa\u011flar.<\/li>\n<li><strong>BIMI:<\/strong> Marka logonuzun gelen kutusunda g\u00f6r\u00fcnmesini sa\u011flayan yeni bir standartt\u0131r (DMARC ile s\u0131k\u0131 ba\u011fl\u0131).<\/li>\n<\/ul>\n<p>Bu geli\u015fmi\u015f DNS kay\u0131tlar\u0131 i\u00e7in ad\u0131m ad\u0131m \u00f6rnekler g\u00f6rmek isterseniz <a href=\"https:\/\/www.dchost.com\/blog\/mta-sts-tls-rpt-ve-bimi-nedir-e-posta-guvenligi-ve-marka-gorunurlugu-icin-gelismis-dns-ayarlari\/\">MTA\u2011STS, TLS\u2011RPT ve BIMI rehberimiz<\/a> iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/p>\n<h3><span id=\"Spam_Klasorunu_Onlemek\">Spam Klas\u00f6r\u00fcn\u00fc \u00d6nlemek<\/span><\/h3>\n<p>Transactional maillerin spam klas\u00f6r\u00fcne d\u00fc\u015fmesi genellikle \u00fc\u00e7 ana ba\u015fl\u0131\u011fa dayan\u0131r:<\/p>\n<ul>\n<li><strong>\u0130tibar:<\/strong> IP\/alan ad\u0131 kara listeleri, y\u00fcksek bounce oran\u0131, spam \u015fikayetleri.<\/li>\n<li><strong>\u0130\u00e7erik:<\/strong> Konu sat\u0131rlar\u0131, link yap\u0131lar\u0131, HTML\/Text oran\u0131.<\/li>\n<li><strong>Teknik:<\/strong> SPF\/DKIM\/DMARC hatalar\u0131, reverse DNS eksikleri, zay\u0131f TLS.<\/li>\n<\/ul>\n<p>Bu ba\u015fl\u0131klar\u0131n her birini pratik kontrol listeleriyle ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/e-postalar-neden-spam-klasorune-dusuyor-paylasimli-hosting-ve-vps-icin-teslim-edilebilirlik-kontrol-listesi\/\">e\u2011postalar neden spam\u2019e d\u00fc\u015f\u00fcyor rehberimiz<\/a>, Postfix + Dovecot altyap\u0131n\u0131z\u0131 canl\u0131ya al\u0131rken yan\u0131n\u0131zda durmas\u0131 gereken bir dok\u00fcman gibi d\u00fc\u015f\u00fcn\u00fclebilir.<\/p>\n<h2><span id=\"Izleme_Log_Analizi_ve_Hata_Yonetimi\">\u0130zleme, Log Analizi ve Hata Y\u00f6netimi<\/span><\/h2>\n<p>\u0130yi optimize edilmi\u015f bir transactional mail sunucusunun ortak \u00f6zelli\u011fi: <strong>log\u2019lar\u0131n ciddiye al\u0131nmas\u0131<\/strong>. Postfix ve Dovecot\u2019un yazd\u0131\u011f\u0131 g\u00fcnl\u00fckler; kapasite limitleri, spam\/abuse giri\u015fimleri ve ISP rate limit\u2019leri hakk\u0131nda olduk\u00e7a zengin sinyaller i\u00e7erir.<\/p>\n<h3><span id=\"Postfix_Kuyruk_Yonetimi\">Postfix Kuyruk Y\u00f6netimi<\/span><\/h3>\n<p>G\u00fcnl\u00fck operasyonlarda en \u00e7ok kullanaca\u011f\u0131n\u0131z komutlar:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">postqueue -p          # Kuyru\u011fu listele\npostsuper -d QUEUEID  # Belirli bir maili sil\npostcat -q QUEUEID    # Kuyruktaki mailin i\u00e7eri\u011fini g\u00f6ster\n<\/code><\/pre>\n<p>Kuyrukta birikme g\u00f6r\u00fcyorsan\u0131z dikkat etmeniz gerekenler:<\/p>\n<ul>\n<li>Destination baz\u0131nda m\u0131 (\u00f6rne\u011fin sadece belirli b\u00fcy\u00fck sa\u011flay\u0131c\u0131lara gidenler), yoksa genel bir t\u0131kan\u0131kl\u0131k m\u0131 var?<\/li>\n<li>Loglarda <code>deferred<\/code> say\u0131s\u0131 nas\u0131l art\u0131yor? Hangi hata kodlar\u0131 \u00f6ne \u00e7\u0131k\u0131yor?<\/li>\n<li>Sunucu kaynaklar\u0131 (CPU, RAM, disk I\/O) tavan yapm\u0131\u015f m\u0131?<\/li>\n<\/ul>\n<p>SMTP hata kodlar\u0131n\u0131 anlamak, burada do\u011fru te\u015fhis i\u00e7in \u00e7ok \u00f6nemli. <a href=\"https:\/\/www.dchost.com\/blog\/smtp-hata-kodlari-ve-bounce-mesajlari-rehberi\/\">SMTP hata kodlar\u0131 ve bounce mesajlar\u0131 rehberimiz<\/a>, 4xx\/5xx hatalar\u0131n\u0131n ne anlama geldi\u011fini h\u0131zla yorumlaman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<h3><span id=\"Dovecot_Loglari_ve_Kullanici_Deneyimi\">Dovecot Loglar\u0131 ve Kullan\u0131c\u0131 Deneyimi<\/span><\/h3>\n<p>Dovecot taraf\u0131nda en s\u0131k kar\u015f\u0131la\u015f\u0131lan problemler genelde:<\/p>\n<ul>\n<li>Parola\/kimlik do\u011frulama hatalar\u0131 (yanl\u0131\u015f kullan\u0131c\u0131 ad\u0131, brute force denemeleri)<\/li>\n<li>Disk kotas\u0131 doldu\u011fu i\u00e7in mail kabul edilememesi<\/li>\n<li>IMAP klas\u00f6r senkronizasyon sorunlar\u0131<\/li>\n<\/ul>\n<p>Dovecot loglar\u0131n\u0131 g\u00fcnl\u00fck olarak tarayarak:<\/p>\n<ul>\n<li>Hangi IP\u2019lerden yo\u011fun ba\u015far\u0131s\u0131z login denemeleri geldi\u011fini,<\/li>\n<li>Hangi hesaplar\u0131n kota limitine dayand\u0131\u011f\u0131n\u0131,<\/li>\n<li>Hangi istemci t\u00fcrlerinin (Outlook, mobil, webmail) daha \u00e7ok sorun \u00fcretti\u011fini<\/li>\n<\/ul>\n<p>g\u00f6rebilir, buna g\u00f6re firewall, fail2ban ve kota politikalar\u0131n\u0131z\u0131 g\u00fcncelleyebilirsiniz.<\/p>\n<h3><span id=\"Merkezi_Loglama_ve_Alarm\">Merkezi Loglama ve Alarm<\/span><\/h3>\n<p>G\u00fcnde on binlerce transactional e\u2011posta \u00fcreten bir sistemde \u201cloglara bakmak\u201d manuel bir i\u015f olmamal\u0131. Loglar\u0131 merkezi bir sisteme (\u00f6rne\u011fin Loki, ELK) g\u00f6nderip; belirli oranlar\u0131n \u00fczerine \u00e7\u0131kan:<\/p>\n<ul>\n<li>4xx\/5xx SMTP hatalar\u0131,<\/li>\n<li>Hard bounce oranlar\u0131,<\/li>\n<li>Brute force denemeleri,<\/li>\n<\/ul>\n<p>i\u00e7in uyar\u0131 kurallar\u0131 yazmak, olas\u0131 itibar problemlerini daha b\u00fcy\u00fcmeden yakalaman\u0131z\u0131 sa\u011flar. Bunun i\u00e7in genel bir yakla\u015f\u0131m\u0131 <a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi-loglama-tutma-sureleri-ve-alarm-kurallari\/\">VPS log y\u00f6netimi<\/a> rehberimizde detayl\u0131 anlatt\u0131k.<\/p>\n<h2><span id=\"DCHost_Tarafinda_Tipik_Bir_Kurulum_Senaryosu\">DCHost Taraf\u0131nda Tipik Bir Kurulum Senaryosu<\/span><\/h2>\n<p>DCHost olarak transactional e\u2011posta altyap\u0131s\u0131n\u0131 kendi VPS\u2019ine ta\u015f\u0131mak isteyen pek \u00e7ok m\u00fc\u015fteri ile \u00e7al\u0131\u015f\u0131rken, genelde \u015fu ak\u0131\u015fla ilerliyoruz:<\/p>\n<ol>\n<li>\u0130htiya\u00e7 analizi: G\u00fcnl\u00fck\/ayl\u0131k beklenen e\u2011posta hacmi, hedeflenen teslim s\u00fcresi, transactional\/pazarlama ayr\u0131m\u0131.<\/li>\n<li>Uygun VPS se\u00e7imi: CPU, RAM, disk ve a\u011f taraf\u0131nda yeterli ba\u015f bo\u015fluk (headroom) b\u0131rakmak.<\/li>\n<li>Postfix + Dovecot + opsiyonel spam filtresi (\u00f6rne\u011fin rspamd) temel kurulumu. Temel ad\u0131mlar i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/vpste-e-posta-sunucusu-kurulumu-postfix-dovecot-rspamd-ile-teslim-edilebilirlik-ve-ip-isitma-adim-adim\/\">VPS\u2019te Postfix + Dovecot kurulum rehberimiz<\/a> iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/li>\n<li>SPF, DKIM, DMARC, rDNS, MTA\u2011STS gibi DNS taraf\u0131 kay\u0131tlar\u0131n eksiksiz tan\u0131mlanmas\u0131.<\/li>\n<li>IP \u0131s\u0131tma plan\u0131: \u0130lk haftalar i\u00e7in g\u00f6nderim kademeleri ve log tabanl\u0131 itibar takibi.<\/li>\n<li>Uygulama entegrasyonu: Laravel, WooCommerce, SaaS panelinizin SMTP ayarlar\u0131n\u0131 bu yeni altyap\u0131ya y\u00f6nlendirme.<\/li>\n<\/ol>\n<p>Bu ad\u0131mlar tamamland\u0131ktan sonra, birka\u00e7 hafta boyunca log ve metriklere bakarak Postfix concurrency, rate limit ve Dovecot s\u00fcre\u00e7 limitlerini ince ayarlarla oturttu\u011fumuzda, genellikle <strong>stabil, tahmin edilebilir ve y\u00fcksek teslim oranl\u0131<\/strong> bir transactional mail altyap\u0131s\u0131 elde ediyoruz.<\/p>\n<h2><span id=\"Ozet_ve_Sonraki_Adimlar_Transactional_EPostayi_Bir_Urun_Gibi_Yonetin\">\u00d6zet ve Sonraki Ad\u0131mlar: Transactional E\u2011Postay\u0131 Bir \u00dcr\u00fcn Gibi Y\u00f6netin<\/span><\/h2>\n<p>Transactional e\u2011posta \u00e7o\u011fu projede \u201cnas\u0131l olsa g\u00f6nderiliyor\u201d diye d\u00fc\u015f\u00fcn\u00fclen, ancak sorun \u00e7\u0131kt\u0131\u011f\u0131nda herkesi aya\u011fa kald\u0131ran kritik bir bile\u015fen. VPS \u00fczerinde Postfix ve Dovecot ile \u00e7al\u0131\u015fmak size <strong>tam kontrol ve maliyet avantaj\u0131<\/strong> sa\u011flarken, ayn\u0131 zamanda <strong>y\u00fcksek sorumluluk<\/strong> da getiriyor: IP itibar\u0131n\u0131 korumak, DNS kay\u0131tlar\u0131n\u0131 g\u00fcncel tutmak, limitleri do\u011fru ayarlamak ve loglar\u0131 izlemek.<\/p>\n<p>Bu yaz\u0131da Postfix kuyru\u011fundan concurrency ayarlar\u0131na, Dovecot oturum y\u00f6netiminden SPF\/DKIM\/DMARC ve MTA\u2011STS gibi teslim edilebilirlik katmanlar\u0131na kadar <strong>y\u00fcksek hacimli transactional e\u2011posta<\/strong> i\u00e7in ihtiya\u00e7 duyaca\u011f\u0131n\u0131z temel optimizasyonlar\u0131 \u00f6zetledik. Bir sonraki ad\u0131m, kendi ortam\u0131n\u0131zda ger\u00e7ek metriklere bakarak (g\u00fcnl\u00fck hacim, hata oranlar\u0131, gecikme s\u00fcreleri) bu ayarlar\u0131 <strong>sisteminize \u00f6zel<\/strong> hale getirmek.<\/p>\n<p>Kendi transactional e\u2011posta altyap\u0131n\u0131z\u0131 kurmak veya mevcut Postfix + Dovecot VPS\u2019inizi g\u00f6zden ge\u00e7irmek istiyorsan\u0131z, DCHost \u00fczerinde <strong>e\u2011posta odakl\u0131 VPS<\/strong> yap\u0131land\u0131rmalar\u0131m\u0131zla, hem kapasite planlama hem de teslim edilebilirlik optimizasyonu taraf\u0131nda size yard\u0131mc\u0131 olabiliriz. Projenizin hacmini, hedef kitlenizi ve reg\u00fclasyon gereksinimlerinizi birlikte de\u011ferlendirip <strong>\u00f6l\u00e7eklenebilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir<\/strong> bir transactional e\u2011posta mimarisi \u00e7\u0131karabiliriz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Transactional E\u2011Posta \u0130\u00e7in Postfix + Dovecot Kombinasyonunu Do\u011fru Kurmak2 Mimariyi Do\u011fru Tan\u0131mlamak: Transactional E\u2011Posta Sunucusundan Beklentiler3 VPS Kaynak Planlama ve Altyap\u0131 Gereksinimleri3.1 IP, rDNS, IPv6 ve A\u011f Taraf\u01314 Postfix Optimizasyonu: Kuyruk, Concurrency ve Rate Limit Dengesi4.1 Temel Postfix Parametreleri4.2 master.cf ile \u00d6zel Outbound Servisleri4.3 Ek Teslim Edilebilirlik Ayarlar\u01314.4 IP Is\u0131tma ve Concurrency5 Dovecot Optimizasyonu: [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4573,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4572","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=4572"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4572\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4573"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4572"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4572"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}