If you are thinking about installing Spamassasin 3.0 PAY ATTENTION:
If you haven't been reading this list carefully you will
have missed the fact that spamd has been moved
from /usr/sbin/ to /usr/bin . However, the old version remains
in /usr/sbin which is often where your scripts expect to
On Fri, Sep 24, 2004 at 01:30:19AM -0800, John Andersen wrote:
If you are thinking about installing Spamassasin 3.0 PAY ATTENTION:
If you haven't been reading this list carefully you will
have missed the fact that spamd has been moved
from /usr/sbin/ to /usr/bin . However, the old
On Fri, 24 Sep 2004 01:30:19 -0800 John Andersen [EMAIL PROTECTED] wrote:
If you are thinking about installing Spamassasin 3.0 PAY ATTENTION:
If you haven't been reading this list carefully you will
have missed the fact that spamd has been moved
from /usr/sbin/ to /usr/bin . However,
Justin Mason wrote:
Yeah -- this is almost definitely something to do with SuSE's
packaging of either perl (if it uses the defaults from
ExtUtils::MakeMaker) or SpamAssassin itself (if its rpm spec moves
the file around as Debian does).
Actually, for any real package manager (ie, rpm or
On Friday 24 September 2004 08:52 am, Justin Mason wrote:
Bob Apthorpe writes:
On Fri, 24 Sep 2004 01:30:19 -0800 John Andersen [EMAIL PROTECTED]
wrote:
If you are thinking about installing Spamassasin 3.0 PAY ATTENTION:
If you haven't been reading this list carefully you will
On Fri, Sep 24, 2004 at 02:37:31PM -0400, Kris Deugau wrote:
Justin Mason wrote:
Yeah -- this is almost definitely something to do with SuSE's
packaging of either perl (if it uses the defaults from
ExtUtils::MakeMaker) or SpamAssassin itself (if its rpm spec moves
the file around as
