[Gross] Gross not greylisting in postfix properly [?]

[Stefan Förster]

* Justin Piszcz <jpiszcz at lucidpixels.com> wrote:
> Current greylisting with gross:
> 
> Oct 26 04:37:28 p34 postfix/smtpd[11478]: connect from dslb-084-061-200-033.pools.arcor-ip.net[84.61.200.33]
> Oct 26 04:37:28 p34 grossd: #40fdb950: a=greylist d=123 w=3 c=84.61.200.33 s=nicotine at herbalwerks.com r=user at destination.com h=xppe.arcor-ip.net m=zen.spamhaus.org+3
> 
> [ .. ] a later policy/restriction takes over instead [ .. ]
> 
> Oct 26 04:37:28 p34 postfix/geoip[11481]: address[84.61.200.33] country[DE, Germany] result[strictcheckslvl2]
> Oct 26 04:37:28 p34 postfix/smtpd[11478]: NOQUEUE: reject: RCPT from dslb-084-061-200-033.pools.arcor-ip.net[84.61.200.33]: 454 4.7.1 Service unavailable; Client host [84.61.200.33] blocked using dul.dnsbl.sorbs.net; Dynamic IP Addresses See: http://www.sorbs.net/lookup.shtml?84.61.200.33; from=<nicotine at herbalwerks.com> to=<user at destination.com> proto=SMTP helo=<xppe.arcor-ip.net>
> Oct 26 04:37:28 p34 postfix/smtpd[11478]: disconnect from dslb-084-061-200-033.pools.arcor-ip.net[84.61.200.33]
> 
> To fix this same problem in postgrey, one modifies the POSTGREY_OPTS from:
> 
> (Default = DEFER_IF_PERMIT)
> 
> POSTGREY_OPTS="--inet=127.0.0.1:60000"
> 
> To:
> 
> POSTGREY_OPTS="--inet=127.0.0.1:60000 --greylist-action=421"
> 
> So when it gets to the specific restriction in postfix [grossd] it will
> greylist and not continue to the next check.
> 
> Is this possible to get this added into grossd or make the action specifiable?
> So grossd greylists the e-mail first before it gets to the next check?

Set "postfix_response_grey" accordingly (available in version 1.0.1).


Cheers
Stefan
-- 
Stefan Förster     http://www.incertum.net/     Public Key: 0xBBE2A9E9