-
Notifications
You must be signed in to change notification settings - Fork 135
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
relay abuse through SRS #316
Comments
It looks like you have an open relay due to misconfigured networking on your kubernetes. You excluded the most interesting part of the log, where the bad guy connects to you postfix. My bet would be that these excluded line tell you that connection comes from 127.0.0.1. You need to find out why and rectify it.
A specific advice cannot be given here as it depends, on what how network is setup and configured within your cluster and how connectivity from the bad guy to your pod actually works, you need to experiment a bit and trace how that happens. If you google a bit, you will find a lot of similar reports for docker / kubernetes setup with other popular container based mail server implementation, which are also due to networking misconfiguration. A couple of examples: |
Hi, Thanks for the reply, the network configuration is done thanks to the service embedded in the helm charts, the only change I've made is to turn the daemonset/nodeport into a replicaset/loadbalancer : The "connect from localhost" message has nothing to deal with the problem, it's due to the liveness probe connecting every 10 seconds to check if server is still alive (this is also part of the helm deployment) I've created this issue as requested by Kayou :
|
Sorry, I meant kubernetes networking configuration, not the one specific to mailu as per helm chart.
Yep, that checks, yet the most interesting part of the log is missing. |
Pinging @kaiyou as apparently this was discussed on Matrix. |
Hi There, The To help with that, we are currently trying to find out which issues are actively keeping users from using In order for us to better assess this, it would be helpful if you could put a reaction on this post (use the 😃 icon to the top-right).
|
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. |
Hi all,
I had a strange case of thousand of mails being relayed by mailu for a user that does'nt exist, here are the logs from postfix:
User [email protected] does'nt exist, I don't know ow this manage to get through.
I'm running the helm deployment on a kubernetes 1.17.2 :
root@k8p1:~/helm_charts/mailu/mailu# cat Chart.yaml apiVersion: v1 appVersion: "1.8" description: Mailu mail system name: mailu version: 0.0.6
Cheers,
The text was updated successfully, but these errors were encountered: