On Sat, 8 Jun 2002, Andy Coy wrote:
> Yes but if you look at the line above I have the same but without the sql
> bit.
Sure, but the debug output still points to a MySQL db lookup (which
fails).
> I know that, but it looks like a reverse DNS error, I was woundering if that
> was the problem.
# dig -x 80.40.0.178
; <<>> DiG 9.2.1 <<>> -x 80.40.0.178
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50990
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;178.0.40.80.in-addr.arpa. IN PTR
;; ANSWER SECTION:
178.0.40.80.in-addr.arpa. 604800 IN PTR
ppp-5-178.london-b-cvx-1.access.as9105.com.
Funky rDNS there, but I don't think it'll give Exim problems.
> I don't believe so as this worked for 2 1/2 years b4 the new IP's came
> online. Also it continues to go through with non sql checks b4 relay is
> denied.
>
> Yes each time I edited it.
Well, it's still doing a MySQL lookup, and as Dave pointed out, the host
with the address 80.40.0.178 isn't in your host_accept_relay, so things
point to an editing mistake. Do you have stray exim.conf files on your
system?
--
Juha Saarinen
