And also since I'm on the silliness track:
dovecot-spamass_destination_recipient_limit = 1 ##dovecot_destination_recipient_limit = 1 This is mine and what I want. Again disregard my unused parameter: question for dovecot_destination_recipient_limit. I was not even using this. Finally, was policy_time_limit replaced with policy-spf_time_limit? Thanks, S On 2013-11-12 12:24, Simon Loewenthal wrote: > Please disregard my chroot silliness because this was embarrassingly caused > by a typo. y|n not yes|no. > > On 2013-11-12 11:44, Simon Loewenthal wrote: > >> Hi, >> >> This email contains several questions and all related my upgrade on Debian 6 >> of Postfix from version 2.7 to 2.9.3 (and for Debian this is >> 2.9.3-2.1~bpo60+1) >> >> I pipe email to dovecot via SA for content scanning and delivery, and had >> this option added , >> >> dovecot_destination_recipient_limit=1 >> This should make sure delivery of recipients is done one at a time. My >> server lacks memory and CPU. >> >> policy_time_limit=3600s >> >> I use this to keep SPF perl module from dying and restarting too often and I >> recall I had problems with this set at the defaults because SPF policy would >> not start again. My hack was to increase the policy time because there is >> always one email withing 3600 seconds, and not 1200 seconds. I have this in >> my master.cf: >> >> policy-spf unix - n n - - spawn >> user=nobody argv=/usr/sbin/postfix-policyd-spf-perl >> >> I would like to know what replaced these commands, and if they weren't >> replaced, then what changed within postfix that ensured I don't need to use >> them anymore, because I have this warning: >> >> postconf: warning: /etc/postfix/main.cf: unused parameter: >> dovecot_destination_recipient_limit=1 >> postconf: warning: /etc/postfix/main.cf: unused parameter: >> policy_time_limit=3600s >> >> Finally, I tried to turn of chroot in the master.cf and postfix would not >> start: postfix/master[28375]: fatal: /etc/postfix/master.cf: line 13: field >> "chroot": bad value: "no" >> >> I put this back a hyphen and postfix works! >> >> Thanks lots in advance if someone could shed a little light over here. >> >> Si.
