Rspamd rejecting all emails. HFILTER_HOSTNAME_UNKNOWN #5868
Comments
|
Having the same issue. Ever since the last update all of my incoming external mail is getting rejected. |
|
Following all of the steps here: https://docs.mailcow.email/post_installation/firststeps-disable_ipv6/ |
|
We don't provide support here on GitHub |
|
Hi. I'm not looking for support. It was very easy to update rspamd settings for emails to get through. Had a little time to test. I was running Downgraded to Downgrading to If You want to label it upstream. Or close it if it's not specific to mailcow in general. @jacksonwilliams in case you want to downgrade gist |
|
Network is the issue, not container Version |
|
Ran into this problem after upgrading from
|
Hi @superstes You incorrectly using mail system, this is an issue. Symbol you specifically see says that your mail gateway don't have Helo=A=PTR setup, but this only half of issues external mail gateway is creating as Mailcow doing everything correctly, by extra host you break spf as well as ip reputation and rbls checks as rspamd not aware about origin ip. You or must set mailcow to be direct MX or need to configure rspamd external relay module property so it can parse orgin ip and hostname details from received header instead of that which provided by postfix's milter protocol. Having extra mail gateway in front of mailcow in most cases is providing significantly worse filtration quality then not having it at all. My personal recommendation is to better take an eye on proper learning & configuration of existing rspamd then taking care about 2 independent spam filters one of which even not aware about mails could be rejected on the way - this is direct way to be a backscatters spreader which is very bad to be... While rspamd not receiving properly all spam that it going to reject anyway because some spam would be rejected by first mta - it leaves without big portion of source to learn itself to better filter new spam that could be unknown to rbls and so on, so this greatly lowers it's detection quality. More over rspamd that shipped into mailcow has a bunch of features like spamtraps, alias expansion, sogo address book auto whitelist, quarantine and so on that external spam system usually can't provide at all or at least in same useful way as it exists in Mailcow. I not speaking about rspamd itself even, in my personal opinion it's the best antispam open source solution that you can find today from terms of filtration quality, extensibility, flexibility and performance. If you still want to use external antispam solution - another option is just add multimap prefilter in rspamd that will instantly accept any incoming mail from your's gateway ip, which will basically turn off any incoming antispam checks in rspamd. I would then also explicitly disable all rbls checks in both postscreen and rspamd and all other modules of rspamd except arc & dkim signing to reduce unnecessary compute resources usage from yourself and external systems while not break dkim signing which done by rspamd. |
|
I see this tread is abused a bit... Dear users, please:
I will lock conversation on this issue to not create a mess. |
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12 bookworm
Server/VM specifications:
10Gb memory. 1 x 1.7GHz core
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
Proxmox KVM
Docker version:
26.1.1
docker-compose version or docker compose version:
v2.27.0
mailcow version:
2024-04
Reverse proxy:
Nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: