Wildblue

[Dave Laird]

Good morning, James...

Yes, it's ugly. To reset it, unload the driver and reload.

Yes, it is ugly, but it WORKS for me!!! 8-)

Speaking of the Perl, yesterday I had to entirely reset my entire Perl
configuration using perl -MCPAN e shell and then calling o config init to
reset everything to their default values. This was, of course, all caused
by the upgrade to the latest Perl, 5.8.8, I believe.

However, I'm not complaining. If I cannot find a tool that does what I
want, with Perl I can simply go write one, such as what you have done.
It's still a wonderful way to program that sure beats Visual Basic. <sigh>
Although now I understand there is even a Linux/Debian/Ubuntu application
called Gambas that has matured to where it actually offers *most* of the
features of Visual Basic. Not that one would truly WANT to, that is. 8-)

Dave

[James Vahn]

Post by Dave Laird

Yes, it's ugly. To reset it, unload the driver and reload.

Yes, it is ugly, but it WORKS for me!!! 8-)

I should have mentioned that there is a bit of binary in the otherwise
text script. It's at the end of the format= line, generated under the joe
editor (a cousin of jed) by pressing the squiggle button followed by the
up-arrow cursor control. I'm trying to keep the output of the script on
one line. Do you know of a better way? That's why I posted it uuencoded.


--

[James Vahn]

Post by Dave Laird
Speaking of the Perl, yesterday I had to entirely reset my entire Perl
configuration using perl -MCPAN e shell and then calling o config init to
reset everything to their default values. This was, of course, all caused
by the upgrade to the latest Perl, 5.8.8, I believe.

I almost cried the last time I did that. What happens under Debian is
that you take the package and security management out when you do that
(transfering it to CPAN). It destroys dependancy control, made a mess of
the packaging system. Perl is deeply engrained in Debian.

After removing every bit of CPAN-Perl I could find, I re-installed every
bit of Debian-Perl. Hours. It's the same stuff, what was I thinking...


--

[Dave Laird]

Good morning, James...

Post by James Vahn

Post by Dave Laird
Speaking of the Perl, yesterday I had to entirely reset my entire Perl
configuration using perl -MCPAN e shell and then calling o config init to
reset everything to their default values. This was, of course, all caused
by the upgrade to the latest Perl, 5.8.8, I believe.

I almost cried the last time I did that. What happens under Debian is
that you take the package and security management out when you do that
(transfering it to CPAN). It destroys dependancy control, made a mess of
the packaging system. Perl is deeply engrained in Debian.

Perhaps that is why MailScanner works so well beneath Debian and Ubuntu
but is worthless beneath CentOS unless you are willing to put up with the
CPAN. After this bad experience, I think I will build most of my mail
machines using either Debian or Ubuntu until CentOS gets their collective
sh*t together with respect to Perl.

Post by James Vahn
After removing every bit of CPAN-Perl I could find, I re-installed every
bit of Debian-Perl. Hours. It's the same stuff, what was I thinking...

Yes, that is precisely what happened. The damned dependencies in CPAN
broke at least half a dozen functions, nearly all of which impacted
MailScanner adversely. If you are going to run MailScanner, you have to
have a pretty complex Perl configuration, including some really obscure
files that only seem to appear in Debian and Ubuntu (unless you are
sadistic and use CPAN.

However, having muttered all of that, I will say this: if you persevere
and run MailScanner, the SPAM simply disappears, particularly if you run
MySQL and the tricky bit of business involving the Bayesian filters,
SpamAssassin, Pyzor and Razor2. Then SPAM simply dies. Plus, it is
amazingly fast and not so hard on memory, either.

Dave