Upgrade to debian 12 and add postfix_exporter #49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Since we're stuck with syslog for the moment (due to OpenDKIM) we could alternatively keep postfix using syslog for the time being. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're attempting to reduce the reliance on syslogd. Recent versions of postfix can log directly to stdout or a file so we're making use of this. S6 also has a logging system that performs its own file rotation and can output to both a file and stdout (
s6-log). Logging to a file is necessary to support the postfix_exporter which uses both the spool socket and mail logs. Unfortunately OpenDKIM only support syslog logging (hopefully this will change in the future and we can completely remove syslog).