[GH-ISSUE #142] DKIM Signing clarification #716

Closed
opened 2026-03-14 10:19:47 +03:00 by kerem · 2 comments
Owner

Originally created by @Flash1232 on GitHub (Apr 14, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/142

Just to make sure this is not some bug with the docker image:

Is it true that the signing.table file as described in SELF-HOSTING.md will sign mail to both *.domain.com as well as the main domain.com aliases? When testing with the docker image I only receive DKIM signed mails when sending to xyz.domain.com. Mails sent to domain.com aliases simply don't have a DKIM signature.

The docker image inserts *.domain.com blabla (github.com/anonaddy/docker@d3573ee4a1/rootfs/etc/cont-init.d/03-config.sh (L272)) into the signing.table file whereas the SELF_HOSTING.md describes to use *@*.domain.com. Is there any difference or do I even need to additionally make a line with just domain.com without prefix asterisk?

Or am I doing something else incorrectly?

PS: There is a related issue in the docker repo: https://github.com/anonaddy/docker/issues/47 .

Originally created by @Flash1232 on GitHub (Apr 14, 2021). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/142 Just to make sure this is not some bug with the docker image: Is it true that the `signing.table` file as described in [SELF-HOSTING.md](https://github.com/anonaddy/anonaddy/blob/master/SELF-HOSTING.md#spf-and-dkim) will sign mail to both *.domain.com as well as the main domain.com aliases? When testing with the docker image I only receive DKIM signed mails when sending to xyz.domain.com. Mails sent to domain.com aliases simply don't have a DKIM signature. The docker image inserts *.domain.com blabla (https://github.com/anonaddy/docker/blob/d3573ee4a12eb53d65f001cbb46599997129187d/rootfs/etc/cont-init.d/03-config.sh#L272) into the `signing.table` file whereas the SELF_HOSTING.md describes to use `*@*.domain.com`. Is there any difference or do I even need to additionally make a line with just domain.com without prefix asterisk? Or am I doing something else incorrectly? PS: There is a related issue in the docker repo: https://github.com/anonaddy/docker/issues/47 .
kerem closed this issue 2026-03-14 10:19:52 +03:00
Author
Owner

@willbrowningme commented on GitHub (Apr 16, 2021):

The signing.table file should have both lines:

*@example.com    default._domainkey.example.com
*@*.example.com    default._domainkey.example.com

The first line signs all emails at the apex domain (example.com) and the second line signs all emails that are subdomains of the apex domain (anything.example.com). Both with the same key.

It seems the docker image needs another line:

${ANONADDY_DOMAIN}    default._domainkey.${ANONADDY_DOMAIN}
*.${ANONADDY_DOMAIN}    default._domainkey.${ANONADDY_DOMAIN}

Also I would have thought the lines in the docker file should be:

*@${ANONADDY_DOMAIN}    default._domainkey.${ANONADDY_DOMAIN}
*@*.${ANONADDY_DOMAIN}    default._domainkey.${ANONADDY_DOMAIN}

Although I don't use Docker so I haven't tested this myself.

In the self-hosting instructions I mention "add this line too" meaning in addition to the one from the tutorial - https://www.linuxbabe.com/mail-server/setting-up-dkim-and-spf

I've moved over to Rspamd recently which can sign emails so I may update the self-hosting docs soon to describe how to use that instead.

<!-- gh-comment-id:821276394 --> @willbrowningme commented on GitHub (Apr 16, 2021): The `signing.table` file should have both lines: ``` *@example.com default._domainkey.example.com *@*.example.com default._domainkey.example.com ``` The first line signs all emails at the apex domain (example.com) and the second line signs all emails that are subdomains of the apex domain (anything.example.com). Both with the same key. It seems the docker image needs another line: ``` ${ANONADDY_DOMAIN} default._domainkey.${ANONADDY_DOMAIN} *.${ANONADDY_DOMAIN} default._domainkey.${ANONADDY_DOMAIN} ``` Also I would have thought the lines in the docker file should be: ``` *@${ANONADDY_DOMAIN} default._domainkey.${ANONADDY_DOMAIN} *@*.${ANONADDY_DOMAIN} default._domainkey.${ANONADDY_DOMAIN} ``` Although I don't use Docker so I haven't tested this myself. In the self-hosting instructions I mention "add this line too" meaning in addition to the one from the tutorial - https://www.linuxbabe.com/mail-server/setting-up-dkim-and-spf I've moved over to Rspamd recently which can sign emails so I may update the self-hosting docs soon to describe how to use that instead.
Author
Owner

@Flash1232 commented on GitHub (Apr 16, 2021):

In the self-hosting instructions I mention "add this line too" meaning in addition to the one from the tutorial - https://www.linuxbabe.com/mail-server/setting-up-dkim-and-spf

Oh right, I got confused as I am using the docker image and just assumed this would be already present.

I've moved over to Rspamd recently which can sign emails so I may update the self-hosting docs soon to describe how to use that instead.

That would be great, and thanks for your work here! It is much appreciated :).

<!-- gh-comment-id:821329759 --> @Flash1232 commented on GitHub (Apr 16, 2021): > In the self-hosting instructions I mention "add this line too" meaning in addition to the one from the tutorial - https://www.linuxbabe.com/mail-server/setting-up-dkim-and-spf Oh right, I got confused as I am using the docker image and just assumed this would be already present. > I've moved over to Rspamd recently which can sign emails so I may update the self-hosting docs soon to describe how to use that instead. That would be great, and thanks for your work here! It is much appreciated :).
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#716
No description provided.