Then I added the email address and IP of the sender server to the whitelist /etc/exim4/white-blocks.conf
Unfortunately, this didn’t help.
I know that this e-mail address is incorrect, the mail domain is incorrect, but I really need to receive mail from it.
The admin on the other side is unavailable and it is impossible to reconfigure sending mail.
Yesterday, before migrating to hestiacp, the whitelist worked fine.
What am I doing wrong?
Thanks a lot!
The whitelist function itself is for spam detection or/and blacklists, the sender verify will be triggered always. You could now rewrite this function to also honor the ip whitelist for sender verification, a short google search gave me a lot of results, here a untested example: http://bohwaz.net/p/Exim-whitelist-senders-to-pass-the-sender-verify-callout
It looks but…
On the old server running ispmanager 5, the config also has this line.
require verify = sender
And everything worked fine there.
Well, thank you.
A couple of things suggest themselves. First of all, shouldn’t you be making edits in /etc/exim4/exim4.conf.template, rather than in conf.d/ ? At least thats where I make all my config changes.
Secondly, just a vague memory that if you add an address to an exim filter, and its a regex search, you’d have to backslash the dots in the domain name. So your examples above might have to be
Great. I see the forum editor removed the backslashes from my previous post, so that might have been a bit confusing. I’ve added them back in now. But it looks like it wasn’t the regexs, but the other reason anyway … glad it worked out.
Can anyone explain this? I’d like to whitelist an MX that keeps getting refused to deliver mail to my hestia controlled exim server.
It’s truly amazing how bad exim’s documentation is. It’s just completely unclear how to even whitelist anything. Why did you pick exim? Please, change back to postfix if or whenever possible. Exim is really disasters waiting to happen.