Good IPConfig 3.1, but ...

I don't have a problem with much spam coming through on my ISPConfig servers and ISPConfig 3.1 has integrated postgrey already, you just have to install postgrey on your server, run a reconfigure services to configure it in postfix and then you can enable it in the mailbox settings. If you have a problem with too much spam coming trough, then you should check the mail headers of the mails to see which scores they got and adjust the score of the policy that you selected for the emails. You can also install additional spamassassin rules, if you like. You should then add some realtime blacklists under system > server config > mail. And if you run postfix 2.8 or newer you can use postscreen as well, just enable it in master.cf, there are no changes in ispconfig required.

 

I said postgrey is already integrated in ISPConfig 3.1.

Postgreay is a Greylist daemon.

For what do you want to wait? The ISPConfig version 3.1 that includes postgrey support has already ben released on September 27 and I posted above how to enable it on your server if the server was not installed by using the perfect server guide for ISPConfig 3.1.

 

I understood that your server has a problem with spam filtering, right? Or why else would you suggest to add improvements in the spam filter when it is already working perfectly on your server? I told you that improving the spam filter on a system is a matter of choosing the right settings without the need for any changes in ISPConfigand I posted you hints on how to improve the filtering on your system. But if the spam filtering on your system works already perfectly, then I misunderstood your post.

 

I'm not upset at all. You just did not seem to have read my answers and it is annoying to have to say the same things several times in the same thread.

A reconfiguration of the services is required on a major version update and an update from 3.0 to 3.1 is a major update. And I I already explained above, you have to install postgrey before you do that, on Debian and Ubuntu, that's just:

apt-get install postgrey

and thats described in the latest perfect server setups for ISPConfig 3.1 as well.

There are no manipulations required in any way, I just suggested various settings for you, which are completely independent from ispconfig, on how you can improve the spam filtering for your server.

For example, postscreen requires it that all clients connect to port 587 to send email and not port 25 anymore and you need at least postfix 2.8 which is not installed on all systems, so you can only enable it on systems where you made sure that nobody connects to port 25 for sending anymore and where postfix is new enThat's Thats why we did not put it in the default setup yet and I have no spam problems on my servers without using it, but if you caensurere on your server that none of your clients uses port 25 anymore, then you can enable postscreen on your system as decscribed here: http://www.postfix.org/POSTSCREEN_README.html

As you can see, its just some changes in postfix master.cf and nothing related to ispconfig or nothing that we have to change in ispconfig to enable it.

 

If you use Debian or Ubuntu, run:

apt-get install postgrey

Then run:

ispconfig_update.sh

select "git-stable" as update source and choose yes when the updater asks to reconfigure services.

 

That's not an error, as the message states it is an information and this information says that it can be that dnssec fails if you do not have the haveged daemon installed. So in case that you get problems with dnssec not generating keys due to low entropy, then install haveged as described in the ISPConfig 3.1 perfect server tutorials:

apt-get install haveged

 

See postgrey configuration file /etc/default/postgrey to set the delay time in postgrey.

You can generate dnssec records in the ispconfig dns manager.

 

How should someone help you when you do not even post what you did and where you got this message and what was not working while you got it.

 

I never had to change the permissions of the file /etc/postfix/mysql-virtual_outgoing_bcc.cf on a server as the ispconfig installer sets them to these value which is how they should be:

root@server1:~# ls -la /etc/postfix/mysql-virtual_outgoing_bcc.cf
-rw-r----- 1 root postfix 271 Sep 27 17:12 /etc/postfix/mysql-virtual_outgoing_bcc.cf

That you added group read permissions is not necessary, but you can leave it as it is, it should not harm.