On 04/08/16 03:50, Jason wrote:
The problem is that the messages being sent are originating from localhost
(a web server), and aren't making an SMTP connection (they're injected via
PHP's mail() function), so a rcpt ACL wouldn't affect these messages.
You could add the verify recipient for the "acl_not_smtp" acls, however
this will be for the whole message no matter how many recipients
involved and is a permanent failure. This may mean that the message is
silently discarded or that an ugly error message is sent to the user of
the php script. An option might be that you could do something like
control=freeze for those recipients that fail to verify so that you
accept the whole message but nothing makes its way to your smarthost.
On Wed, Aug 3, 2016 at 1:47 PM, <[email protected]> wrote:
From: Jason
Is it possible for Exim to verify outgoing mail when using a smarthost?
Specifically, I'm looking to have Exim verify (using dnslookup) that the
domain exists for the recipient.
Besides the router, you need "verify = recipient" (without callout)
in rcpt ACL before accepting the submitting message.
If the domain returns NXDOMAIN (or some
other DNS error), defer it
If the message is submitted by a Windows MUA, it may act weird in response
to
defer.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
