Greylisting with Postgrey

[Thibs]

Hi all,

I'm a french user of ISPCP 3 and i have successfully integrated Postgrey with Postfix.
For me, the utility of Postgrey is to reduce ressource load of amavis when filtering spam.
I have a small server which received a lot of mail, and amavis make a high load on cpu, 70% constant with the spam filtering.
With Postgrey, i have reduced the load of cpu to 30% constant.
The conf was easy, just three config files, and if possible to integrate with ISPCP is to enable or disable postgrey per mail domain and per user, and perhaps give the user the ability to write blacklist and whitelist of sender.

I can confirm that Postgrey works like a charm with ISPCP 3.0.1.3.

See you soon !!!

Thibs

[Ben]

General question, do you use blacklisting at all? As it looks like you are using greylisting to prevent some mails beeing "dropped" by your server to avoid spam mails to be scanned by clamav and thus reducing the overall load.
Nevertheless, after using greylisting for 3 years, from my point of view it is kind of outdated as it reduces the overall spam at a maximum of 10%.
More helpfull for reducing spam for me was balcklisting and denying emails from dynamic hosts based on the reverse dns name (eventhough most of them are covered by the blacklists as well).

[grungy]

I want to implement this too, since I am using ISPConfig Version: 3.0.2 is this implemented already? I see there is a mysql table named mail_greylist

[kinai]

sqlgrey will be a better solution in a multi-server installation.
sqlgrey use a mysql database to store database vs postgrey that use a berkley database.

[sh1ny]

I would suggest using policydv2 . I use it on a quite large smtp setups ( somewhere around 700-800 msgs/min ) and it does it job extremely well, not ot mention the functionality