Skip to content

Fixed opendkim config on multiple nameservers#1218

Merged
erik-wramner merged 1 commit intodocker-mailserver:masterfrom
romansey:fix-opendkim-multiple-nameservers
Aug 9, 2019
Merged

Fixed opendkim config on multiple nameservers#1218
erik-wramner merged 1 commit intodocker-mailserver:masterfrom
romansey:fix-opendkim-multiple-nameservers

Conversation

@romansey
Copy link
Copy Markdown

@romansey romansey commented Aug 9, 2019

Having multiple nameservers set in /etc/resolv.conf currently results in a malformed opendkim configuration and opendkim performing a crash loop.

Given the file /etc/resolv.conf:

nameserver 1.2.3.4
nameserver 2.3.4.5
nameserver 3.4.5.6

The following /etc/opendkim.conf configuration lines are created on startup (which are malformed):

Nameservers 1.2.3.4
2.3.4.5
3.4.5.6

This fix merges the multiple lines and delimits them using ,, just as opendkim requires:

Nameservers 1.2.3.4,2.3.4.5,3.4.5.6

@erik-wramner
Copy link
Copy Markdown
Contributor

The tests failed, but I don't think it was caused by this change. I've restarted them.

@erik-wramner erik-wramner merged commit 1903e98 into docker-mailserver:master Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants