On Mon, Jan 22, 2007 at 11:38:06AM -0800, Bob Eby wrote: > [EMAIL PROTECTED] > > freeze is not available as package, you need to install it from the > > ports tree. > > Good to know, but painful to hear. Guess I'll have to work on learning > ports...
It's not that difficult; in this case, cd /usr/ports/archivers/freeze make install will do the trick. > [EMAIL PROTECTED] > > If you want to know more about freeze-2.5 you can easily type: > > # cd /usr/ports > > # make search key=freeze > > Ok, so freeze is a compression library, and a few other packages rely on > it. Not sure how that helps me other than raising questions about why > amavisd uses it... Since amavisd also does virus scanning, it should be able to look inside all sorts of archives. Or so the reasoning goes - I'm not a big fan of such archaic stuff myself. > > In general, the anti-virus scanners have a lot of dependencies and > > not all of the dependencies (or all scanners) are licensed to allow > > redistribution. > > Okay, you've got me. I don't really care that much about virus scanning > anyways. It was "bayes filtering" and "web interface" + "steps I could > actually follow" that hooked me in to this particular HOWTO. If you've > got a better HOWTO for doing bayes filtering plus a reasonably easy to > use interface for training the filter then I'm all ears. (web > interface, mail interface, it's all the same to me if it's fairly easy > to use.) Bonus points if it's something a novice like me has a chance > of installing in some reasonable time-frame. > > For the record, I'm doing this stuff in a commercial setting, but I'm > in-house so I'm only really in need of freedom 0 at this point. dspam might work, although I'm not sure if it's CGI will work with OpenBSD at all. Otherwise, amavisd, while somewhat complex and rather slow, is a well-known solution; there are probably some web front-ends for it, although I've found their Bayesian implementation rather deficient. > > All of this means you'll be using the ports tree to install your > > antivirus gateway. > > Well, from what little I know, I'd like to avoid this if at all > possible... Then again, I probably should at least stay current with > the latest "stable" and I believe I read the word ports somewhere in > that process. > > Of course the download line from the HOWTO I've been using: > lynx http://www.ijs.si/software/amavisd/amavisd-new-20030616-p10.tar.gz > > Made me think this was a manual install, rather than a use of ports. > > ---<everyone>--- > > You guys have definitely answered: > Question #1: Why can't I find freeze? > > The only thing I'm still pondering a bit is: > Question #2: What am I missing? > > ie: Would I be better off doing something else? I almost chose sendmail > early on since it is built into OpenBSD, but was a bit put off by all > the configuration horror stories, so I stuck with postfix... > > I'm pretty fond of OpenBSD because of all the neat things I've been able > to do using pf and various other networking tools in the past, but I've > definitely never tried to use it as a mail server before (built-in > OpenBSD server management via email doesn't count), nor have I run it as > a hardened external box in any kind of production setting... (Okay, > this is a DMZ, but that doesn't really change my hardening goals.) Postfix works pretty well; sendmail might too, I've never used it. Hardening OpenBSD is both easy and seldom necessary; the only big oops you can run into out of the box is a fork bomb. As to stopping spam, spamd seems pretty popular around these parts, and I've heard good things about greylisting - which is essentially what spamd does. You might want to give that a try, if you can take the hit (slower mail delivery in some cases). Spam filters, however, are a difficult problem. I've tried amavisd, and I'll be using dspam Real Soon Now. > P.S. - I'm a programmer, not a sys admin. Just in case that affects > anything. Not really, I think. Joachim
