Every day at 1:20

1

The server seems to be working correctly, emails are being received and sent, both from the account configured in Thunderbird and from the WEB environment itself through Roundcube.

However, every day administrator@box… receives this email:

[box…] Status Checks Change Notice

Traceback (most recent call last):
File “/home/MyAccount/mailinabox/management/status_checks.py”, line 1141, in
run_and_output_changes(env, pool)
File “/home/MyAccount/mailinabox/management/status_checks.py”, line 982, in run_and_output_changes
run_checks(True, env, cur, pool)
File “/home/MyAccount/mailinabox/management/status_checks.py”, line 65, in run_checks
run_network_checks(env, output)
File “/home/MyAccount/mailinabox/management/status_checks.py”, line 286, in run_network_checks
zen = query_dns(rev_ip4+‘.zen.spamhaus.org’, ‘A’, nxdomain=None, retry=False)
TypeError: query_dns() got an unexpected keyword argument ‘retry’

2

It would appear that code was modified about a week ago and that retry argument was added. I’m not sure of the details of this change. Could you check the github repo and see if an issue has been filed, and if not please file one?

3

I see there’s been no new official release since v70, so I don’t think these recent code commits should be running on a production machine yet. I’m curious how you ended up having this code on your system.

4

Mail-in-a-box was installed on the 26th and the administrator has been receiving this message since the first day.

I don’t know anything else. The truth is that the server seems to be working perfectly.

5

I can see there’s an error in the code, and have made a github issue
This code comes from the main branch and should not be installed. It would be good to find out how this code ended up on your Mail-in-a-Box installation. Was the installation procedure followed?

6

I actually tried two installations.

But I’m trying to reference both processes but it won’t let me attach links/URLs because I’m new.

Although I understand both processes do exactly the same thing. With the second process I had reinstalled Ubuntu Server 22.04 LTS to make sure there were no traces of the first installation, although it should also work, but I was missing some configuration in the DNS of the domain used.