#STARTTLS
ldap.conf controls every libldap client: ldapsearch, nslcd, pam_ldap. Set TLS_REQCERT demand to force StartTLS and cert validation against your CA. #linux #ldap #starttls https://www.valtersit.com/vault/force-starttls-for-openldap-client-with-ldapconf-and-tlsreqc-04a10a/
Force StartTLS for OpenLDAP Client with ldap.conf and TLS_REQCERT
www.valtersit.com
November 16, 2026 at 4:20 PM
Hosting on Hetzner, DigitalOcean, or Linode? Most cloud providers block outbound Port 25 by default to combat spam.

If you run Coolify or Dokku, route transactional mail over submission port 587 with STARTTLS instead.

Setup guide: www.sadasend.com/integrations...
November 18, 2026 at 12:04 PM
🚨 EUVD-2026-122689
📊 5.3/10

📝 If an attacker was able to perform a man-in-the-middle attack on an SMTP or POP3 server connection using STARTTLS, the attacker could inject server responses befo...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-122689

#cybersecurity #infosec #cve #euvd
November 16, 2026 at 9:02 PM
開かれたシステムであることの利点と欠点は不可分なので、それを持って電子メールはダメだと言われても賛同できないな
メールも使い方が大事で、何でもかんでも一々メッセージアプリを入れろと言ってくるほうが嫌だわ
STARTTLS+MTA-SLSとSPF+DKIM+DMARCで最低限求められる水準はクリアしているんじゃないですか?代替システムを作るより、SMTPSとドメイン検証の普及活動をしたほうがいいと思います
November 13, 2026 at 9:53 AM
Du hast vermutlich auf einem der Geräte das sogenannte POP3 Protokoll eingerichtet. Schau Mal hier und klicke dich notfalls durch, wie du stattdessen IMAP einrichtest.
November 12, 2026 at 8:46 PM
⚠️ Sooma is reporting an Incident since 00:26 UTC

"SMTP mail.sooma.com…"

Affects: SMTP mail.sooma.com:587 (STARTTLS), SMTP mail.sooma.com:465 (SSL), SMTP mail.sooma.com:25

Live timeline → https://pingoru.io/providers/sooma/incidents/12479741?utm_source=bluesky&utm_content=inc-12479741
Sooma: SMTP mail.sooma.com:25, SMTP mail.sooma.com:587 (STARTTLS), and 1 other service are degraded · November 11, 2026 · Pingoru
Sooma incident on November 11, 2026: SMTP mail.sooma.com:587 (STARTTLS) and SMTP mail.sooma.com:465 (SSL) are degraded. Started 12:26 AM UTC, resolved ongoing (● 6m). Affected: Servidores de envio (SMTP mail.sooma.com:587 (STARTTLS)), Servidores de envio (SMTP mail.sooma.com:465 (SSL)), Servidores de envio (SMTP mail.sooma.com:25).
pingoru.io
November 11, 2026 at 12:32 AM
CVE-2026-126135 - SMTP and POP3 response injection when using STARTTLS
CVE ID : CVE-2026-126135

Published : 10. November 2026 18:59 | 28 Minuten ago

Description : If an attacker was able to perform a man-in-the-middle attack on an SMTP or POP3 server connection using STA...
CVE-2026-126135 - SMTP and POP3 response injection when using STARTTLS
If an attacker was able to perform a man-in-the-middle attack on an SMTP or POP3 server connection using STARTTLS, the attacker could inject server responses before the TLS handshake completed. Thunderbird would process these responses after the handshake, as if they had been received from the server over the encrypted …
cvefeed.io
November 10, 2026 at 7:58 PM
SMTP accepted the message. That didn't mean it reached the inbox.
On one of my own systems, an automatic notification reported success. The next mail server accepted the message over an encrypted connection (SMTP over STARTTLS). I checked the recipient side anyway. The message was in Spam. That is a small example of a bigger debugging mistake: treating success at one layer as proof of the user's outcome. ## Name the assertion you are actually testing A website contact or notification flow has several different assertions: 1. The visitor can find the contact action. 2. The browser sends the request. 3. The application accepts it. 4. The sending server hands off the message. 5. The receiving system accepts or classifies it. 6. The intended person can find it where they expect it. A green result for step 4 does not establish steps 5 or 6. SMTP acceptance is evidence about the handoff, not an inbox-placement guarantee. ## Don't leap from symptom to cause In my case, the receiving-side check established Spam placement for that message. It did **not** establish the spam cause, and I am not presenting it as a completed deliverability fix. Investigating the cause would mean looking at the actual message, authentication results (SPF/DKIM/DMARC), domain records, reputation, and sending/receiving behavior. Blindly changing DNS because "email is broken" can add a second problem. A useful diagnostic note separates three things: what was observed, what remains unknown, and what the next check would establish. Any correction then needs its own result check. ## Honest limits * This write-up is from my own systems, not a customer case study. * Placement ≠ root cause. I found where the message landed; that alone did not fix authentication or reputation. * I will not claim a universal spam fix from one observation. ## Why I'm writing this under Mosfetti I'm Carl. Mosfetti is a service-first tech shop: WordPress and website help, business email/domain troubleshooting, hosting and backups, remote diagnosis, and local computer repair in Michigan's Upper Peninsula. The public site leads with the problem, not a product shelf. If your site reports success but the useful result is missing, start here: https://mosfetti.com
dev.to
November 9, 2026 at 8:40 PM
Time every SMTP phase with swaks: connect to banner, banner to STARTTLS, TLS handshake, message acceptance. Parse the verbose transcript for per-step metrics on Ubuntu/Debian. #smtp #swaks #mail https://www.valtersit.com/vault/roundtrip-smtp-transaction-timing-with-swaks-and-tls-handsha-b1b568/
Round-trip SMTP transaction timing with swaks and TLS handshake metrics
www.valtersit.com
November 8, 2026 at 7:50 AM
Configure Postfix to relay outbound mail via Microsoft 365 using smtp.office365.com:587 with SASL PLAIN, STARTTLS, and TLS pinning against the system CA store. https://www.valtersit.com/vault/relay-mail-through-microsoft-365-with-postfix-connector-and--75e265/
Relay mail through Microsoft 365 with Postfix connector and TLS pinning
www.valtersit.com
November 7, 2026 at 10:20 PM
CVE-2026-120250 - OpenAlgo 1.0.0.29 before 2.0.3.1 Improper Certificate Validation in SMTP Connections
CVE ID : CVE-2026-120250

Published : Nov. 1, 2026, 1:17 a.m. | 16 minutes ago

Description : OpenAlgo 1.0.0.29 before 2.0.3.1 contains an improper certificate validation...
CVE-2026-120250 - OpenAlgo 1.0.0.29 before 2.0.3.1 Improper Certificate Validation in SMTP Connections
OpenAlgo 1.0.0.29 before 2.0.3.1 contains an improper certificate validation vulnerability in utils/email_utils.py and utils/email_debug.py that disables TLS hostname and certificate checks for STARTTLS and SMTPS. Network-positioned attackers can present a forged certificate to intercept SMTP credentials and all later mail, including password-reset links.
cvefeed.io
November 1, 2026 at 1:55 AM
Consiglio n8n: il nodo Send Email con Gmail non si collega? Host smtp.gmail.com, verifica in due passaggi attiva e una password per le app al posto della tua. Porta 465 con SSL/TLS acceso; con la 587 lascia SSL/TLS spento, perché n8n usa STARTTLS. #n8n
October 30, 2026 at 11:36 AM
587 with STARTTLS works too. The RFC rates the two as equally secure when both ends are set to require encryption, so that's the setting worth checking. www.rfc-editor.org/rfc/rfc8314
October 28, 2026 at 1:49 PM
DuoKey bietet Live-Sondierung des Post-Quanten-Schlüsselaustausches, Datenbank-/STARTTLS-Abdeckung und generiert standardisierte Cryptography Bill of Materials (CBOM)-Exporte. Die Plattform bietet simulationsbasierte Migrationsplanung, um Organisationen beim Übergang zur NIST-...
DuoKey: Live-Sondierung und Post-Quanten-kryptografisches Sicherheitslage-Management
quantumzeitgeist.com
October 27, 2026 at 3:56 PM
Port 25 is for server-to-server relay. Port 587 is for submission with STARTTLS. Port 465 is submission with TLS from the first byte, and RFC 8314 has recommended it since 2018.
October 27, 2026 at 1:00 PM
DuoKey обеспечивает живое тестирование обмена постквантовыми ключами, покрытие базы данных/STARTTLS и генерирует стандартизированные экспорты реестра криптографии (СБМ). Платформа предлагает планирование миграции на основе моделирования, чтобы помочь организациям перейти на по...
DuoKey: Живое тестирование и управление состоянием постквантовой криптографии
quantumzeitgeist.com
October 27, 2026 at 3:57 PM
DuoKey מספקת בדיקה חיה של החלפת מפתחות לאחר-קוואנטית, כיסוי בסיס נתונים/STARTTLS, וייצוא ביל חומרים קריפטוגרפיים (CBOM) סטנדרטיים. הפלטפורמה מציעה תכנון הגירה מבוסס סימולציה כדי לעזור לארגונים לעבור לקריפטו NIST לאחר-קוואנטית...

#קריפטו_קוואנטי #קריפטוגרפיה #חדשות
DuoKey: בדיקה חיה וניהול עמדה קריפטוגרפית לאחר-קוואנטית
quantumzeitgeist.com
October 27, 2026 at 3:58 PM