Skip to content

postfix-tlspol: upgrade to trixie + 1.11.0 update - #7334

Open
DerLinkman wants to merge 2 commits into
mailcow:stagingfrom
DerLinkman:feat/postfix-tlspol-update
Open

postfix-tlspol: upgrade to trixie + 1.11.0 update#7334
DerLinkman wants to merge 2 commits into
mailcow:stagingfrom
DerLinkman:feat/postfix-tlspol-update

Conversation

@DerLinkman

Copy link
Copy Markdown
Member

Contribution Guidelines

What does this PR include?

Short Description

This pull request updates the postfix-tlspol component and related configuration files to use newer versions of dependencies and images, and makes configuration changes to ensure compatibility with these updates. The main focus is on upgrading to version 1.11.0 of postfix-tlspol and updating related system and service configurations.

Dependency and Image Upgrades:

  • Updated the base images in the Dockerfile to use golang:1.26-trixie for building and debian:trixie-slim for runtime, and bumped the postfix-tlspol version to 1.11.0.
  • Updated the postfix-tlspol-mailcow service in docker-compose.yml to use image version 1.11.0.

Configuration Updates for Compatibility:

  • Upgraded syslog-ng configuration files to version 4.8, and replaced the deprecated stats_freq(0) option with the new stats(freq(0)) syntax in both syslog-ng.conf and syslog-ng-redis_slave.conf. [1] [2] [3] [4]
  • Changed the smtp_tls_policy_maps setting in postfix/main.cf to use the QUERYwithTLSRPT socketmap, likely reflecting an updated query interface in the new version.

Affected Containers

  • postfix-mailcow
  • postfix-tls-mailcow

Did you run tests?

What did you tested?

General mailing + startups, as well as MTA-STS Lookups during mail sending.

What were the final results? (Awaited, got)

Everything works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant