starred/modoboa-modoboa

Fork 0

mirror of https://github.com/modoboa/modoboa.git synced 2026-04-25 17:06:01 +03:00

[GH-ISSUE #1647] dkim check fails #1295

New issue

Closed

opened 2026-02-27 11:16:21 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 11:16:21 +03:00

Owner

Originally created by @Greybane on GitHub (Jan 6, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1647

Impacted versions

Modoboa: 1.13.0
installer used: Yes
Webserver: Nginx

Steps to reproduce

Add domain to modoboa.
Configure DKIM in the web ui.
Make sure the record passes tests on sites like dmarcanalyzer.com & dkimcore.org

Current behavior

The DNS check is red and says "No record found."

Expected behavior

DNS check should turn green and say "A DNS record has been found and is valid."

Originally created by @Greybane on GitHub (Jan 6, 2019). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1647 # Impacted versions * Modoboa: 1.13.0 * installer used: Yes * Webserver: Nginx # Steps to reproduce Add domain to modoboa. Configure DKIM in the web ui. Make sure the record passes tests on sites like dmarcanalyzer.com & dkimcore.org # Current behavior The DNS check is red and says "No record found." # Expected behavior DNS check should turn green and say "A DNS record has been found and is valid."

kerem

2026-02-27 11:16:21 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@tonioo commented on GitHub (Jan 9, 2019):

@Greybane Can you check if #1648 fixes your problem?

@tonioo commented on GitHub (Jan 9, 2019): @Greybane Can you check if #1648 fixes your problem?

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@ObiOnyemaobi commented on GitHub (Jan 21, 2019):

Same issue here. Two different environments/installations

@ObiOnyemaobi commented on GitHub (Jan 21, 2019): Same issue here. Two different environments/installations

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@lsh-0 commented on GitHub (Feb 9, 2019):

I've just upgraded to 1.13.1, the information pane in the Modoboa admin interface confirms this however my DKIM label is still red with the label no record found. https://www.dmarcanalyzer.com gives me all green and I can't see a fault in my configuration.

Can anybody else confirm the 1.13.1 release fixes this bug?

@lsh-0 commented on GitHub (Feb 9, 2019): I've just upgraded to 1.13.1, the information pane in the Modoboa admin interface confirms this however my DKIM label is still red with the label `no record found`. https://www.dmarcanalyzer.com gives me all green and I can't see a fault in my configuration. Can anybody else confirm the 1.13.1 release fixes this bug?

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@ObiOnyemaobi commented on GitHub (Feb 9, 2019):

+1.

Fault is still apparent at 1.13.1.

On Feb 9, 2019, at 3:53 AM, LSH notifications@github.com wrote:

I've just upgraded to 1.13.1, the information pane in the Modoboa admin interface confirms this however my DKIM label is still red with the label no record found. https://www.dmarcanalyzer.com gives me all green and I can't see a fault in my configuration.

Can anybody else confirm the 1.13.1 release fixes this bug?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ObiOnyemaobi commented on GitHub (Feb 9, 2019): +1. Fault is still apparent at 1.13.1. > On Feb 9, 2019, at 3:53 AM, LSH <notifications@github.com> wrote: > > I've just upgraded to 1.13.1, the information pane in the Modoboa admin interface confirms this however my DKIM label is still red with the label no record found. https://www.dmarcanalyzer.com gives me all green and I can't see a fault in my configuration. > > Can anybody else confirm the 1.13.1 release fixes this bug? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or mute the thread.

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@tonioo commented on GitHub (Feb 25, 2019):

@lsh-0 @ObiOnyemaobi Can you provide examples? (DNS records)

@tonioo commented on GitHub (Feb 25, 2019): @lsh-0 @ObiOnyemaobi Can you provide examples? (DNS records)

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@ObiOnyemaobi commented on GitHub (Feb 25, 2019):

As with everything, issues take time to figure possibly figure themselves out.
The fault is now resolved on my end. Seems as if the DNS was taking it's time.

@ObiOnyemaobi commented on GitHub (Feb 25, 2019): As with everything, issues take time to figure possibly figure themselves out. The fault is now resolved on my end. Seems as if the DNS was taking it's time.

kerem commented

2026-02-27 11:16:22 +03:00

Author

Owner

@drtrdrs commented on GitHub (Feb 14, 2025):

This issue is still persistent. I have found that my additional domains are not susceptible to this issue, so it seems it is related to the primary domain configured during setup.

@drtrdrs commented on GitHub (Feb 14, 2025): This issue is still persistent. I have found that my additional domains are not susceptible to this issue, so it seems it is related to the primary domain configured during setup.