Closed 9600 closed 1 year ago
Thanks!
Wonder if it would make sense to base the config on the default debian one somehow?
Let me know if i should tag a new release
Wonder if it would make sense to base the config on the default debian one somehow?
The only other thing I spotted was that by default they also set OversignHeaders From
. The given rationale sounds reasonable and I very quickly tested here with my setup and it didn't result in DKIM header signature failure with mail received by Gmail, but I'm not sure if more testing might be wise.
Let me know if i should tag a new release
That would be great, thanks!
Wonder if it would make sense to base the config on the default debian one somehow?
The only other thing I spotted was that by default they also set
OversignHeaders From
. The given rationale sounds reasonable and I very quickly tested here with my setup and it didn't result in DKIM header signature failure with mail received by Gmail, but I'm not sure if more testing might be wise.
Ok! thinking also maybe it would require more complicated sedding/editing if the config format does not support overriding key=value pairs by just appending to it.
Feel free to look into if you want
Let me know if i should tag a new release
That would be great, thanks!
Pushed v1.1.20
Missing standard OpenDKIM base config. Possibly more of interest with DKIM verification than signing, but also gets rid of the key not secure error when running 'opendkim-testkey -vvv' inside the container to debug (which can confuse and lead people to think it means private key filesystem permissions instead of DNSSEC).