I decided to set up some of my mail servers to require certification authentication on the submission port (587). In my case, I want to forward mail from my server at home to my public servers out there on the Internet. I don’t want just anyone to be able to submit mail here, so the easiest way for me do to this was with certification.
Postoffice — Encrypted Mail Service
Send secure, encrypted messages as NFTs. Only the recipient can decrypt. Permanent, immutable, and truly private communication on the blockchain.
Requirements for HTTPS for Local Domains
When connecting to servers on their local network, users are surprised to encounter user interfaces that display errors, show insecure connections, and block some HTTP features when missing a secure context. However, obtaining PKIX certificates for those servers is difficult for a variety of reasons. This document explores requirements for authenticating local servers.
HTTPS for Local Networks · Issue #78 · w3c/tpac2024-breakouts
Session description It is not possible to get a publicly trusted CA to sign a certificate for a local domain (i.e. a non-publicly resolvable domain name such as router.local, printer.home, 192.168....
forwardemail/caldav-adapter
CalDAV server for Node.js and Koa. Modernized and maintained for @forwardemail
Install a root CA certificate in the trust store
Enterprise environments sometimes have a local Certificate Authority (CA) that issues certificates for use within the organization. For an Ubuntu server to be functional, and to trust the hosts in ...
Self-hosting email the hard way from your own routable IPv4 block up
How we refreshed self-hosted Recoil email with our own RIPE-allocated IPv4 block, and deployed Postfix/rspamd/Dovecot to get full SPF/DKIM/DMARC deliverability.
Free Email Forwarding for Custom Domains - #1 Open Source Email Service 2026
Get free email forwarding for custom domains. Send & receive as you@yourdomain.com with unlimited aliases, 10GB storage, IMAP/POP3/SMTP & 100% open-source security. Trusted by 500K+ users. Setup in 2 minutes.
Open Badges 3.0: Complete guide to digital credentials | POK
Discover what Open Badges 3.0 are, the global standard for verifiable digital credentials. Learn how they work and how POK uses them to certify skills and competencies.
Verified.Quest
Below you will find answers to the most common questions about this project, instructions for requesting verification, and details on how to see badges on the Officially Verified accounts in your feed.
These 20 Awesome API Clients Will Change How You Work with APIs
Postman has become a staple in API development, but it’s far from the only option. As the API...
647959 - Add Honest Achmed's root certificate
RESOLVED (kathleen.a.wilson) in CA Program - CA Certificate Root Program. Last updated 2026-04-24.
Using Gmail SMTP with Cloudflare Email Routing: A Step-by-Step Guide
Using Gmail SMTP with Cloudflare Email Routing: A Step-by-Step Guide · GitHub
Home - maddy
Maddy Mail Server implements all functionality required to run a e-mail server. It can send messages via SMTP (works as MTA), accept messages via SMTP (works as MX) and store messages while providing access to them via IMAP. In addition to that it implements auxiliary protocols that are mandatory to keep email reasonably secure (DKIM, SPF, DMARC, DANE, MTA-STS).
A New Form of Verification on Bluesky - Bluesky
We’re introducing a new layer of verification — a user-friendly, easily recognizable badge. Additionally, independent organizations can verify accounts directly through our Trusted Verifiers feature.
New authentication flow for Sill - Euphonos
Sill no longer requires an email for signup
Decentralized Identity Verification using Zero-Knowledge Proofs: A Privacy-Preserving Authentication Framework
In the contemporary online interaction, digital iden- tity is central, but most systems follow a centralized provider like Google or Facebook. Although convenient, these models pose ma- jor risks to data breach, surveillance, and single point of failure. The proposed paper proposes a privacy-sensitive decentralized identity verification system that uses Zero-Knowledge Proofs (ZKPs) to allow users to make it through claims (e.g., age, citizen- ship, or enrollment) without any personal data being provided, thereby solving the challenges outlined in the paper. Our architecture integrates verifiable credentials, zero-knowledge-SNARKs and an issuer trust registry that is maintained on blockchain smart contracts to guarantee trustless verification and eliminate dependence on centralized authorities. Its system gives its users full control over credentials, allows reuse across applications, and does not expose data.A proof-of-concept implementation has shown the approach to be feasible with Circom and SnarkJS to generate proof, Solidity smart contracts to verify them, and a user interface implemented in React. Results of the evaluations showed that determination of the verification latency is low, the overhead to generate proofs is moderate, and no privacy leakage occurs. It can be used in potential applications such as education, e-governance, healthcare, finance, and online voting.