Len Conrad:
>
> I did the usual freebsd upgrade
>
> postfix stop
>
> make
> make reinstall ( with setenv FORCE_PKG_REGISTER )
>
> postfix start
>
>
>
> mx1# postconf mail_version
> mail_version = 2.7-20091209
>
>
> ==========================================================================
> dnsblog unix - - n - 0 dnsblog
> smtp inet n - - - 1 postscreen
> smtpd pass - - - - 200 smtpd
> #smtp inet n - n - 1000 smtpd
>
> runs as above gives:
>
> Dec 17 11:28:38 mx1 postfix/master[4857]: daemon started -- version
> 2.7-20091209, configuration /usr/local/etc/postfix
>
> then no other errors until immediately:
>
> Dec 17 11:28:40 mx1 postfix/master[4857]: warning: process
> /usr/local/libexec/postfix/postscreen pid 4867 exit status 1
>
> Dec 17 11:28:40 mx1 postfix/master[4857]: warning:
> /usr/local/libexec/postfix/postscreen: bad command startup -- throttling
postscreen will also log "fatal: reason for exit status 1".
If your syslog daemon sends "FATAL" and "WARNING" logs to different
files, then consider using a configuration that keeps those records
together.
Wietse
> I tried -v on the postscreen master.cf line, but got no more log lines.
>
> If comment the first three lines, uncomment the 4th, postfix stop/start
> postfix works.
>
> btw, after postfix upgrades, it seems that I have to postmap all the .map
> files or postfix chokes.
>
> thanks
> Len
>
>
>
