On Sun, 18 Nov 2001, Richard Welty wrote:
> 158.198.23.216.kbl.krusty-motorsports.com. 86400 IN A 127.0.0.2
> 158.198.23.216.kbl.krusty-motorsports.com. 86400 IN TXT "Mail from
> 216.23.198.128/25 blocked - See
> http://www.krusty-motorsports.com/blocked.html"
>
> there's no evidence in rejectlog or mainlog of my lookups being done,
> and a spam from 216.23.198.158 leaked through last night. how do i
> debug this?
Try exim -bh 216.23.198.158 and play the part of an SMTP client if
necessary.
> 2) the connection for the spam that leaked thorugh was a TLS
> connection (i don't know the internal flow, and am only speculating
> that there might be a path by which an inbound email coming in over
> TLS might circumvent the rbl_domains check.)
No, there isn't. One of the reasons for the big upheaval that is Exim 4
is so that there can be such paths for people that want them!
> i have added the particular IP range that leaked to hosts_avoid_tls to
hosts_avoid_tls is an option for outgoing messages.... (or do you mean
tls_advertise_hosts?)
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.