Re: [Exim] Message: "result of an earlier callout reused"

Tim Jackson <lists@???> wrote:
> Hi Bill, on Mon, 26 Jul 2004 16:56:50 -0700 you wrote:
>
>> Digging better into my logs I'm seeing a few failures from apache.org
>> that include details of a SMTP callout rejection. All are "503 MAIL
>> first":
>> rejectlog.12.gz:2004-07-14 23:38:54 H=(minotaur.apache.org)
>> [209.237.227.194] sender verify fail for
>> <dev-return-8076-apmail-moseley=apache.org@???>:
>> response to "HELO hank.org" from mail.apache.org [209.237.227.199]
>> was: 503 MAIL first
>
> Aha. I'm stabbing in the dark a bit here, not being an avid user of
> the sender callouts. However, notice that this rejection is in
> response to the *HELO* command! Looks like a temporary
> misconfiguration at apache.org, or a weird way of them saying they
> don't like "hank.org" as a HELO (is your machine *really* hank.org?).
> Either way, it seems possible (likely, even?) that Exim is
> (reasonably enough) caching this HELO rejection. A rejection at HELO
> time means that *no* recipients are going to get through, and
> therefore Exim is actually behaving correctly, even though it hasn't
> seen the precise sender in question before.

Yes, I'm with Tim here - I think a bad response to HELO will make Exim think
that any callout in the domain it was trying to callout to will fail, so the
caching code optimises out any further callouts.

You may need to bypass sender callouts for the bad domain to get round this.

Peter