Staff Member

sender verification will check that the domain does exist prior to accepting the message. This is typically used as an anti-spam message to cut down on spoofed messages for non-existing sender domains.

Please note there is a difference between using sender verification and sender verification callouts. Callouts actually connect to the remote machine to check an address actually exists. Oftentimes, callouts will cause legitimate emails to be bounced due to policies on the sending machine for such a connection. As such, I would not recommend enabling sender verification callouts, but I would recommend enabling sender verification.

Issue is that I have SENDER VERIFICATION ON and sender verification will check that the domain does exist prior to accepting the message. Domain exists and it is valid. How to solve this as domain is valid but still refused by server. What is exact definition of sender verification...

I'm sorry but under security I can not send domain name. In your opinion this is issue on the sender side server (Microsoft Exchange Server)? Which setting defines this as I thought it was issue with setting on receiver side: SENDER VERIFICATION ON

Staff Member

Does the user exist on that other server? If the user cannot be verified as existing, then the check is going to fail. You could add the IP for that machine to WHM > Exim Configuration Editor > Sender verification bypass IPs area.