Closed jabl closed 8 years ago
After bumping the version of the postfix role to v1.1.0 e-mail stopped working on our install node. So I reverted that one. I guess some education/documentation is needed before we can use the updated version.
Ok, in what way did it fail? What does the generated /etc/postfix/main.cf look like?
@tiggi do you remember?
On 2016-08-22 07:50, Johan Guldmyr wrote:
@tiggi https://github.com/tiggi do you remember?
A diff between the postfix configs would be really usable..
Ulf Tigerstedt || Senior systems specialist CSC Oy || NeIC NT1 / NDGF GSM +358503818558 Johannesbergsvägen 17 || Närpes || Finland
Turns out I opened an issue about it: https://github.com/CSC-IT-Center-for-Science/fgci-ansible/issues/142 maybe that helps?
Any comments?
I looked at #142, but I couldn't really figure out what was wrong based on that. Can you copy-paste the generated /etc/postfix/main.cf, both for the install node and for a compute node? Or send them by email to me, if you don't want to broadcast your host/domain names to the interwebs.
@Tiggi and me did some testing yesterday. My problem is that the e-mails sent to root on the local machine - like: mail -s "test" root aren't forwarded to the FGCI admins list. We've done this with an /etc/aliases. Maybe this null config doesn't work for that scenario?
Quick googling brings up https://serverfault.com/questions/675365/postfix-hostname-and-etc-aliases . So yes, a "null client" config doesn't read /etc/aliases..
Compute nodes run postfix too, so we should configure it. Also set postfix_mydomain (https://github.com/CSC-IT-Center-for-Science/ansible-role-postfix/pull/2) in all.example.