Ja uzturi vietni, tu parasti pie\u0146em, ka e-pasts vienk\u0101r\u0161i str\u0101d\u0101: kontaktformas iesniegumi iekr\u012bt inbox, klients sa\u0146em pas\u016bt\u012bjuma apstiprin\u0101jumu, un paroles atiestates saites pien\u0101k laik\u0101. Br\u012bd\u012b, kad tas nenotiek, t\u0101 vairs nav \u201cs\u012bka ne\u0113rt\u012bba\u201d – tas ir uztic\u012bbas kritums, kas maks\u0101 l\u012bdus, klientus un reput\u0101ciju.<\/p>\n\n\n\n
\u013boti bie\u017ei klusais iemesls aiz paz\u016bdo\u0161iem e-pastiem ir vietnes noklus\u0113juma pasta konfigur\u0101cija. Daudzas vietnes (\u012bpa\u0161i WordPress) e-pastu s\u016bta veid\u0101, kas Gmail, Outlook un citiem m\u016bsdienu pastkast\u012b\u0161u nodro\u0161in\u0101t\u0101jiem izskat\u0101s aizdom\u012bgi un atg\u0101dina spamu.<\/p>\n\n\n\n
Praktiskais risin\u0101jums ir apiet \u0161o \u201csal\u016bzu\u0161o\u201d modeli un s\u016bt\u012bt vietnes e-pastus caur profesion\u0101lu, autentific\u0113tu kan\u0101lu, izmantojot SMTP – Simple Mail Transfer Protocol<\/strong> (vienk\u0101r\u0161ais pasta p\u0101rs\u016bt\u012b\u0161anas protokols). Un te par\u0101d\u0101s tehniski vienk\u0101r\u0161s, bet kritiski svar\u012bgs jaut\u0101jums: kuru SMTP portu 2026. gad\u0101 izv\u0113l\u0113ties?<\/p>\n\n\n\n SMTP (Simple Mail Transfer Protocol) var uztvert k\u0101 interneta \u201cofici\u0101lo pasta noda\u013cu\u201d – univers\u0101lu noteikumu kopumu, ko e-pasta klienti (piem., Outlook vai Apple Mail) un e-pasta serveri izmanto zi\u0146ojumu nos\u016bt\u012b\u0161anai un p\u0101rs\u016bt\u012b\u0161anai.<\/p>\n\n\n\n Kad nos\u016bti e-pastu, tas nenon\u0101k tie\u0161i adres\u0101ta pastkast\u012bt\u0113 vien\u0101 sol\u012b:<\/p>\n\n\n\n SMTP protokols darbojas gan pirmaj\u0101 (submission), gan otraj\u0101 (relay) sol\u012b. Savuk\u0101rt SMTP ports<\/strong> ir konkr\u0113tas numur\u0113tas \u201cdurvis\u201d server\u012b, kas paredz\u0113tas \u0161ai sazi\u0146ai.<\/p>\n\n\n\n K\u0101p\u0113c vietnei visp\u0101r tas j\u0101zina? T\u0101p\u0113c, ka WordPress p\u0113c noklus\u0113juma bie\u017ei nemaz neizmanto SMTP. Tas pa\u013caujas uz ieb\u016bv\u0113tu funkciju No pieg\u0101des (deliverability) viedok\u013ca tas ir liels risks:<\/p>\n\n\n\n Rezult\u0101ts: pastkast\u012b\u0161u nodro\u0161in\u0101t\u0101js redz neautentific\u0113tu e-pastu no web servera un iemet to spam map\u0113 vai pat noblo\u0137\u0113 piln\u012bb\u0101, bie\u017ei pat nepazi\u0146ojot.<\/p>\n\n\n\n T\u0101p\u0113c pareiz\u0101 pieeja ir piespiest WordPress apiet SMTP portu evol\u016bcija b\u016bt\u012bb\u0101 ir interneta c\u012b\u0146a ar spamu. Katrs ports ir kompromiss starp v\u0113sturisku mantojumu un m\u016bsdienu dro\u0161\u012bbas pras\u012bb\u0101m.<\/p>\n\n\n\n S\u0101kum\u0101 (1982. gad\u0101) praktiski bija viens variants – 25. ports<\/strong>, dom\u0101ts e-pasta serveru savstarp\u0113jai p\u0101rs\u016bt\u012b\u0161anai (Mail Transfer Agents, MTA). Tas bija atv\u0113rts, bez autentifik\u0101cijas un bez \u0161ifr\u0113\u0161anas – agr\u012bnaj\u0101, uztic\u012bbas pilnaj\u0101 interneta vid\u0113 tas str\u0101d\u0101ja.<\/p>\n\n\n\n Probl\u0113ma: spameri \u0101tri saprata, ka var piesl\u0113gties jebkuram serverim uz 25. porta un \u201catst\u0101t\u201d miljonu zi\u0146ojumu, ko serveris p\u0113c tam m\u0113\u0123in\u0101s pieg\u0101d\u0101t. T\u0101 k\u013cuva par atv\u0113rtu, ne\u0161ifr\u0113tu, neautentific\u0113tu \u013caunpr\u0101t\u012bgas izmanto\u0161anas kan\u0101lu.<\/p>\n\n\n\n M\u016bsdien\u0101s (un \u012bpa\u0161i 2026. gada realit\u0101t\u0113) gandr\u012bz visi ISP, cloud pakalpojumu sniedz\u0113ji un pat m\u0101jas t\u012bkli blo\u0137\u0113 izejo\u0161os savienojumus uz 25. portu<\/strong>, lai aptur\u0113tu botnetus un kompromit\u0113tus serverus.<\/p>\n\n\n\n 25. ports nav paredz\u0113ts tam, ko dara tava vietne (submission). Pat ja hostings to neblok\u0113tu, liela da\u013ca interneta tik un t\u0101 noblo\u0137\u0113s tavu s\u016bt\u012bjumu.<\/p>\n\n<\/div>\n\n\n\n 90. gadu beig\u0101s k\u013cuva skaidrs, ka e-pastam vajag \u0161ifr\u0113\u0161anu. T\u0101 par\u0101d\u012bj\u0101s 465. ports<\/strong> ar SMTPS<\/strong> (SMTP over SSL). \u0160eit \u0161ifr\u0113tais tunelis (m\u016bsdien\u0101s TLS) tiek izveidots uzreiz, pirms tiek s\u016bt\u012btas SMTP komandas – t\u0101 saucamais Implicit SSL\/TLS<\/strong>.<\/p>\n\n\n\n Interesant\u0101 nianse: 465. ports ilgsto\u0161i bija pla\u0161i izmantots, bet k\u0101du laiku tas pat tika uzskat\u012bts par \u201cdeprecated\u201d (jo standartu l\u012bmen\u012b virz\u012bba bija uz STARTTLS). Tom\u0113r praks\u0113 tas atgriez\u0101s ar pilnu jaudu un \u0161odien ir piln\u012bb\u0101 pie\u0146emts un \u013coti popul\u0101rs dro\u0161s standarts. Daudzi lieli pakalpojumi (t.sk. Gmail) to joproj\u0101m iesaka.<\/p>\n\n\n\n Lai sak\u0101rtotu standartu pusi, IETF ofici\u0101li noteica 587. portu<\/strong> k\u0101 galveno e-pasta submission<\/em> portu (tie\u0161i tas, kas vajadz\u012bgs vietnei un e-pasta klientiem).<\/p>\n\n\n\n 587. ports izmanto \u0161ifr\u0113\u0161anu caur STARTTLS<\/strong> – tas ir Explicit TLS<\/strong> modelis. Pl\u016bsma tipiski izskat\u0101s \u0161\u0101di:<\/p>\n\n\n\n Teor\u0113tiski \u0161is ports var\u0113tu atbalst\u012bt ar\u012b ne\u0161ifr\u0113tus savienojumus, bet 2026. gad\u0101 serveris, kas uz 587 neuzspie\u017e \u0161ifr\u0113\u0161anu, ir j\u0101uzskata par nedro\u0161u.<\/p>\n\n\n\n Praks\u0113: 587. ports ir visizplat\u012bt\u0101kais, ieteicamais m\u016bsdienu standarts e-pasta s\u016bt\u012b\u0161anai (submission)<\/strong> un pirmais, ko v\u0113rts m\u0113\u0123in\u0101t.<\/p>\n\n\n\n Da\u017ereiz dokument\u0101cij\u0101s par\u0101d\u0101s 2525. ports<\/strong>. Tas nav ofici\u0101ls SMTP standarta ports – dr\u012bz\u0101k alternat\u012bvs \u201crezerves\u201d ports, ko daudzi SMTP servisi un hosteri pied\u0101v\u0101 situ\u0101cij\u0101m, kad 587 un 465 ir blo\u0137\u0113ti.<\/p>\n\n\n\n Kad to lietot: ja hostings vai platforma blo\u0137\u0113 gan 587, gan 465 (reti, bet gad\u0101s), 2525 var b\u016bt vien\u012bgais praktiskais ce\u013c\u0161. Parasti tas izmanto to pa\u0161u STARTTLS pieeju k\u0101 587.<\/p>\n\n\n\n 2026. gad\u0101 izv\u0113le re\u0101li reduc\u0113jas uz diviem portiem – 587 un 465.<\/p>\n\n\n\n Pirm\u0101 izv\u0113le ir 587. ports ar STARTTLS.<\/strong> Tas ir ofici\u0101lais, m\u016bsdien\u012bgais e-pasta submission standarts, ko atbalsta praktiski visi SMTP pakalpojumu sniedz\u0113ji. Konfigur\u0113jot SMTP spraudni WordPress vid\u0113, \u0161o parasti ievada k\u0101 pirmo m\u0113\u0123in\u0101jumu.<\/p>\n\n\n\n Ja 587 k\u0101da iemesla d\u0113\u013c nestr\u0101d\u0101 (vai pakalpojuma sniedz\u0113js tie\u0161i iesaka 465), 465. ports ar SMTPS (implicit SSL\/TLS)<\/strong> ir piln\u012bgi korekta un dro\u0161a alternat\u012bva.<\/p>\n\n\n\n 25. ports nav dom\u0101ts vietnes e-pasta s\u016bt\u012b\u0161anai, tas bie\u017ei b\u016bs blo\u0137\u0113ts un ir ne\u0161ifr\u0113ts. T\u0101 m\u016bsdienu loma pamat\u0101 ir serveru savstarp\u0113ja relay sazi\u0146a, nevis WordPress pazi\u0146ojumi.<\/p>\n\n\n\n Kad ir skaidrs, kur\u0161 ports<\/em> ir pareizs, n\u0101kamais ir sak\u0101rtot visu \u0137\u0113di – no s\u016bt\u012b\u0161anas servisa l\u012bdz DNS autentifik\u0101cijai un WordPress konfigur\u0101cijai.<\/p>\n\n\n\n Pirmais solis ir p\u0101rst\u0101t s\u016bt\u012bt e-pastu no web servera. Tev vajag transactional e-pasta pakalpojumu<\/strong>, kura bizness ir pieg\u0101de (deliverability).<\/p>\n\n\n\n Daudziem nelieliem un vid\u0113jiem projektiem bezmaksas l\u012bmenis ir pietiekams tie\u0161i vietnes transactional pl\u016bsmai.<\/p>\n\n\n\n \u0160is ir kritisk\u0101kais tehniskais solis. Kad izv\u0113lies SMTP pakalpojumu, tev ir \u201cj\u0101pier\u0101da\u201d pasaulei, ka \u0161im servisam ir at\u013cauts s\u016bt\u012bt e-pastu tava dom\u0113na v\u0101rd\u0101. To izdara ar DNS ierakstiem (pie dom\u0113na re\u0123istratora vai DNS hostinga). Pakalpojumu sniedz\u0113js iedos prec\u012bzas v\u0113rt\u012bbas, kas j\u0101nokop\u0113.<\/p>\n\n\n\n SPF un DKIM iestat\u012b\u0161ana nav izv\u0113les lieta. Bez tiem pat labs SMTP serviss bie\u017ei negl\u0101bs no spam mapes.<\/p>\n\n<\/div>\n\n\n\n T\u0101l\u0101k WordPress ir j\u0101pasaka, lai tas lieto jauno s\u016bt\u012b\u0161anas kan\u0101lu. Praktisk\u0101kais veids ir SMTP spraudnis, kas p\u0101rtver Bie\u017ei izmantoti spraud\u0146i:<\/p>\n\n\n\n Tipiska konfigur\u0101cijas sec\u012bba (neatkar\u012bgi no spraud\u0146a):<\/p>\n\n\n\n Labiem SMTP spraud\u0146iem ir \u201cTest Email\u201d sada\u013ca. Nos\u016bti testu uz savu Gmail vai Outlook.<\/p>\n\n\n\n No izstr\u0101d\u0101t\u0101ja skatu punkta iepriek\u0161\u0113jie so\u013ci ir lo\u0123iski, bet tipiskam biznesa \u012bpa\u0161niekam tie ir daudz: dom\u0113na DNS, atsevi\u0161\u0137s SMTP serviss, spraudnis, porti, atsl\u0113gas. T\u0101p\u0113c tirg\u016b par\u0101d\u0101s integr\u0113tas pieejas, kas \u0161o komplekt\u0113 vien\u0101 pl\u016bsm\u0101.<\/p>\n\n\n\n T\u0101 k\u0101 WordPress probl\u0113mas sakne ir neautentific\u0113ta s\u016bt\u012b\u0161ana, visviegl\u0101k ir to apiet bez sare\u017e\u0123\u012btas konfigur\u0113\u0161anas. Piem\u0113rs \u0161\u0101dai pieejai ir Site Mailer by Elementor<\/a>, kas pozicion\u0113ts k\u0101 \u201czero-configuration\u201d spraudnis.<\/p>\n\n\n\n Otra bie\u017ea probl\u0113ma ir pats hostinga ierobe\u017eojums: porti, outbound politika, dro\u0161\u012bbas ierobe\u017eojumi. Kvalitat\u012bvs managed WordPress hostings parasti saprot Piem\u0113ram, Elementor Hosting<\/a> tiek b\u016bv\u0113ts uz cloud infrastrukt\u016bras un tiek pozicion\u0113ts k\u0101 performance-optimiz\u0113ts pamats, kur tipiski porti k\u0101 587 ir atv\u0113rti izmanto\u0161anai ar tavu SMTP spraudni. Ideja – maz\u0101k c\u012bn\u012bties ar vidi un vair\u0101k fokus\u0113ties uz korektu e-pasta pieg\u0101di.<\/p>\n\n\n\n Kad vietnes e-pasts ir salabots, svar\u012bgi nepazaud\u0113t reput\u0101ciju ar nepareizu lietojumu.<\/p>\n\n\n\n Nes\u016bti m\u0101rketinga jaunumus (newsletter) caur savu transactional SMTP servisu. Tas var saboj\u0101t dom\u0113na s\u016bt\u012b\u0161anas reput\u0101ciju un p\u0113c tam pat paroles atiestates s\u0101ks krist spam\u0101.<\/p>\n\n<\/div>\n\n\n\n At\u0161\u0137ir\u012bba praks\u0113:<\/p>\n\n\n\n Ja 10 000 adres\u0101tu kampa\u0146u s\u016bt\u012bsi caur transactional kan\u0101lu, palielin\u0101sies s\u016bdz\u012bbas un atteik\u0161an\u0101s, kas sit\u012bs pa reput\u0101ciju. Pareiz\u0101 pieeja ir izmantot atsevi\u0161\u0137u Email Service Provider (ESP) m\u0101rketingam (piem\u0113ram, Mailchimp vai ConvertKit), kas \u0161o reput\u0101cijas un atsl\u0113g\u0161an\u0101s procesu tur izol\u0113tu no kritiskajiem vietnes pazi\u0146ojumiem.<\/p>\n\n\n\n Lai vietne nekad nepaliek \u201cbez balss\u201d, strat\u0113\u0123iju var sak\u0101rtot tr\u012bs da\u013c\u0101s:<\/p>\n\n\n\n Jaut\u0101jums \u201ckuru SMTP portu izv\u0113l\u0113ties?\u201d ir labs starts, un 2026. gad\u0101 atbilde ir skaidra: 587 ar STARTTLS<\/strong> (ar 465\/SMTPS<\/strong> k\u0101 dro\u0161u alternat\u012bvu).<\/p>\n\n\n\n Ta\u010du \u012bst\u0101 probl\u0113ma parasti nav ports vien – t\u0101 ir vietnes s\u016bt\u012b\u0161anas metode. Ja p\u0101rst\u0101j pa\u013cauties uz Lieto 587. portu<\/strong> ar STARTTLS<\/strong> \u0161ifr\u0113\u0161anu. Ja tas nestr\u0101d\u0101, n\u0101kam\u0101 lab\u0101k\u0101 izv\u0113le ir 465. ports<\/strong> ar SMTPS<\/strong> (SSL\/TLS) \u0161ifr\u0113\u0161anu.<\/p>\n\n\n\n 25. ports ir ori\u0123in\u0101lais, ne\u0161ifr\u0113tais SMTP ports no 1982. gada. Tas tika masveid\u0101 izmantots spama s\u016bt\u012b\u0161anai, t\u0101p\u0113c m\u016bsdien\u0101s to blo\u0137\u0113 gandr\u012bz visi m\u0101jas ISP un daudzi cloud hostinga<\/a> pakalpojumu sniedz\u0113ji. Submission vajadz\u012bb\u0101m tas vienk\u0101r\u0161i nestr\u0101d\u0101s.<\/p>\n\n\n\n Abi ir dro\u0161i. 465<\/strong> izmanto Implicit TLS<\/em> – \u0161ifr\u0113tais savienojums s\u0101kas uzreiz. 587<\/strong> izmanto Explicit TLS<\/em> caur STARTTLS komandu – s\u0101kum\u0101 savienojums ir plain text un p\u0113c tam tiek \u201cupgrade\u201d uz \u0161ifr\u0113tu. 587 ir m\u016bsdienu ieteicamais standarts, bet abi varianti str\u0101d\u0101.<\/p>\n\n\n\n Tas ir viens-pret-vienu e-pasts, ko iedarbina lietot\u0101ja darb\u012bba vietn\u0113: kontaktformas iesniegums, paroles atiestates piepras\u012bjums, jauna lietot\u0101ja re\u0123istr\u0101cija, eCommerce pas\u016bt\u012bjuma apstiprin\u0101jums u.tml. \u0160\u0101di e-pasti j\u0101nos\u016bta caur dedicated SMTP servisu.<\/p>\n\n\n\n Marketing e-pasts ir viens-pret-daudziem s\u016bt\u012bjums (newsletter, akcijas, pazi\u0146ojumi). To j\u0101veic caur atsevi\u0161\u0137u platformu (Email Service Provider jeb ESP), lai nesaboj\u0101tu dom\u0113na s\u016bt\u012b\u0161anas reput\u0101ciju un neietekm\u0113tu vietnes kritisko pazi\u0146ojumu pieg\u0101di.<\/p>\n\n\n\n J\u0101, tie ir oblig\u0101ti. Tie ir DNS ieraksti, kas pier\u0101da e-pasta le\u0123itimit\u0101ti. SPF<\/strong> ir at\u013cauto s\u016bt\u012bt\u0101ju saraksts tavam dom\u0113nam. DKIM<\/strong> ir digit\u0101ls paraksts, kas apliecina, ka zi\u0146ojums nav ticis main\u012bts. Bez tiem e-pasts bie\u017ei izskat\u012bsies k\u0101 spams.<\/p>\n\n\n\n \u201cHost\u201d ir tava SMTP pakalpojuma pasta servera adrese. Piem\u0113ram, SendGrid gad\u012bjum\u0101 tas ir Tehniski var, bet nav ieteicams. Tas noz\u012bm\u0113, ka WordPress panel\u012b j\u0101glab\u0101 person\u012bg\u0101s piek\u013cuves deta\u013cas (dro\u0161\u012bbas risks), un Google piem\u0113ro stingrus s\u016bt\u012b\u0161anas limitus. Trafika p\u012b\u0137a laik\u0101 konts var tikt \u012bslaic\u012bgi noblo\u0137\u0113ts. Lab\u0101k izv\u0113l\u0113ties dedicated pakalpojumu.<\/p>\n\n\n\n Vienk\u0101r\u0161\u0101kais ir izmantot \u201czero-configuration\u201d spraudni k\u0101 Site Mailer by Elementor<\/a>, kas ar vienu uzst\u0101d\u012b\u0161anu p\u0101r\u0146em transactional e-pastu mar\u0161rut\u0113\u0161anu un pieg\u0101di bez portu un API konfigur\u0113\u0161anas.<\/p>\n\n\n\n Lab\u0101kajiem SMTP spraud\u0146iem (piem\u0113ram, WP Mail SMTP) iestat\u012bjumos ir \u201cTest Email\u201d sada\u013ca. Nos\u016bti testu no WordPress admin uz savu e-pastu. Ja tas pien\u0101k inbox, konfigur\u0101cija ir korekta.<\/p>\n\n\n Ja kontaktformas zi\u0146ojumi, pas\u016bt\u012bjumu apstiprin\u0101jumi vai paroles atiestates paz\u016bd \u201cnekurien\u0113\u201d, vaina bie\u017ei nav WordPress form\u0101, bet gan taj\u0101, k\u0101 vietne s\u016bta e-pastus. Izskaidroju, kur\u0161 SMTP ports 2026. gad\u0101 ir pareiz\u0101 izv\u0113le un k\u0101 sak\u0101rtot uzticamu pieg\u0101di.<\/p>\n","protected":false},"author":53,"featured_media":214,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[124,36,123,5,10],"class_list":["post-215","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-dns","tag-drosiba","tag-e-pasta-piegade","tag-smtp","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/posts\/215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/users\/53"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/comments?post=215"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/posts\/215\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/media\/214"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/media?parent=215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/categories?post=215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/lv\/wp-json\/wp\/v2\/tags?post=215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Galvenie secin\u0101jumi (\u012bsum\u0101)<\/h2>\n\n\n\n
\n\n
wp_mail()<\/code>) ir neautentific\u0113ta un n\u0101k no web servera, kam nav e-pasta reput\u0101cijas.<\/li>\n\n\nKas ir SMTP un k\u0101p\u0113c tas ir svar\u012bgi vietnei?<\/h2>\n\n\n\n
\n\n
smtp.gmail.com<\/code>). \u0160o soli bie\u017ei d\u0113v\u0113 par submission<\/em>.<\/li>\n\n\nWordPress
wp_mail()<\/code> probl\u0113ma<\/h3>\n\n\n\nwp_mail()<\/code>, kas m\u0113\u0123ina s\u016bt\u012bt e-pastu no pa\u0161a web servera<\/em>.<\/p>\n\n\n\n\n\n
tavs-domens.lv<\/code>, bet bez pier\u0101d\u0101mas identit\u0101tes.<\/li>\n\n\nwp_mail()<\/code> s\u016bt\u012b\u0161anas ce\u013cu un s\u016bt\u012bt e-pastu caur profesion\u0101lu SMTP pakalpojumu. Un te portu izv\u0113le k\u013c\u016bst praktiska.<\/p>\n\n\n\n\u012asa SMTP portu v\u0113sture (un k\u0101p\u0113c da\u013ca ir novecoju\u0161i)<\/h2>\n\n\n\n
25. ports – ori\u0123in\u0101lais \u201cspama \u0161osejas\u201d mantojums<\/h3>\n\n\n\n
Svar\u012bgi<\/h4>\n\n\n
465. ports – pirmais dro\u0161ais variants (SMTPS)<\/h3>\n\n\n\n
587. ports – m\u016bsdienu standarts (STARTTLS)<\/h3>\n\n\n\n
\n\n
EHLO<\/code> (sveiciens\/iesp\u0113ju piepras\u012bjums).<\/li>\n\n\nSTARTTLS<\/code>.<\/li>\n\n\nSTARTTLS<\/code> komandu, lai paaugstin\u0101tu<\/strong> savienojumu uz \u0161ifr\u0113tu.<\/li>\n\n\n2525. ports – neofici\u0101ls rezerves variants<\/h3>\n\n\n\n
2026. gada spriedums: kuru SMTP portu lietot?<\/h2>\n\n\n\n
Prim\u0101r\u0101 izv\u0113le: 587 (STARTTLS)<\/h3>\n\n\n\n
Sekund\u0101r\u0101 izv\u0113le: 465 (SMTPS)<\/h3>\n\n\n\n
Gandr\u012bz nekad: 25 (tikai relay, nevis submission)<\/h3>\n\n\n\n
SMTP portu sal\u012bdzin\u0101jums<\/h3>\n\n\n\n
\n\n
K\u0101 salabot WordPress e-pastu: soli pa solim<\/h2>\n\n\n\n
1) Izv\u0113lies dedicated transactional SMTP pakalpojumu<\/h3>\n\n\n\n
\n\n
2) Sak\u0101rto dom\u0113na DNS: SPF un DKIM<\/h3>\n\n\n\n
\n\n
tavs-domens.lv<\/code> dr\u012bkst pie\u0146emt tikai tad, ja tie n\u0101k no \u0161iem serveriem\/IP (piem\u0113ram, no maniem un SendGrid).\u201d Tas pal\u012bdz pret adre\u0161u spoofing.<\/li>\n\n\nSPF\/DKIM nav \u201cnice to have\u201d<\/h4>\n\n\n
3) Instal\u0113 un nokonfigur\u0113 SMTP spraudni WordPress vid\u0113<\/h3>\n\n\n\n
wp_mail()<\/code> un p\u0101radres\u0113 s\u016bt\u012b\u0161anu caur izv\u0113l\u0113to pakalpojumu.<\/p>\n\n\n\n\n\n
\n\n
smtp.sendgrid.net<\/code> vai smtp.gmail.com<\/code>).<\/li>\n\n\n4) Notest\u0113 un paskaties logus<\/h3>\n\n\n\n
\n\n
\u201cVienk\u0101r\u0161ais\u201d risin\u0101jums: ko dara modern\u0101s WordPress platformas<\/h2>\n\n\n\n
1) Integr\u0113ts transactional e-pasts (zero-config pieeja)<\/h3>\n\n\n\n
\n\n
2) Managed hostings ar sagatavotu pamatu SMTP izmanto\u0161anai<\/h3>\n\n\n\n
wp_mail()<\/code> riskus un nodro\u0161ina pamatu, lai tu visp\u0101r var\u0113tu ieviest lab\u0101s prakses.<\/p>\n\n\n\n\u0100rpus SMTP: transactional vs. marketing ir kritiska robe\u017ea<\/h2>\n\n\n\n
Svar\u012bgs noteikums<\/h4>\n\n\n
\n\n
Praktiska e-pasta strat\u0113\u0123ija 2026. gadam<\/h2>\n\n\n\n
\n\n
Nosl\u0113gum\u0101: p\u0101rst\u0101j pazaud\u0113t e-pastus un atjauno uztic\u012bbu<\/h2>\n\n\n\n
wp_mail()<\/code> un p\u0101rej uz autentific\u0113tu, profesion\u0101lu s\u016bt\u012b\u0161anu (ar korektu SPF\/DKIM), tu ne tikai salabo tehnisku niansi. Tu uzb\u016bv\u0113 uzticamu komunik\u0101cijas kan\u0101lu, kur klients sa\u0146em kv\u012bti, l\u012bds nepaz\u016bd, un bizness darbojas paredzami.<\/p>\n\n\n\nBie\u017e\u0101k uzdotie jaut\u0101jumi (FAQ)<\/h2>\n\n\n\n
1. K\u0101da ir vienk\u0101r\u0161\u0101 atbilde – kuru SMTP portu lietot?<\/h3>\n\n\n\n
2. K\u0101p\u0113c nevajadz\u0113tu izmantot 25. portu?<\/h3>\n\n\n\n
3. K\u0101da ir at\u0161\u0137ir\u012bba starp 587 (STARTTLS) un 465 (SMTPS)?<\/h3>\n\n\n\n
4. Kas ir \u201ctransactional email\u201d?<\/h3>\n\n\n\n
5. Ar ko transactional at\u0161\u0137iras no marketing e-pasta?<\/h3>\n\n\n\n
6. Kas ir SPF un DKIM, un vai tie tie\u0161\u0101m ir vajadz\u012bgi?<\/h3>\n\n\n\n
7. SMTP spraudnis prasa \u201cHost\u201d. Kas tas ir?<\/h3>\n\n\n\n
smtp.sendgrid.net<\/code>, bet Google gad\u012bjum\u0101 smtp.gmail.com<\/code>. Pakalpojuma sniedz\u0113js \u0161o v\u0113rt\u012bbu vienm\u0113r nor\u0101da dokument\u0101cij\u0101 vai iestat\u012bjumos.<\/p>\n\n\n\n8. Vai varu vienk\u0101r\u0161i izmantot savu parasto Gmail kontu vietnes e-pastiem?<\/h3>\n\n\n\n
9. K\u0101ds ir pats vienk\u0101r\u0161\u0101kais veids, k\u0101 salabot WordPress e-pastu probl\u0113mas?<\/h3>\n\n\n\n
10. K\u0101 notest\u0113t, vai SMTP iestat\u012bjumi str\u0101d\u0101?<\/h3>\n\n\n\n
Atsauces \/ Avoti<\/h2>\n