Re: [exim] Temporary reject when random sender verification …

Top Page
Delete this message
Reply to this message
Author: Heiko Schlittermann
Date:  
To: exim-users
Subject: Re: [exim] Temporary reject when random sender verification should succeed
Ian Zimmerman via Exim-users <exim-users@???> (Do 07 Jun 2018 19:30:34 CEST):
> On 2018-06-07 16:44, Jeremy Harris 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?

    Best regards from Dresden/Germany
    Viele Grüße aus Dresden
    Heiko Schlittermann
-- 
 SCHLITTERMANN.de ---------------------------- internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --------------- key ID: F69376CE -
 ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -