![\"Backend-i](\"\/wp-content\/uploads\/2025\/02\/d0a8ec5a067a9d674e2b77db68d1a4f0.gif\")
<\/center> <\/p>\nT\u00eb rejat kryesore: <\/p>\n
- \n
- \u00ebsht\u00eb shtuar mund\u00ebsia e p\u00ebrdorimit t\u00eb algoritmeve kriptografik\u00eb TLS, t\u00eb q\u00ebndruesh\u00ebm ndaj p\u00ebrpjekjeve p\u00ebr thyerje nga kompjutera kuantik\u00eb. P\u00ebr t\u00eb p\u00ebrdorur k\u00ebta algoritm\u00eb k\u00ebrkohet p\u00ebrdorimi i deg\u00ebs s\u00eb bibliotek\u00ebs OpenSSL 3.5, e cila ende nuk ka dal\u00eb nga faza e zhvillimit. P\u00ebr zgjedhjen e algoritmeve paskanonik\u00eb n\u00eb Postfix nuk \u00ebsht\u00eb futur nj\u00eb sintaks\u00eb t\u00eb re p\u00ebr grupet TLS, por \u00ebsht\u00eb mb\u00ebshtetur n\u00eb cil\u00ebsimet e OpenSSL, t\u00eb cilat do t\u00eb p\u00ebrdoren gjat\u00eb p\u00ebrcaktimit t\u00eb parametrave \u00abtls_eecdh_auto_curves\u00bb dhe \u00abtls_ffdhe_auto_groups\u00bb me vlera bosh.\n
- \u00ebsht\u00eb shtuar mb\u00ebshtetje p\u00ebr titullin e mesazheve \u00abTLS-Required: no\u00bb (RFC 8689), p\u00ebr t\u00eb cilin dor\u00ebzimi do t\u00eb kryhet edhe n\u00eb rast se nuk \u00ebsht\u00eb e mundur t\u00eb realizohet politika e siguris\u00eb TLS t\u00eb vendosur n\u00eb cil\u00ebsime. N\u00ebse ky titull ekziston, klienti SMTP punon n\u00eb modin \u00absmtp_tls_security_level = may\u00bb, dmth nuk verifikon certifikatin. serverit<\/a> dhe mund t\u00eb rikthehet n\u00eb nj\u00eb lidhje me transferim t\u00eb dh\u00ebnash n\u00eb tekst t\u00eb hapur. N\u00eb deg\u00ebn e ardhshme t\u00eb r\u00ebnd\u00ebsishme t\u00eb Postfix, synojm\u00eb t\u00eb realizojm\u00eb zgjerimin SMTP REQUIRETLS.\n
- \u00ebsht\u00eb shtuar mb\u00ebshtetje p\u00ebr protokollin TLS-RPT (Transport Layer Security Reporting), q\u00eb lejon ndjekjen e d\u00ebshtimeve n\u00eb dor\u00ebzimin e mesazheve, t\u00eb cilat ndodhin kur nuk \u00ebsht\u00eb e mundur t\u00eb vendoset nj\u00eb lidhje e koduar, e cila p\u00ebrcaktohet nga p\u00ebrdorimi i zgjerimeve DANE (DNS-based Authentication of Named Entities) ose MTA-STS (MTA Strict Transport Security). Pronari i domain-it t\u00eb post\u00ebs p\u00ebrcakton n\u00eb DNS parametrat p\u00ebr TLS-RPT, pas s\u00eb cil\u00ebs server\u00ebt e post\u00ebs do t\u00eb d\u00ebrgojn\u00eb raporte me informacion rreth lidhjeve t\u00eb suksesshme dhe atyre d\u00ebshtake t\u00eb TLS te server\u00ebt MX q\u00eb sh\u00ebrbejn\u00eb domain-in. Zbatimi \u00ebsht\u00eb i bazuar n\u00eb bibliotek\u00ebn libtlsrpt.\n
- \u00ebsht\u00eb shtuar cil\u00ebsimi \u00absmtpd_hide_client_session = yes\u00bb, i cili \u00e7aktivizon futjen e informacionit mbi sesionin e klientit kur SMTP-serveri fut titullin \u00abReceived:\u00bb. Shembulli i titullit t\u00eb shkurtuar: \u00abReceived: by mail.example.com (Postfix) id postfix-queue-id p\u00ebr ; Dit\u00eb, dd Mon yyyy hh:mm:ss tz-offset (zon\u00eb).\u00bb\n
- \u00ebsht\u00eb shtuar mund\u00ebsia e kodimit MIME (RFC 2047) t\u00eb emrave n\u00eb titujt e gjeneruar nga Postfix \u00abFrom:\u00bb, t\u00eb cilat p\u00ebrfshijn\u00eb simbole jo ASCII. Schema e propozuar e kodimit lejon q\u00eb t\u00eb shmangen zgjerimet SMTPUTF8 (RFC 6531), t\u00eb cilat nuk mb\u00ebshteten nga t\u00eb gjitha aplikacionet. Rezultati i kodimit MIME duket si \u2018\u00bb=?charset?Q?gibberish?=:\u2019.\u2019 P\u00ebr t\u00eb p\u00ebrcaktuar kodimin origjinal t\u00eb emrave \u00ebsht\u00eb shtuar parametri \u00abfull_name_encoding_charset\u00bb, i cili n\u00eb m\u00ebnyr\u00eb default \u00ebsht\u00eb vendosur n\u00eb vler\u00ebn utf8.\n
- \u00ebsht\u00eb ndryshuar logjika e p\u00ebrpunimit t\u00eb lidhjeve t\u00eb d\u00ebshtuara kur n\u00eb cil\u00ebsime \u00ebsht\u00eb e specifikuar \u00abmysql:\u00bb ose \u00abpgsql:\u00bb vet\u00ebm nj\u00eb server. Ky server tani perceptohet si nj\u00eb balancues ngarkese dhe n\u00eb rast t\u00eb nj\u00eb d\u00ebshtimi, k\u00ebrkesa e p\u00ebrs\u00ebritur d\u00ebrgohet menj\u00ebher\u00eb, pa vones\u00eb prej 60 sekondash.\n
- N\u00eb Milter \u00ebsht\u00eb implementuar pasqyrimi n\u00eb log t\u00eb informacionit me arsyen p\u00ebr vendosjen e mesazhit n\u00eb karantin\u00eb.\n
- N\u00eb serverin SMTP, \u00ebsht\u00eb siguruar q\u00eb t\u00eb shkruhet n\u00eb log identifikuesi i radh\u00ebs ose vlera \u00abNOQUEUE\u00bb kur p\u00ebrfundon lidhja p\u00ebr shkak t\u00eb koh\u00ebs s\u00eb parapar\u00eb, nd\u00ebrprerjes ose tejkalimit t\u00eb kufirit t\u00eb numrit t\u00eb gabimeve. Procesi i pastrimit n\u00eb k\u00ebt\u00eb rast jep n\u00eb log \u00abqueueid: canceled\u00bb p\u00ebr mesazhet me nj\u00eb transaksion t\u00eb nisur, por jo t\u00eb p\u00ebrfunduar.\n
- N\u00eb klientin Dovecot SASL, kur jepen n\u00eb log mesazhet \u00abInvalid authentication mechanism\u00bb, tani tregohet mekanizmi i autentifikimit q\u00eb nuk ka mundur t\u00eb p\u00ebrdoret. Serveri SMTP, kur jep regjistrimet n\u00eb log \u00abreject\u00bb, tani tregon vlerat e cil\u00ebsimeve sasl_method, sasl_username dhe sasl_sender.\n
- P\u00ebr shkak t\u00eb ndryshimit t\u00eb protokollit t\u00eb brendsh\u00ebm, t\u00eb p\u00ebrdorur n\u00eb agjentin e dor\u00ebzimit, pas p\u00ebrdit\u00ebsimit t\u00eb versionit t\u00eb Postfix, k\u00ebrkohet q\u00eb t\u00eb rihapet me komand\u00ebn \u00abpostfix reload\u00bb ose me komandat \u00abpostfix stop\u00bb dhe \u00abpostfix start\u00bb. P\u00ebrndryshe, n\u00eb log do t\u00eb jepet nj\u00eb paralajm\u00ebrim \u00abunexpected attribute smtputf8 from xxx socket (expecting: sendopts)\u00bb. <\/ul>\n