On 2018-06-08 18:34, Heiko Schlittermann wrote:
> > > >> 2018-05-29 12:25:40 H=haskell.org [23.253.242.70]:51176 sender verify
> > > >> defer for <haskell-cafe-bounces@???>: Could not complete
> > > >> sender verify callout: mail.haskell.org [23.253.242.70] :
> > > >> response to "RCPT TO:<mymx.com-1527621934-testing@???>" was: 250 2.1.5 Ok
> > > >> 2018-05-29 12:25:40 H=haskell.org [23.253.242.70]:51176
> > > >> F=<haskell-cafe-bounces@???> temporarily rejected RCPT
> > > >> <itz@???>:
> > > >> Could not complete sender verify callout
> > Well OK, but the spec says (43.46):
> >
> > If the “random” check succeeds, the result is saved in a cache record,
> > and used to force the current and subsequent callout checks to succeed
> > without a connection being made, until the cache record expires.
> >
> > Note "current".
> Even for a non-native speaker it seems clear to me. (Or, because I'm a
> non-native speaker ;)
>
> But I'm confused anyway. If the random test leads to the conclusion,
> that the following callouts are wasted effort and considered as
> succeeeded, why does Exim rejects the following RCPT?
>
> Can you paste the relevant port of your ACL?
I simply modified the sender verify acl in the example config:
diff --git a/exim/exim.conf b/exim/exim.conf
index 423de93..5391114 100644
--- a/exim/exim.conf
+++ b/exim/exim.conf
@@ -508,7 +508,7 @@ acl_check_rcpt:
drop
log_message = acl_check_rcpt: $sender_address cannot be verified
- !verify = sender
+ !verify = sender/callout=random
# Insist that any other recipient address that we accept is either in one of
# our local domains, or is in a domain for which we explicitly allow
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
