GitHub puppet-postfix
Puppet postfix module

Repo Checks ( 20 of 26 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Debian
No translation
passed
Supports Latest Debian
No translation
passed
Supports Only Current Ubuntu
No translation
passed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
passed
Supports Only Current Alpine
No translation
failed
Supports Latest Alpine
No translation
failed
Supports Only Current Fedora
No translation
passed
Supports Latest Fedora
No translation
failed
Supports Only Current Freebsd
No translation
passed
Supports Latest Freebsd
No translation
passed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
failed

Open Pull Requests

Handle [host] vs [host]:port nexthop

Pull Request (PR) description

This expands the testing on host/port combinations in nexthop in order to allow more options to get handled correctly.
I'm not an expert on this by any means, but I think this covers the edge cases that #311 brings up?

This Pull Request (PR) fixes the following issues

Fixes #311

Open PR in GitHub
if relayhost is defined, then use the satellite profile
enhancement
merge-conflicts
enhancement

Pull Request (PR) description

when relayhost is define in the init.pp, there is nothing call behind it. As it, if you use it like show in the documentation, it don't work.
After reading the code, it look like that the standard usage for relayhost is to use satellite profile that permit to configure postfix to send all email to $relayhost.

This Pull Request (PR) fixes the following issues

Fixes #295

Open PR in GitHub
Native support for storing bind_pw in hiera; ldap_options is now more flexible.

There was no intrinsic way to store an encrypted bind password in heira, so added '$postfix::ldapbindpw'.

Converted '$postfix::ldap_options' to be optional or a string or an array of strings.

Modified the ldap-aliases.cf template so that ldap_options can be optional / a string / an array of strings, and then rendered in alphabetical order.

Open PR in GitHub
init.pp: use the postfix default for mydestination
enhancement
backwards-incompatible
enhancement
backwards-incompatible
enhancement
backwards-incompatible

It is less surprising if the puppet module's default configuration matches a standard default postfix configuration.

Open PR in GitHub