<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
span.EmailStyle19
{mso-style-type:personal-compose;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p>Hi Peter<o:p></o:p></p>
<p>I have wanted to mention this package for some time. I consider it essential to postfix TLS and TLSRPT integration. Although I have been compiling myself and using this package on my production servers since January 2025 with ease, I believe it would benefit
the EL community more to have it available on GhettoForge.<o:p></o:p></p>
<p>https://github.com/Zuplu/postfix-tlspol<o:p></o:p></p>
<p>To the best of my knowledge, it was the first (and possibly is still the only) open-source program to resolve both TLSA and MTA-STS records and prioritize DANE delivery when recipients have specified both record types. The author has been developing this
since October 2024 and has brought Wietse Venema into the discussion several times to clarify IETF RFC language and postfix connectivity. A couple of European email services providers (with high and varied volume) also actively worked with the author to fix
some issues. The integration was extremely well done with helpful logs, console query commands for testing, compact, high-speed processing, and using best practice in general. The only updates for about the last 6 weeks have been platform related and I personally
consider it stable.<o:p></o:p></p>
<p>Mike<o:p></o:p></p>
<p><o:p></o:p></p>
</div>
</body>
</html>