castaway
commented
2 years ago The main issue here seems to be that the DKIM setup is done via the web ui, but the generating of the initial keys is triggered by the same "every few minutes" background run, which also rotates the keys if necessary - thus it can be 0-5 minutes before the dkim page lists anything (the page only lists generated keys)
Possible fixes (we can do more than one):
- Make the dkim page display the domain status even if the keys have not yet been generated (and add "generating keys ..." to it)
- Make the dkim page generate the first set of keys instead of waiting for the background code to run, polling until this is done (or timing out and reporting an error if not possible)
gtandersen
runboxdave
Describe the bug When setting up DKIM for a domain the customer is required to add DNS records for the DKIM keys. As part of the set up process we have a table which shows whether the DNS records are present and correct. However, this often doesn't update once the customer has set up the DNS records and they are left believing they have done something wrong and wasting time trying to fix the issue. Eventually this can lead to a support request.
To Reproduce This is the URL where the checks are visible to the customer: https://runbox.com/app/dkim
Expected behavior I am not sure the current method of using an updating table is really suitable in the first place and we may be better off with something more like the feature for checking the MX record is correct (see https://runbox.com/mail/account_domain_status) as this would provide immediate and obviously up to date information on the status of the expected DNS records.