Forwarding Hosts not accepting multiple ip's or DNS resolve in GUI or API

renevs

Hello,

I have a commercial mail filter in front of my mailcow installation and I want to add the ip’s in “Forwarding Hosts” and disable spam checks. In the past I just added in the dns name, and it auto populated itself, but on the current version; 2023-05a it gives a “Invalid host specified:” if I grab the list from the NS, add commas, it returns the same error. looked in API logs, it provides the same language.
{
“type”: “error”,
“msg”: “Request body doesn’t contain valid json!”
}
The above error also comes from Swagger

DNS resolve works on the host and in docker, (just double checked), single ip’s work, more than 1 results in above.

I can add them all one by one, it’s a list of ±75 Ips, so I rather not.
As they also rotate the IP’s it would also be beneficial to allow a DNS name only?

Thanks to anybody that could help me sorting this out!

esackbauer

The quickest approach I can imagine is to whitelist the networks from that provider. Those 75 IPs are maybe in only 5 networks.
Another approach would be to disable spam check if a certain unique smtp header is sent from that antispam service. Maybe in sieve? I dont know.

renevs

Thanks for your reply, I did manual add them already, unfortunately it where more than 5 networks, and then still multiple ip or /n networks did not work, all single IP’s needed to be added in manual. I did add the dns name in my firewall config to be the only one to post, so I might end up indeed disabling the filter.
I was/i’m just annoyed the function is not working anymore, where it was in the past.

Thanks!