KumoMTA is connecting to proxy, but mails are not delivered. I am using port 2016 for proxy.
When I run this command :- journalctl -n50 -u kumomta.service | grep “socks5”
Logs :-
source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“socks5_proxy_source_address”:“172.33.33.33”}
source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“name”:“ip-1”}
source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“socks5_proxy_source_address”:“172.33.33.33”}
source ip-1: {“name”:“ip-1”,“ehlo_domain”:“growth.com”,“socks5_proxy_source_address”:“172.33.33.33”,“socks5_proxy_server”:“172.33.33.33:2016”}
source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“name”:“ip-1”}
source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“name”:“ip-1”}
source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“socks5_proxy_source_address”:“172.33.33.33”}
source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”}
source ip-1: {“name”:“ip-1”,“socks5_proxy_source_address”:“172.33.33.33”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”}
source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”,“socks5_proxy_server”:“172.33.33.33:2016”,“name”:“ip-1”}
source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”}
Hey there @natural-frog, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.
Your grep is possibly removing relevant entries near the lines you show.
Add a -A5 to your grep so you can see a few lines after the socks5 line. Your error is likely exposed AFTER those lines you shared.
May 23 04:20:14 growth.com kumod[459]: source ip-1: {“ehlo_domain”:“growth.com”,“socks5_proxy_server”:“172.33.33.33:2016”,“name”:“ip-1”,“socks5_proxy_source_address”:“172.33.33.33”}
May 23 04:21:14 growth.com kumod[459]: source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”}
May 23 04:22:14 growth.com kumod[459]: source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”}
May 23 04:23:14 growth.com kumod[459]: source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”,“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”}
May 23 04:23:54 growth.com kumod[459]: pool rotation: {“name”:“rotation”,“entries”:[{“weight”:1,“name”:“ip-1”}]}
May 23 04:24:14 growth.com kumod[459]: source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“socks5_proxy_source_address”:“172.33.33.33”}
May 23 04:26:54 growth.com kumod[459]: pool rotation: {“name”:“rotation”,“entries”:[{“name”:“ip-1”,“weight”:1}]}
May 23 04:27:54 growth.com kumod[459]: source ip-1: {“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”,“socks5_proxy_source_address”:“172.33.33.33”}
May 23 04:28:54 growth.com kumod[459]: source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”,“ehlo_domain”:“growth.com”}
May 23 04:29:54 growth.com kumod[459]: source ip-1: {“socks5_proxy_server”:“172.33.33.33:2016”,“name”:“ip–1”,“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”}
May 23 04:32:54 growth.com kumod[459]: source ip-1: {“socks5_proxy_source_address”:“172.33.33.33”,“ehlo_domain”:“growth.com”,“name”:“ip-1”,“socks5_proxy_server”:“172.33.33.33:2016”}
Here are some of the logs without using grep with journalctl
Are you using the Kumo proxy or another proxy?
i have another socks server and connected kumo with it.
We have found that most Socks5 proxies seem to have a problem passing email traffic. The KumoSocks proxy was specifically designed to handle email. You would be well served to install it instead.
To be clear, I personally have not had success with any Socks5 proxy other than our own.
But the KumoProxy works like a dream and it is very easy to install and run
could you please tell me about it’s installation and configuration?
Sure.
The easiest way to deploy is to install a minimal KumoMTA install (docker container is likely easiest.) then execute the proxy from the s in directory.
That’s it. KumoProxy will proxy anything you send to it transparently
So, i have to install minimal kumomta in a docker container and run this command /opt/kumomta/sbin/proxy-server --listen IP:Port
You don’t have to use docker, it is easier for some people. When I use it, I just do a normal dev install like this :
And don’t even bother updating the config. Then run the proxy like this:
/opt/kumomta/sbin/proxy-server --listen IP:Port
In the future, it will be much easier to install. For now, it lives with the main MTA code.
Even though the MTA does not even need to be running
I am setting up my KumoMTA to relay mails from another mail server. It was working perfectly along with IP rotation (mails were sent by two round-robin rotating IPs), but now I want to use proxy so I an attach multiple IPs to proxy since there is a limit of network interface or IPs you can attach to an AWS server. I installed kumoMTA initially (not dev version) but when I install dev version it masks my kumomta.service. I tried using dante-server as a socks5 proxy (in aseperate new AWS Server) but only connections were made between kumomta and dante but mails were not delivered.
Even if I install dev version and run “/opt/kumomta/sbin/proxy-server --listen IP:Port” it outputs nothing just a blinking cursor. Also which IP and port do I enter here?
My end goal is to use multiple IPs for proxying so how can kumoMTA help in that?
are you tryong to run the proxy on the same server as kumomta?