[GH-ISSUE #2931] New Admin: DKIM bind says _domain_key instead of _domainkey #1713

New issue

Closed

opened 2026-02-27 11:18:43 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 11:18:43 +03:00

Owner

Originally created by @fmp777 on GitHub (Mar 24, 2023).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/2931

Just a typo in the new UI. The old UI displays _domainkey correctly.

Originally created by @fmp777 on GitHub (Mar 24, 2023). Original GitHub issue: https://github.com/modoboa/modoboa/issues/2931 Just a typo in the new UI. The old UI displays _domainkey correctly. ![image](https://user-images.githubusercontent.com/2659615/227589093-cf9964e6-2a25-4f79-886b-7863bffb1349.png)

kerem

2026-02-27 11:18:43 +03:00

closed this issue
added the
feedback-needed
label

kerem commented

2026-02-27 11:18:44 +03:00

Author

Owner

@Spitfireap commented on GitHub (Mar 25, 2023):

Hi, this was fixed with #2630 released with 2.0.3. Please make sure your modoboa instance is up-to-date. Also, please follow the new-admin upgrade instructions ;)

@Spitfireap commented on GitHub (Mar 25, 2023): Hi, this was fixed with #2630 released with 2.0.3. Please make sure your modoboa instance is up-to-date. Also, please follow the [new-admin upgrade instructions](https://modoboa.readthedocs.io/en/latest/upgrade.html#new-admin-interface) ;)

kerem commented

2026-02-27 11:18:44 +03:00

Author

Owner

@fmp777 commented on GitHub (Mar 27, 2023):

Hi, thanks!
Hmm well I did all updates that the UI said existed

Up to 2.0.5 - I was on 2.0.3 so I did 2.0.4 and followed the upgrade instructions for that patch, then I did 2.0.5 which had no upgrade instructions. I wasn't sure if modoboa needed a step by step upgrade or a 2.0.5 direct would've worked. I see that docs list 2.1.0 but I supposed that wasn't officially released yet.

I see on the page you linked it mentioned "if you used the installer to upgrade" - I have only ever followed all the pip instructions to upgrade. Is there a document that describes this "installer" method?

@fmp777 commented on GitHub (Mar 27, 2023): Hi, thanks! Hmm well I did all updates that the UI said existed ![image](https://user-images.githubusercontent.com/2659615/228010769-cc67b167-c437-4614-b459-92184b961931.png) Up to 2.0.5 - I was on 2.0.3 so I did 2.0.4 and followed the upgrade instructions for that patch, then I did 2.0.5 which had no upgrade instructions. I wasn't sure if modoboa needed a step by step upgrade or a 2.0.5 direct would've worked. I see that docs list 2.1.0 but I supposed that wasn't officially released yet. I see on the page you linked it mentioned "if you used the installer to upgrade" - I have only ever followed all the pip instructions to upgrade. Is there a document that describes this "installer" method?

kerem commented

2026-02-27 11:18:44 +03:00

Author

Owner

@fmp777 commented on GitHub (Mar 27, 2023):

CONFIRMED: yes after completing the copy of the package new frontend folder, the bug is fixed

@fmp777 commented on GitHub (Mar 27, 2023): CONFIRMED: yes after completing the copy of the package new frontend folder, the bug is fixed

kerem commented

2026-02-27 11:18:44 +03:00

Author

Owner

@Spitfireap commented on GitHub (Mar 27, 2023):

Hi, you can update straight away to the last version, just be sure to follow all specific upgrade instructions. You need also to perform the usual steps on each upgrade.

As for the installer side : it comes with modoboa installer, but you need to have the config file set according to your actual setup, better continue with the manual way ;).

As for the copy, you can use a symbolic link instead of a hard copy, provided that :

you are using a venv created by the same user as the instance (usually modoboa)
you access new-admin the standard way : same server, same domain, just fqdn/new-admin
We'll add a warning if some files require manual editing

And lastly for the 2.1.0 it is indeed prep work for the upcoming release and docs are built against master, we should perhaps improve branching management with a dedicated doc branch (@tonioo)

@Spitfireap commented on GitHub (Mar 27, 2023): Hi, you can update straight away to the last version, just be sure to follow all specific upgrade instructions. You need also to perform[ the usual steps ](https://modoboa.readthedocs.io/en/latest/upgrade.html#modoboa) on each upgrade. As for the installer side : it comes with [modoboa installer](https://github.com/modoboa/modoboa-installer), but you need to have the config file set according to your actual setup, better continue with the manual way ;). As for the copy, you can use a symbolic link instead of a hard copy, provided that : - you are using a venv created by the same user as the instance (usually `modoboa`) - you access new-admin the standard way : same server, same domain, just `fqdn/new-admin` We'll add a warning if some files require manual editing And lastly for the `2.1.0` it is indeed prep work for the upcoming release and docs are built against master, we should perhaps improve branching management with a dedicated doc branch (@tonioo)