On 8/2/2011 9:32 AM, Wietse Venema wrote:
> Jeetu:
>> i get this in log
>> Aug  2 17:27:52 inbound-in-1 postfix/postscreen[24480]: NOQUEUE: reject: 
>> RCPT from [x.x.x.x]:17847: 550 5.7.1 Service unavailable; client 
>> [x.x.x.x] blocked using zen.spamhaus.org; from=<s...@xxx.com>, 
>> to=<ka...@yyy.net>, proto=ESMTP, helo=<d124252.upc-d.chello.nl>
>> Aug  2 17:28:30 inbound-in-1 postfix/postscreen[24480]: NOQUEUE: reject: 
>> RCPT from [y.y.y.y]:33109: 550 5.7.1 Service unavailable; client 
>> [y.y.y.y] blocked using zen.spamhaus.org; from=<f...@yyy.com>, 
>> to=<sippr...@zzzz.net>, proto=SMTP, helo=<www5.nederlandweb.nl>
>>
>> i want the spamhaus.org URL in the logs, how do i achieve it ?
> 
> If in doubt, read the fine documentation. As documented, postsceen
> currently does not have any controls to format the DNSBL reply
> (other than aliasing the DNSBL domain name).

I think some folks have allowed themselves to believe that postscreen is
a total anti spam solution due to feature creep late in development.
They forget its design goal was simply to keep bots from tying up smtpd
processes.

Jeetu, if you need this particular rejection text, the solution is
simple:  use zen in smtpd_foo_restrictions as you did historically, and
remove it from your postscreen config.  One half of the Zen list is
comprised of the PBL and CBL, which target bot spam.  Postscreen does
pretty well here by itself.  I'm sure you can sacrifice a few smtpd
processes to combat the snowshoe, and hard core spammers on 'bullet
proof' hosting.  Your system handled this before Postscreen.

-- 
Stan

Reply via email to