-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Nice Project #6
Comments
Limitshttps://www.postfix.org/TUNING_README.html Linux kernel parameters can be specified in /etc/sysctl.conf or changed with sysctl commands: fs.file-max=16384 /etc/sysctl.conf |
:-(, UnixSock and TCP, Connection timed out warning: problem talking to server private/isp-policyd: Connection timed out |
Hi @jniltinho, I frankly haven't worked with PPS in a long time, so it's hard to tell out of the box, especially given that it's hard to replicate your environment. But yes, it sounds like you might be running into kernel limits here, indeed. There is also a Postfix tuning guide, not sure if you already checked that out: https://www.postfix.org/TUNING_README.html PPS is already making use of Go routines, so I am not sure if there is optimization potential there, but I'll have a look in the next days if there is maybe something I can tweak. |
I already corrected these parts of limits, I don't think that's it https://github.com/bejelith/policyd/tree/main/pkg/handler https://github.com/d--j/go-milter
|
|
Hi @wneessen I created a Simple TCP Daemon to check if the same problem occurs, I'm not having the same problem, the stream and connections are occurring without any errors.
|
Interesting. Out of curriosity, could you test your environment with the simple echo server that is provided with PPS? https://github.com/wneessen/postfix-policy-server/blob/main/example-code/echo-server/main.go and see if it causes the same timeouts in your high-traffic environment? |
I was already testing the Echo Server a few days ago when I came across this problem, so I did a simple test with this code and it worked correctly and is still running in the environment, I already got another code for the server which is this one with the settings , now I'm going to try to mix your project's code a little with my new Server, but now I understand better how it works, because I already knew how it works with Perl, I really appreciate your project, congratulations. https://gist.github.com/jniltinho/8ff31a444c9aa44d048b747dfc4ecf91
|
Hi, @wneessen
These errors appear constantly, policyd often stops working, I still don't know the reason, I've already done the tests with Golang 1.17, 1.18, 1.19,1.20 and 1.22,
I made some adjustments to Postfix.
postfix/smtpd[1270100]: warning: problem talking to server 127.0.0.1:11066: Connection timed out
postfix/smtpd[1270100]: warning: problem talking to server 127.0.0.1:11066: Connection timed out
Recipient address rejected: Server configuration problem;
Recipient address rejected: Server configuration problem;
postfix/smtpd[1272995]: warning: problem talking to server 127.0.0.1:11066: Connection timed out
I'm testing your project in an environment with a lot of email reception, I'd like to know how I can achieve this result here.
I receive many connections, it is constantly giving timeout, there is no way you can add go routines to accept a greater number of connections thus avoiding the timeout.
https://github.com/bejelith/policyd/blob/main/pkg/acceptor/acceptor_linux.go
https://github.com/d--j/go-milter
The text was updated successfully, but these errors were encountered: