DKIM and DMARC for built-in outgoing mail
@subven yes, the file exists. These are the permissions:
drwxr-xr-x 2 yellowtent yellowtent 4096 May 10 10:33 ./ drwxr-xr-x 4 yellowtent yellowtent 4096 May 10 11:27 ../ -rw------- 1 yellowtent yellowtent 887 May 10 10:33 private -rw-r--r-- 1 yellowtent yellowtent 272 May 10 10:33 public -rw-r--r-- 1 yellowtent yellowtent 8 May 10 10:33 selector
The DKIM-signing works after a
chmod 777 privatebut I don't think that 's a sustainable solution.
The 'renew all certs'-button does not seem te renew my certificates.
My DNS-setup is 'wildcard', so I don't think it 's possible to re-setup dns?
I just added an extra domain (with cloudron 4.0.3) and it results in the same permissions:
drwxr-xr-x 2 yellowtent yellowtent 4096 May 17 06:54 ./ drwxr-xr-x 5 yellowtent yellowtent 4096 May 17 06:54 ../ -rw------- 1 yellowtent yellowtent 887 May 17 06:54 private -rw-r--r-- 1 yellowtent yellowtent 272 May 17 06:54 public -rw-r--r-- 1 yellowtent yellowtent 8 May 17 06:54 selector
doomilation last edited by
@girish Hi, I can confirm that this issue is still there with 2 domains.
Unfortunately I didn't check after a fresh install and just 1 domain.
@girish I had already deleted my test-setup; so I just set up a new one from scratch at scaleway. It results in the same errors and permissions as above.
@ruben Thanks. Can you tell me which DNS provider you are using? Let me try to reproduce the bug with that backend.
@girish I’m using the wildcard DNS-option.
@ruben thanks, I was able to reproduce the issue. It is related to the ubuntu image on scaleway. We relied on the user id to match between the host OS and the container. For some reason, adding a new user on scaleway starts from uid 1001 instead of 1000. Looking into a fix.
A fix for now is to just run
chmod +r /home/yellowtent/boxdata/mail/dkim/*/private.
As for certs for renewing, @ruben do you have incoming port 80 open on your server? The cert issue is not related to dkim keys.
This is fixed now in 4.1 (which will get released next week or so)
@girish Nice! Will definitely try again after the release.
subven last edited by
I can confirm that this is finally fixed now