Would want to use regex to do fancy masquerading

[tardich]

Would want to use regex to do fancy masquerading

[bokysan]

Sure, that does sound something that could be added. While it's not, you're free to create your own init script, mount it to /docker-init.db and it will be executed automatically on startup.

[tardich]

Ah good insight! Forgot that :-( I'll take a look at it, meanwhile

[tardich]

OK, I made it working. Here's what I did.

1. Created and mounted an init script to install postfix-pcre module from a secret (with the help of extraVolumes and extraVolumeMounts). This portion should be done at the docker image creation level I'd say
2. Created and mounted the pcre map as /etc/postfix/generic.pcre from a secret again, containing in my case: /([a-z]+)@int.fake.stba/ $[email protected]
3. Added config.postfix.smtp_generic_maps: "pcre:/etc/postfix/generic.pcre" as a value to the deployment

And then test. A message, originating from [email protected] is now actually sent to [email protected], which was the expected result.

Even more, this could be a little more templated from Helm to make it a little more seemlessly accessible. Something, maybe, like pcre.map: "/([a-z]+)@int.fake.stba/ $[email protected]", pcre.enabled: true, and pcre.filename: somefilename.pcre that could create the secret (or configMap) with the content, mount it to /etc/postfix/somefilename.pcre, and add smtp_generic_maps: pcre:/etc/postfix/somefilename.pcre to /etc/postfix/main.cf

This would be the ultimate goal, but I can live without it :-)

[bokysan]

Latest image (currently in master branch only) now includes install of postfix-pcre.