On Tue, Aug 03, 2004 at 09:07:29PM -0400, Stephen Gran wrote:
> Note that that is July 14 - you certainly could have had a callout
> cached on the 18th, if that's the case. And since the reject was for
> HELO, everything from that domain was (improperly? - eye of the
> beholder, I guess) cached as a reject.
So the problem is I'm not sure if the cache entry really existed and
was since purged, or didn't exist ever.
I guess it would be helpful to have two messages. Instead of:
550-(result of an earlier callout reused).
Maybe:
550-(result of an earlier host callout reused).
550-(result of an earlier localpart callout reused).
And even better, the timestamp of that earlier callout.
Someone commented that Exim may not wait for the response to the HELO
command. Is there any truth to that? Sounds hard to believe.
Anyway, I looked at the source for the MTA that's having this problem
-- qpsmtpd. Seems qpsmtpd and Exim are confused about the state of
the SMTP connection. Exim logs:
response to "HELO hank.org" from mail.apache.org [209.237.227.199] was: 503 MAIL first
But qpsmtpd, AFAICT, only sends that response to a DATA command.
220 apache.org ESMTP qpsmtpd 0.27.1 ready; send us your mail, but not your spam.
helo me
250 apache.org Hi [63.205.225.170] [63.205.225.170]; I am so happy to meet you.
data
503 MAIL first
Exim doesn't send a DATA command on a sender callout, right?
--
Bill Moseley
moseley@???
