leap_platform.git/puppet/modules/site_postfix, branch 0.8.0rc1

add postscreen greeter (Resolves: 2303)

2016-02-11T23:45:46+00:00

Conflicts:
	puppet/modules/site_postfix/manifests/mx.pp

Due to the smtps transport specifying a header_check, the received_anon

2016-02-11T15:35:39+00:00

replacement wasn't being done. (#7890)

This moves that replacement into its own class, clears the old value and
sets it properly in the smtps transport.

Change-Id: I27c02730597df4943761d8bcb61014aeded9dc75

add postscreen greeter (Resolves: 2303)

2016-02-10T10:45:05+00:00

fix postfix Received anonymizing header regexp to properly match Client

2016-02-04T15:28:29+00:00

CN entries (#7867)

Change-Id: Ie33277a62e90f9dc0602bb963dbb96a61cebed1d

[bug] Add smtpd_relay_restrictions to postfix conf

2016-02-02T22:34:48+00:00

smtpd_relay_restrictions was added in postfix 2.10 (jessie
has 2.11 atm). Without this, outbound mails are rejected to
be relayed.

from http://www.postfix.org/SMTPD_ACCESS_README.html:

    NOTE: Postfix versions before 2.10 did not have
    smtpd_relay_restrictions. They combined the mail relay and spam blocking
    policies, under smtpd_recipient_restrictions. This could lead to
    unexpected results. For example, a permissive spam blocking policy could
    unexpectedly result in a permissive mail relay policy. An example of
    this is documented under "Dangerous use of
    smtpd_recipient_restrictions".

smtpd_relay_restrictions defaults to
'permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination'
and is configured here to check for a valid client cert.

see http://www.postfix.org/postconf.5.html#smtpd_relay_restrictions

- Resolves: #7856

Make sure the certs are installed for all smtp tls clients, thus

2016-01-21T15:46:49+00:00

ensuring the satellite hosts are setup properly (#7611)

Change-Id: I9dce57c305a6fd6a39596a941174fe1879af5e4f

Make sure machines in mynetworks are able to send mail through us,

2016-01-19T20:23:58+00:00

without getting blocked by the rbl (#7819)

Change-Id: Ib7a00f810b6c49528e5f99a1d83296553a81e65e

Make sure values that might get set incorrectly, due to preseed or

2015-12-17T20:51:21+00:00

debconf selections, are set correctly (#7478)

Change-Id: I3bd261fd6fe27bbf10b8994ffff9f8b7be5b9de0

Use client cert fingerprint lookup to determine if the user is allowed

2015-12-09T21:26:28+00:00

to relay mail through us (#3634)

Change-Id: I46cf3ffbef4261839c376f4c36a50d9c44eb1374

Switch from 'vmail' to leap-mx's user/group (#6936, #7639)

2015-12-01T15:12:47+00:00

This change will make sure that the user/group for leap-mx exist, and it
changes the mail location from /var/mail/vmail to the more helpful name
/var/mail/leap-mx.

This change requires:

https://github.com/leapcode/leap_mx/pull/78

and it would replace merge request:

https://github.com/leapcode/leap_mx/pull/65

and fix https://leap.se/code/issues/6936 and
https://leap.se/code/issues/7635

Change-Id: Idbe678dc999e394232c2eeef2b2018d39ab7cc3b