[Bug 290315] mail/py-pyspf broken with openssl32+ patch provided, tested to OpenSSL 3.0.16

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290315

            Bug ID: 290315
           Summary: mail/py-pyspf  broken with openssl32+ patch provided,
                    tested to  OpenSSL 3.0.16
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet@FreeBSD.org
          Reporter: gessel@blackrosetech.com
             Flags: maintainer-feedback?(sunpoet@FreeBSD.org)
          Assignee: sunpoet@FreeBSD.org

Created attachment 264643
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=264643&action=edit
Patch for pyspf-milter for to set CRYPTOGRAPHY_OPENSSL_NO_LEGACY

On my system, where I use OpenSSL 3.0.16 from ports, default mail/py-pyspf
service silently fails to start.  The logs fill with errors like:

postfix/smtp-in/smtpd[76621]: warning: connect to Milter service
unix:/var/run/pyspf-milter/pyspf-milter.sock: No such file or directory

Executing

/usr/sbin/daemon -c /usr/local/bin/pyspf-milter
/usr/local/etc/pyspf-milter/pyspf-milter.conf

yields some additional data

RuntimeError: OpenSSL 3.0's legacy provider failed to load. This is a fatal
error by default, but cryptography supports running without legacy algorithms
by setting the environment variable CRYPTOGRAPHY_OPENSSL_NO_LEGACY. If you did
not expect this error, you have likely made a mistake with your OpenSSL
configuration.

The attached patches restore normal operation.

-- 
You are receiving this mail because:
You are the assignee for the bug.