From 36491e787c8be5b32b93f5c3b20edd9aa9d4c4e9 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 2 Feb 2026 18:01:03 +0000 Subject: More qmail-smtpc stuff --- doc/index.html | 3 ++ doc/qmail-smtpc.html | 79 ++++++++++++++++++++++++++++++++++++++++++++++++++++ doc/upgrade.html | 1 + 3 files changed, 83 insertions(+) create mode 100644 doc/qmail-smtpc.html (limited to 'doc') diff --git a/doc/index.html b/doc/index.html index fc355d7..8dfae68 100644 --- a/doc/index.html +++ b/doc/index.html @@ -39,6 +39,9 @@ requirement if you link against the shared version of the skalibs library.
  • s6 version 2.14.0.1 or later. It's a build-time and run-time requirement.
    • +
  • s6-dns version +2.4.1.1 or later. It's a build-time requirement. It's also a run-time requirement +if you link against the shared version of the s6-dns library.
  • s6-networking version 2.7.2.1 or later. It's a build-time and run-time requirement.
    • diff --git a/doc/qmail-smtpc.html b/doc/qmail-smtpc.html new file mode 100644 index 0000000..47ee375 --- /dev/null +++ b/doc/qmail-smtpc.html @@ -0,0 +1,79 @@ + + + + + + smtpd-starttls-proxy: the qmail-smtpc program + + + + + + +

    +smtpd-starttls-proxy
    +Software
    +skarnet.org +

    + +

    The qmail-smtpc program

    + +

    +qmail-smtpc is an SMTP client, meant to be used as a drop-in +replacement to +qmail-remote. +

    + +

    + It is not meant to be invoked directly by the user; it only makes sense +in the context of a qmail, netqmail or notqmail installation. +

    + +

    Interface

    + +

    + qmail-smtpc follows the exact same interface as +qmail-remote. +The binary can literally be renamed qmail-remote then dropped +in /var/qmail/bin in place of the stock qmail-remote +program. With some patches, it can also be used by setting the +QMAILREMOTE environment variable to the path where qmail-smtpc +is installed. +

    + +

    Differences with qmail-remote

    + + + +

    Control files

    + +

    + qmail-smtpc uses a few extra control files in /var/qmail/control: +

    + +

    +
    trustanchors
    +
    Contains the path to the certificates for known trust anchors for X.509 +certificate validation. If the path ends with a slash, like /etc/ssl/certs/, +then it is interpreted as a directory containing hashes to the certificates. If +it does not, like /etc/ssl/cert.pem, then it is interpreted as a big +PEM file containing all the trust anchors. If the file is nonexistent or empty, +or only contains a newline, then STARTTLS is not attempted.
    +
    clientcert
    +
    If this file exists and is nonempty, it must contain the path to a client +certificate. This certificate will be sent to the server during a TLS negotiation. +This is useful in certain setups requiring client authentication.
    +
    clientkey
    +
    This file must be used in conjunction with clientcert. It contains +the path to the private key used to sign the client certificate. Note that access +to the private key file should be as restricted as possible, but the qmailr +user (or whatever user qmail-smtpc runs as) must be able to read it.
    +
    + + + diff --git a/doc/upgrade.html b/doc/upgrade.html index 7aa6237..1dba5fc 100644 --- a/doc/upgrade.html +++ b/doc/upgrade.html @@ -25,6 +25,7 @@ dependency bumped to 2.14.5.1
  • s6 dependency bumped to 2.14.0.1
    • +
  • New dependency: s6-dns 2.4.1.1
  • s6-networking dependency bumped to 2.7.2.1 and made mandatory.
    • -- cgit v1.3.1