Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HFILTER_HOSTNAME_UNKNOWN always triggers #2014

Closed
langerc opened this issue Nov 16, 2018 · 3 comments
Closed

HFILTER_HOSTNAME_UNKNOWN always triggers #2014

langerc opened this issue Nov 16, 2018 · 3 comments

Comments

@langerc
Copy link

langerc commented Nov 16, 2018

I have 3 instances of mailcow up and running in different datacenters.

The spam rule HFILTER_HOSTNAME_UNKNOWN always triggers and adds spam rating to mails that should not have it.

So every mail, does not matter if the host that sent the mail is good or bad will get the
HFILTER_HOSTNAME_UNKNOWN(2.50)[]
added to its spam score which puts a lot of mails into spam.

The dns status page shows that the local mailserver has a correct ptr record.

If i attach myself to the unbound docker instance (exec ..) and use nslookup to ask for the ptr record of the remote mailserver that was marked as invalid the ptr record resolves correct.

Expected behavior
A domain that has a valid ip / namemapping should not be marked as hostname unknown

System

  • ubuntu 16
  • docker
@andryyy
Copy link
Contributor

andryyy commented Nov 16, 2018

Hi,
Can you post a mail or multiple mails with this score?

@langerc
Copy link
Author

langerc commented Nov 16, 2018

i just found a thing - i use a smtp proxy that does antivirus and antispam in front of the mailserver seems there is an internal ip that was not mapped. i mapped it and will doublecheck in a few hours.

Received: ⁨from firewall (unknown [x.x.x.x]) - this might cause the problem.
i dont want to add the ip to the relay hosts because i would like mails to be analized parsed and sorted by mailcow.

@stale
Copy link

stale bot commented Jan 15, 2019

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.

@stale stale bot added the dunno label Jan 15, 2019
@stale stale bot closed this as completed Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants