Accept mails from the internal network and forward them via mail.typo3.org as smarthost
- debian
- t3-base (~> 0.2.0)
- t3-chef-vault (~> 1.0.0)
- #Logger:0x00007fd4de443468 () (Recommended but not required)
- #Logger:0x00007fd4de443468 () (Suggested but not required)
- Conflicts with #Logger:0x00007fd4de443468 ()
node['email_adress']- email address for the TYPO3 cookbook maintainers. Defaults to[email protected].node['postfix']['main']['inet_interfaces']- Defaults toall.node['postfix']['main']['mynetworks']- Defaults to10.0.0.0/8.node['postfix']['main']['smtp_sasl_auth_enable']- Defaults toyes.
The default recipe
Build status on our CI server:
- master (release):
Every mailrelay server needs an own mail account. Set this up in Mailcow and configure it to disable sender checks.
Storing the secret in chef-vault can be done as follows (after the host has been provisioned with t3-base):
- Create local file containing data bag data (
mailtypo3org-srvXXXtypo3org.json):
{
"smarthosts": {
"mail.typo3.org": {
"username": "[email protected]",
"password": "123456"
}
}
}- Create vault item:
$ knife vault create passwords-production mailtypo3org-srvXXXtypo3org --mode client --search 'fqdn:srvXXX.typo3.org' --json mailtypo3org-srvXXXtypo3org.json- Optionally: Verify that the host is really added to the vault keys:
$ knife data bag show passwords-production mailtypo3org-srvXXXtypo3org_keys- Delete clear-text file, DO NOT COMMIT!
Maintainer:: TYPO3 Server Admin Team ([email protected])
License:: Apache 2.0
