Mailscanner not scanning queue

[Nate]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, I'm running old versions of postfix and mailscanner, but here are
my reasons:

1. I followed the instructions at
http://www.debian-administration.org/articles/172 which has you install
all of the packages from apt.  These are the version that were installed.

2. I did try getting the latest version of Mailscanner since that was my
first inkling as well.  However, on
http://www.mailscanner.info/downloads.html I do not see a plain tarball
source install.  I see installs for redhat, suse, Solaris/BSD, Debian,
FreeBSD.  I tried to install the Debian version but it's from unstable
and so it choked on dependencies.  I'm not afraid of installing the
latest version from a generic tarball, but I did not see that for
Mailscanner, which I think is odd.  Am I missing something here?  Where
is the source tarball?  My only other option is to try re-compiling the
package, which I've done before, but you really can't expect a lot of
users to know how to do that, and in my experience it doesn't always
work very well.

3. I manage over 200 debian boxes.  When you manage that many,
consistency is key.  Having a few boxes be in the unstable branch while
the rest are in stable can cause problems all over the place and make
your life a living hell.  I know, I've done it before.

So at this point I figured it would be quicker and easier to just ask on
the list as the author of that install page (Ugo) suggested.  As it is,
Razor was writing it's log file to the hold queue directory.  So I fixed
that and we'll see how it goes.

Thanks, Glenn.

Nate

Glenn Steen wrote:
> On 14/12/06, Res <res at ausics.net> wrote:
>> On Thu, 14 Dec 2006, Glenn Steen wrote:
>>
>> > If you want to act on Gerards advice (to update), you could very well
>> > go unstable... it's not _that_ bad:-). Or go Ubuntu, if you want to
>>
>> This is one thing that amazes me, people post to lists saying blah doesnt
>> work, but use antiquated versions, it should be mandatory that people
>> wake
>> up, and use the latest versions before trying to obtain help because
>> somthing doesnt work.
>>
>> People should STOP relying on old versions that are called stable by
>> distros like debian and BSD and so on, and install tarballs rather than
>> these so called stable ports thats are a year old.
>>
>> Its like using sendmail 8.8 and saying why is my mail server blocked for
>> open relaying, when the current version is 8.13 or saying I cant get my
>> brand new camera to work but still use kernel 2.02  *sigh*
>>
> My personal view is very close to yours Res. I've only seen grief from
> the few attempts I've made ocver the years to live with the more than
> insanely mossy/mouldy crap that is called "stable" in the Debian case.
> "Unstable" is is in some ways more stable than at least some RPM-based
> distros:-):-). And still not that close to bleeding edge either. Oh
> well.
> 
> But one has to realise that this isn't always up to the one asking the
> questions... It might be the result of pigheaded PHBs and
> miss-directed policies. So ... a friendly clue as to how to get around
> the current problem, as well as some advice ... Keeps the tone of the
> forum nice, and who knows... The asker might even do an update or
> three;-).
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFgW8aRMRYK1K/wKQRAolaAJ4lwsVWvX7HVIY/+4iXW7A5aa+EpgCdGGPB
dOOpRzOJId3waJqT+SVcZSo=
=6F/y
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3491 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20061214/5d3c9a93/smime.bin