Greg Earle wrote:
On Dec 17, 2004, Gordon Messmer wrote:
Greg Earle wrote:
In my /path/to/courier/etc/smtpaccess/default file, there is
137.78 allow,RELAYCLIENT,BOFHCHECKDNS=0
Change that to:
137.78 allow,RELAYCLIENT,BLOCK,BOFHCHECKDNS=0
This will set "BLOCK" to an empty value, and your co-worker won't be
blacklisted.
Again, this seems non-sequitur-ish: it seems like the $BLACKLISTS
construct has the same effect ("if blocked in dnsbl.sorbs.net, then set
$BLOCK") - yet doing that causes the block; whereas you're saying if
"BLOCK" is set to an empty value here, it won't. What's the difference?
Courier's SMTP daemon (submit, actually) checks for the existence of the
BLOCK environment variable. If the variable is set, it then checks to
see if the variable is zero-length or not. Only if the variable is set
and is not zero-length will the message submitted be rejected. The
example above would set the BLOCK variable to a zero-length value after
it had been set by couriertcpd. The submit program would then be unable
to see any value that may have been set as a result of BLACKLISTS.
Your previous attempt, where you tried "BLOCK=0" actually set the BLOCK
variable to a value that was one character long, "0".
Indeed it does! Thanks Gordon. This is actually my/our preferred
solution - we'd prefer it if everyone that sent mail out through
our Courier server use Authenticated SMTP anyway. So I think
we'll close this out by having my co-worker leave Authentication
enabled and skip the addition of ",BLOCK" to smtpaccess/default.
Thanks to both of you for your replies.
Glad to help.
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Way to override a...
