Chris Schumann wrote: > Thanks for the tips, guys. After noodling around some more on the server, > it looks like RHEL has it all integrated pretty well (so there's hope > going forward). > > The bad news is that RHEL3 is only up to spamassassin 2.55, while 2.63 is > required to even apply a patch for the URI blacklist scanning, and 3.0 has > it built in. > > I can update spamassassin, of course, but I'd like to keep the update > management simple, so I think I will hold off until we can update to RHEL4 > and go from there. > You're probably going to find that it's best to be in a position to install Spamassasin yourself anyway - for example, Spamassasin 3.1 is now out and is a big improvement over 3.0.x in a lot of ways, particularly if you're trying to use the Bayesian filters for a large site. It's a pretty easy build and it's pretty easy to build it as an RPM. How many users and how much mail traffic are you supporting? Are you giving your users access to the SIEVE filters in cyrus? If so, how are you doing it? We are currently using a plugin in Squirrelmail, since lots of our users (University campus, lots of students) use Squirrel as their only email client. This works fairly well for the comparatively small number of people who actually set up server-side filtering. And since I'm actually sending this email from the address I'm subscribed to the list from, this will probably actually post to the list :-(. > Chris > > Steve Hanson said: > >>On Thu, September 22, 2005 5:02 pm, Chris Schumann wrote: >> >>>In what may not have been the smartest move of all time (influenced by >>>me!), my company is using Cyrus-IMAPd as our IMAP server, and Sendmail >>>as our SMTP server. >>> >>>It works very well, but we get a lot of spam and I'd like to get >>>SpamAssassin working well too. Since the user's don't have login >>>accounts, a .procmailrc file cannot be created for each user. >>> >>>I would appreciate any tips on where to look for information on how to >>>configure such a setup. We're using Red Hat Enterprise 3.0 for the >>>moment. Hopefully switching to 4.0 soon. The default configuration >>>files don't seem to do anything worthwhile. >>> >>>Many thanks, >>>Chris >>> >> >>Well, you're probably not gonna like this but - >> >>What you really should do is just set up spamassassin to run directly >>under sendmail, and have it spam-mark the mail. >> >>Personally I like to use Mimedefang - it's a milter that runs under >>sendmail and will run spamassassin as well as any of a number of virus >>filters. It's very flexible and pretty fast (I run it on a mail server >>with 6000 users and it holds up pretty well. >> >>THere are a number of other such beasts available - if you just want to >>run spamassassin you could install spamass-milter, which will just put >>spam markings into your email. >> >>Then your users can set up filters on the IMAP server to do something >>useful with the markings - put the mail into the Spam filter, or throw >>it away if the score is really high (though I never do that myself). >> >>I believe there is some info on the spamassassin site on how to set up a >>site-wide spamassassin implementation. I'd look at Mimedefang if you >>want a lot of power, and at spamass-milter if you just want something >>simpler. >> >>I'll see if I can dig up a couple of better pointers in the morning >> >>> >>> >>>_______________________________________________ >>>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >>>tclug-list at mn-linux.org >>>http://mailman.mn-linux.org/mailman/listinfo/tclug-list >>> >> >> >>-- >>Steve Hanson >>Cruiskeen Consulting >>http://www.cruiskeenconsulting.com > > > > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list