4 messages in net.sourceforge.lists.courier-users[courier-users] Any way to override B...
FromSent OnAttachments
Greg EarleAug 21, 2005 2:07 pm 
Sam VarshavchikAug 21, 2005 5:30 pm 
Greg EarleAug 22, 2005 11:11 am 
Gordon MessmerAug 22, 2005 2:04 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Any way to override BLACKLISTS on a per-host basis?Actions...
From:Greg Earle (ear@isolar.DynDNS.ORG)
Date:Aug 21, 2005 2:07:39 pm
List:net.sourceforge.lists.courier-users

Is there some way to override BLACKLISTS on a per-host basis?

I'm still running a setup at home with a front-end relay server accepting mails for my domain and relaying copies to my Courier server (now up to 0.47.0!) on another machine (straight port 25 transfers with no authentication, obviously).

The trouble is, the front-end relay server has a quasi-dynamic IP from Comcast, so if I try to use (lines broken for clarity)

BLACKLISTS='-block=dnsbl.sorbs.net,BLOCK \ -block=sbl-xbl.spamhaus.org,BLOCK \ -block=bl.spamcop.net,BLOCK'

to shoo away other random connections to the back-end server, Courier gets a hit in the SORBS lookup on my incoming relayed mails and it rejects them. I thought I could override this on a per-host basis by having the IP address of the front-end relay server listed in courier/etc/smtpaccess/default (which has

allow,RELAYCLIENT,BOFHCHECKDNS=0

in the entry for the relay server's IP address), but that doesn't seem to override the BLACKLISTS checking.

In the meantime I've temporarily commented out the BLACKLISTS setting, but it would be nice if I could leave it enabled. Is there any way to do this, or does the BLACKLISTS setting have the highest priority and no combination of smtpaccess or any other method can override it?

Thanks,

- Greg