Greylisting?

[angussf]

Search the forums for "greylist" and didn't see it. This would be a Good Thing to have available.

[sjau]

Search the howtos and you will finde one

[angussf]

All the HowTos are for adding PostGrey to Postfix, but do not show how to integrate this in with ISPconfig. That's what I was looking for.

[till]

A greylisting service must be integrated in postfix as postfix is the mailserver. ISPConfig is just a controlpanel and the greylisting seamon works in a step of the email process before any ISPConfig scripts are involved.

[angussf]

Originally Posted by till

A greylisting service must be integrated in postfix as postfix is the mailserver. ISPConfig is just a controlpanel and the greylisting seamon works in a step of the email process before any ISPConfig scripts are involved.

Perhaps, but for resellers or clients to control it (turn it on and off, change settings), they need to be able to configure it. From the HowTo Killing That Spam With Postgrey And Postfix http://www.howtoforge.com/greylisting_postfix_postgrey

...
Configure Postfix

The Postfix configuration files are located in /etc/postfix. Edit /etc/postfix/main.cf and add check_policy_service inet:127.0.0.1:60000 to the smtpd_recipient_restrictions. It should look something like this :

smtpd_recipient_restrictions = permit_sasl_authenticated,
permit_mynetworks,
reject_unauth_destination,
check_policy_service inet:127.0.0.1:60000

I don't see that this is configurable using ISPconfig ...

[AlArenal]

Originally Posted by angussf

I don't see that this is configurable using ISPconfig ...

That is right and it is intended, because it's not ISPConfig's job. ISPConfig is responsible for managing web/ftp/mail accounts, but it has nothing to do with configuring addons to services.

Best kept secret is, that God was disappointed with his creation and chose to create the sysadmin the sixth day. That's why he could afford to have a day off on sunday...

[till]

Originally Posted by angussf

Perhaps, but for resellers or clients to control it (turn it on and off, change settings), they need to be able to configure it. From the HowTo Killing That Spam With Postgrey And Postfix http://www.howtoforge.com/greylisting_postfix_postgrey

...
Configure Postfix

The Postfix configuration files are located in /etc/postfix. Edit /etc/postfix/main.cf and add check_policy_service inet:127.0.0.1:60000 to the smtpd_recipient_restrictions. It should look something like this :

smtpd_recipient_restrictions = permit_sasl_authenticated,
permit_mynetworks,
reject_unauth_destination,
check_policy_service inet:127.0.0.1:60000

I don't see that this is configurable using ISPconfig ...

This can not be configurable in ISPConfig for clients and resellers because greylisting is activated once for the whole server (see your config snipped above) and can not be configured on a reseller / client basis because there is nothing to be configured. The greylisting daemon does not know what a client or reseller is, so we can not enable / disable greylisting on a reseller or client basis.

[cusco]

Hi,

I was just googling fro ispconfig + greylist and came across this thread.

We have a machine with ispconfig with a few domains and mailboxes in there, for some of our clients. However, for us, we use Exim + Dovecot with MySQL with setup idea taken from http://struction.de/projects/HOWTO_V...lamAV-Dovecot/

In this link, you find that exim does not need greylisting daemon. It simply stores the ip and e-mail address whenever a e-mail comes in, wlong with timestamp.

When the e-mail comes back in, it checks if there is a mysql row, the timestamp and if <treshhold time> minutes have past


Could this be implemented in ispconfig? A main postfix ACL that for every e-mail it checkes a greylist (AND NOT IN whitelist) table, and rejects temporarly if time treshhold is not yet reached???

(hope you can understand what I mean)