GitLab

These files do not contain sensitive data, so keep the default files
permissions.

sendmail(1) reads parts of it's configuration from the main.cf file.
When the file is not readable, the command invocation will fail with the
following error:

fatal: open /etc/postfix/main.cf: Permission denied

The parameters read from main.cf are documented here:
http://www.postfix.org/sendmail.1.html

It is an optional array of strings containing addtional entries for the
master.cf file

Make sure our version of the lens gets installed

* Fix resource dependencies

Dependencies must be set only if the resources exist in the catalog.
For some weird reason, this worked in Puppet 4 (and shouldn't have).

* Fix AbsolutePath test for Puppet 5

To be able to configure master.cf with chroot

* Use data types

* Use data types

* Use data types

* Use data types

* Use data types

* Use data types

* Use data types

* Move params validation to corresponding class: We only need to valide the
params when they need to be set / are actually used. Since Puppet 4.6 or 4.7,
stdlib's validate_string function doesn't accept undef anymore, so this has
to be changed.

* Remove specific error checking in specs: types checking validate_* functions
have different error messages depending on the version the stdlib module, the
version of puppet, maybe the version of ruby, the phase of the Moon... who knows.

map defines the default path by prepending '/etc/postfix/' to $name, so
this doesn't work when the name is already the absolute path. We need
to force the path passed to map.

The postmap command needs the complete path of the database

* Add a map define to create postfix maps

It is similar to existing hash define, but this define can create maps
of any type, not just hash.

* Refactor postfix::hash to avoid duplicate code

postfix::hash uses now the new postfix::map to create the hash

Add conffile define

* Add $manage_mailx boolean to control whether mailx is managed (replacement for PR #141)

* add more docs for $manage_mailx

* fix scope of variable

May address #130

so that we can be able to define specific package versions (or latest)