On 27/05/2023 22:32, steve-ALUG@hst.me.uk wrote:
On 27/05/2023 20:23, steve-ALUG@hst.me.uk wrote:
On 24/05/2023 18:57, mick wrote:
Steve Possibly you were using spl/xbl at spamhaus. I used to. See https://www.spamhaus.org/zen/ for the reasons to change.
Hmmm. Deeply perplexing.
the spamhaus check doesn't seem to be checking.
I've tried various configurations but it's not showing up as rejecting anything in my log.
Anyone care to comment on the exim syntax? A or B I've seen examples of both.
A) drop message = REJECTED - ${sender_host_address} is blocklisted dnslists = zen.spamhaus.org
B) drop message = REJECTED - ${sender_host_address} is blocklisted dnslists = zen.spamhaus.org/<;$sender_host_address;$sender_address_domain
Drop or Deny I gather they're similar. Deny logs and doesn't accept; drop does that and forcibly drops the connection, I think.
I've just had a spam email from 239.1.70.111 111.70.1.239.
dig +short TXT 239.1.70.111.zen.spamhaus.org responds "https://www.spamhaus.org/query/ip/111.70.1.239"
showing it's listed and should be dropped.
Or is it simply that it's checking all of the recipients before it gets to the RBL check?
Any thoughts?
Steve
Possibly have a reason why it's not working...
https://uribl.com/refused.shtml
Well, same problem, different product. It *MAY* be that my request to Spamhaus is going via a big name server, and spamhaus is saying, "nope, you're too big, this is for personal use".
I believe a solution is to use a caching name server. I do, but it's pointing at a big name server... So, I've overridden the Name Server for spamhaus to point to a smaller name server. We'll see....
Fingers crossed.
OK - Progress. The DNS fix has resulted in the spamhaus test triggering.
That's good. It's still going through all the unknown "to" emails first and rejecting them, and them hitting the spamhaus test. Just need to work out how to get it to hit the spamhaus one first....
Steve