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.
KumoMTA can manage thousands of IPs and you can have fine control over them. I think you may have misconfigured pools or selection logic. Please include all your configs and data so you can be helped properly.
Please start your own thread instead of adding to this one.
@natural-frog please post YOUR full code and configs so we can help
[source.“ip-1”]
source_address = “172.xx.xx.xx”
ehlo_domain = ‘rowth.com’
[source.“ip-2”]
source_address = “17.x.xx.x”
ehlo_domain = ‘dgrowth.com’
[pool.“pool-1”]
[pool.“pool-1”.“ip-1”]
weight = 2
[pool.“pool-1”]
[pool.“pool-1”."ip-2]
weight = 2
~
kumo.on(‘get_egress_path_config’, function(domain, source_name, site_name)
return kumo.make_egress_path {
max_connection_rate = '100/min',
}
end)
kumo.on(‘get_egress_source’, function(source_name)
return kumo.make_egress_source {
name = source_name,
source_address = SOURCE_TO_IP[source_name],
}
end)
kumo.on(‘get_egress_pool’, function(pool_name)
return POOLS[pool_name]
end)
I am sending mails from main server and relaying them through kumomta and i want kumo to use IP rotation with two IP’s. Now How can i do this
I am new to KumoMTA. THese are the entries of init lua and sources.toml
So many things…
First, this is not your full init.lua. It is impossible to fully diagnose the problem without all of the information.
You are referring to tables POOLS and SOURCES, but you have not populated them with anything.
You have also defined a source.toml file, but not loaded it.
Based on what you have provided, this should not run at all.
I would recommend using the sample configuration with helpers. it is the fastest path to success and it is very easy to implement.
message.txt (9.78 KB)
in the relay host and trusted hosts i mentioned the ip addresses of Main server both the ip’s of relay server.
@natural-frog You have some fundamental code issues in here. Code review is one of the things we charge for as PS work. I can point you to the first obvious one:
get_egress_source event already has a handler defined at @/opt/kumomta/share/policy-extras/sources.lua:92
If you would like us to do a deeper code review and fix issues, you are welcome to bank hours and we can work off that. At a glance, I’d estimate about 3 hours of work to start. If you want to transfer us $750 USD, I’ll add 3 hours to an account for you and start fixing it. Note that this is NOT a guarantee that it will be fixed in 3 hours, but it is a pretty good guess. More complex issues may require more billable time.
The default is 5 hours, but you can adjust it down to 3 in this case: