Bart Silverstrim wrote:
On Nov 10, 2006, at 6:28 PM, Gary V wrote:
Hmm, I wonder how many of the people who responded in one way or
another is actually familiar with the package in question. I have
been using Linux for a couple years now and have installed
thousands of packages. In general, I have not had any problems
navigating the package after it has been installed. Sure packages
need configuration. Sure, time is well spent figuring out how to
configure them. I would have been happy to use the package in
question rather than compile from source, but after spending 30
minutes trying to get into the mindset of the packager so I could
actually get clamav to function, I said f*** it.
See, you do that much effort, but then the OP said he just hacks the
word "example" out of the config file and runs the app as root.
That means he took what, five minutes of effort?
The conf for ClamAV is rather well documented from my experiences
with it. The packages may have altered the defaults or where the
files are located, but once it's in place, it's not normally that
hard to get working. The hard part is integrating with other
daemons and scanners. How do you expect THAT to be simplified for
everyone and all situations?
Yes, unlike the OP, I was willing to spend the time, but like the OP I
wish I could have simply installed it and had it functioning (at least
to the point I could then tweak it). This particular package appears
to me it *is* trying to figure out and mold itself to environments
like "CLAMAV for POSTFIX filtered through AMAVISD-NEW using
SPAMASSASSIN" which in fact was my case, but somehow broke itself in
the process of figuring this out. Your experience may differ. Heck, my
experience may differ if I try to install the aforementioned packages
in a different sequence, but I'm not sure my experience should differ.
I would rather it simply put stuff in reasonably predictable places,
then left it up to me to finish the configuration (if needed). The
complexity of the package left me wanting something I could at least
predict.
The only way to solve this problem is to find someone willing to set up
a Linux VMWare image of a turnkey mail server for people who can't
figure out how to fulfill their sysadmin duties.
Then you can answer the questions of how to set up VMWare Player or
VMWare server.
-Bart
This isn't too far fetched an idea. At least with an Intel Mac running
Parallels you can distribute a complete Fedora Linux VM complete with
all the bells and whistles as a file in a CD. With Sendmail, Postfix, or
what ever you want installed and running along with SpamAssassin and
ClamAV. Once you have it built it is trivial to save it and distribute
it as a VM SMTP gateway solution.
Run it headless on a Core Duo Mac Mini and you have a nice small
footprint, small office SMTP front end that has the best tools
available. You can stuff a lot of Mini's in a refrigerator in your
basement and offer them and yourself as an SMTP service provider.
Or pick another VM package - same idea. I like the idea of Parallels,
though for the price advantage.
I've actually built some Mac Mini mail servers for remote sales offices
and they run and run. And the underlying Unix foundation works very much
the way a remote Linux system runs. And if the systems are low usage you
can install mulitple VM's for multiple customers, and a second Mini to
handle ClamAV chores.
Somebody's taking it seriously: http://www.macminicolo.net/
dp
dp
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
