Mailu: DNS and Dkim Problem

[a1ekseev]

In the anti-spam logs, I get these messages
24.09.2019, 11:18:00 | rspamd_proxy | 6 | proxy | ea17f2 | cannot load dkim key /dkim/gmail.com.dkim.key: cannot stat key file: '/dkim/gmail.com.dkim.key' No such file or directory -- | -- | -- | -- | -- | -- 24.09.2019, 11:13:36 | controller | 8 | map | fdp86m | cannot resolve maps.rspamd.com: query timed out 24.09.2019, 11:07:43 | controller | 8 | map | f61zu5 | cannot resolve maps.rspamd.com: query timed out 24.09.2019, 10:43:39 | rspamd_proxy | 6 | proxy | 6a4515 | cannot load dkim key /dkim/yandex.ru.dkim.key: cannot stat key file: '/dkim/yandex.ru.dkim.key' No such file or directory 24.09.2019, 10:43:01 | rspamd_proxy | 6 | proxy | a2ab83 | cannot load dkim key /dkim/gmail.com.dkim.key: cannot stat key file: '/dkim/gmail.com.dkim.key' No such file or directory 24.09.2019, 10:25:29 | rspamd_proxy | 6 | lua | bd13df | Error querying DNS(79b02fcb6777cde57178ac941273706740344a80.ebl.msbl.org): query timed out 24.09.2019, 10:25:29 | rspamd_proxy | 6 | lua | bd13df | Error querying DNS(fo1wk7518dya4hdfz8g3g7zdfb1c35yw.email.rspamd.com): query timed out 24.09.2019, 10:25:29 | rspamd_proxy | 6 | lua | bd13df | Error querying DNS(qu96fwbu1qxunkig79rpxczqoj7be4ru.email.rspamd.com): query timed out 24.09.2019, 10:25:29 | rspamd_proxy | 6 | lua | bd13df | Error querying DNS(a5f235fe09bd538afb3515a78f2462e510d415af.ebl.msbl.org): query timed out 24.09.2019, 10:16:21 | rspamd_proxy | 6 | lua | aa1a3a | Error querying DNS(fo1wk7518dya4hdfz8g3g7zdfb1c35yw.email.rspamd.com): query timed out
What could be the problem?

[blogwebpl]

I have similar problem:
antispam_1 | 2019-10-27 14:39:37 #10(controller) <zcfokz>; map; rspamd_kv_list_fin: read hash of 1531 elements antispam_1 | 2019-10-27 14:39:42 #10(controller) <fdp86m>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com antispam_1 | 2019-10-27 14:39:42 #10(controller) <k8f914>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com antispam_1 | 2019-10-27 14:39:42 #10(controller) <k8f914>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com antispam_1 | 2019-10-27 14:39:42 #10(controller) <fdp86m>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com antispam_1 | 2019-10-27 14:39:42 #10(controller) <xa6qqy>; map; rspamd_map_dns_callback: cannot resolve rspamd.com antispam_1 | 2019-10-27 14:39:42 #10(controller) <pr5857>; map; rspamd_map_dns_callback: cannot resolve updates.rspamd.com antispam_1 | 2019-10-27 14:39:42 #10(controller) <fdp86m>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com

I run iptables -t nat -A POSTROUTING ! -o docker0 -s 192.168.203.0/24 -j MASQUERADE
and now it is working.

[kaiyou]

Many of these problems are indeed related to people having way too general outbound masquerading rules.

You should never masquerade internal traffic to your Docker. Please use specific masquerading rules. Also, blogwebpl's suggestion will not hold since compose projects will have their own host interface instead of docker0.

[marienfressinaud]

Hi! I think you answered to the DNS errors problem, but there is still the issue with the dkim keys which cannot be loaded. I have the exact same issue:

cannot load dkim key /dkim/gmail.com.dkim.key: cannot stat key file: '/dkim/gmail.com.dkim.key' No such file or directory

It seems pretty normal for rspamd to not be able to find these keys since there are for external domains. It looks identical to this issue, so I bet for a configuration issue (here?). I'm not sure about the reason to use fallback, and even less about the implication of keeping it as it is or not, so I'll let you answer that :wink:

[kaiyou]

Thanks for insisting on the issue about falling back. This might be an easy fix indeed.

[Nebukadneza]

Hi There,

The Mailu-Project is currently in a bit of a bind! We are short on man-power, and we need to judge if it is possible for us to put in some work on this issue.

To help with that, we are currently trying to find out which issues are actively keeping users from using Mailu, which issues have someone who want to work on them — and which issues may be less important. These a less important ones could be discarded for the time being, until the project is in a more stable and regular state once again.

In order for us to better assess this, it would be helpful if you could put a reaction on this post (use the :smiley: icon to the top-right).

• 👍️ if you need this to be able to use Mailu. Ideally, you’d also be able to test this on your installation, and provide feedback …
• 🎉 if you find it a nice bonus, but no deal-breaker
• 🚀 if you want to work on it yourself!
  We want to keep this voting open for 2 weeks from now, so please help out!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[karlisk]

Ran into this issue, my fix for the DKIM problem was to generate the Rspamd dkim key file.

docker exec -it mailu_antispam_1 /bin/bash rspamadm dkim_keygen -s 'dkim' -d example.com -k /dkim/example.com.dkim.key

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.