Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch) (SOLVED)

Michael Shuler wrote: > Jochen Schulz wrote: >> . > > Thanks for the bug link, Jochen - there was no report in my bug search, > prior to posting yesterday. The notes on this bug seem to reflect all > the same behavior I am seeing with 2.3.8

Re: broken upgrade of postfix_2.3.7-3

On Wed, Mar 21, 2007 at 08:17:06 -0400, Carl Fink wrote: > Pardon the thread hijack, but for several versions now the postinst script > hasn't been able to start Postfix on my box. I get > > > Stopping Postfix Mail Transport Agent: postfixpostfix/postfix-script: fatal: > usage: postfix start (or

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Jochen Schulz wrote: > I had the same issue and solved it temporarily by installing OpenSSL > from unstable. See > . > > The release manager noted that unstable's version of OpenSSL won't be > included in etch, though, so that downgrading p

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Michael Shuler: > > Today's postfix update has broken my smtp configuration, I had the same issue and solved it temporarily by installing OpenSSL from unstable. See . The release manager noted that unstable's version of OpenSSL won't be in

Re: Re: broken upgrade of postfix_2.3.7-3

Pardon the thread hijack, but for several versions now the postinst script hasn't been able to start Postfix on my box. I get Stopping Postfix Mail Transport Agent: postfixpostfix/postfix-script: fatal: usage: postfix start (or stop, reload, abort, flush, check, set-permissions, upgrade-configur

Re: Re: broken upgrade of postfix_2.3.7-3

>> From looking at the changelog entry and my trials, this does appear >> be an issue with the current libssl/openssl 0.9.8c-4 that I am >> hitting - the postfix changelog states: >>20070225 "Workaround: Disable SSL/TLS ciphers when the underlying >> symmetric algorithm is not available in the

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Michael Shuler wrote: Mihira Fernando wrote: Do you have btree support installed for postfix ? As I recall, the smtp(d)_session_cache_database parameters are in the default main.cf file but btree support is _not_ installed by default. If you're not using these 2 parameters I suggest you comment

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Mihira Fernando wrote: > Do you have btree support installed for postfix ? As I recall, the > smtp(d)_session_cache_database parameters are in the default main.cf > file but btree support is _not_ installed by default. > If you're not using these 2 parameters I suggest you comment them out > and re

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Michael Shuler wrote: Mihira Fernando wrote: Michael Shuler wrote: Mar 20 19:03:20 aesop postfix/master[2010]: warning: process /usr/lib/postfix/smtpd pid 3983 exit status 127 Mar 20 19:03:20 aesop postfix/master[2010]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling I have

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Mihira Fernando wrote: > Michael Shuler wrote: >> Mar 20 19:03:20 aesop postfix/master[2010]: warning: process >> /usr/lib/postfix/smtpd pid 3983 exit status 127 >> Mar 20 19:03:20 aesop postfix/master[2010]: warning: >> /usr/lib/postfix/smtpd: bad command startup -- throttling I have also not bee

Re: broken upgrade of postfix_2.3.7-3 -> 2.3.8-2 (etch)

Michael Shuler wrote: Today's postfix update has broken my smtp configuration, and I would enjoy any help troubleshooting - I have downgraded to 2.3.7-3 for the moment. The changelog looks fairly trivial, but I have not been able to put my finger on the real problem - is this possibly an libssl/