Hi, I use spam filtering in the postfix smtpd_recipient_restrictions option. These settings are overwritten by ISPConfig in some circumstanses. At least during update where the daemon configuration update is selected. I think ISPConfig should be more carefull in this respect. Relevant part of main.cf: Code: smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf reject_non_fqdn_sender reject_non_fqdn_recipient #### Spam filtering # helo/ehlo syntax check reject_invalid_hostname # Seen false positives, but really efficient on UCE # forbid <name> helos and enforces <fqdn> helos reject_non_fqdn_hostname # at this stage we must be the destination reject_unauth_destination # check for obvious helo fakes # check_helo_access hash:/etc/postfix/smtp_helo_blacklist # RCPT TO not in our maps (reject early instead of bouncing messages) reject_unlisted_recipient # SQLgrey is called here # check_policy_service inet:127.0.0.1:2501 # RBL checks reject_rbl_client zen.spamhaus.org # BL checks reject_rbl_client bl.spamcop.net #### Spam filtering done Is there a way to protect this from being overwritten? Thanks, Bas.
If you select "no" when ispconfig updater asks to update the configuration, then no config files will get altered. You will have to adjust the config files manually then so that they work with the new ispconfig release.
OK, I would prefer that the ispconfig updater would only make the changes and leave the remainder of the file unmodified. How can I find out what required changes to the config files need to be done?
