Forum Replies Created
-
Well, I debated responding to this since my response it so OT, but finally decided to toss it in the hopper, just in case it’s useful. Feel free to ignore it–it doesn’t actually pertain directly to installing SpamAssassin.
Having said that…
IMHO, if you’re going to set up your own spam filter anyway, you might just consider assp instead. Fairly easy to set up and changes practically nothing about the default install (mostly just the port that postfix listens on).
Here’s what the relevant portion of my master.cf file looks like after I changed the port. There may have been changes to the main.cf file for postfix too, but I can’t recall anymore because I’ve tweaked that a lot compared to what it looked like in default mode anyway.
# service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== # Copy/paste smtp line, change to 225, set assp to forward to 127.0.0.1:225 in web config 225 inet n - n - - smtpd #smtp inet n - n - - smtpd
ASSP 1.1.2b1 (yes, beta1 but 3 months of stable operation would suggest it’s fine to use) is the best version out. It’s in the CVS at sourceforge.net. The main improvement is that it adds graylisting, which currently stops about 90% of all spam engines in their tracks. The downside of graylisting is that unrecognized ips are delayed an extra 5 or 10 minutes before they can try and send mail to you.
Well anyways, it’s just a thought. Personally, last time I tried to set up Spam Assassin (admittedly years ago now), it was hard to set up and hard to maintain. ASSP has always been pretty simple and useable for us, particularly since most of the config is done from a nice web interface. Worst case scenario is that you have to rebuild the bayesian db from time to time if it gets exceptionally confused.
Best o’ luck!
You might want to check out the AnandTech article on optimizing for G5. It looks like the answer may be “yes” from their article. Or you could reformat with YDL on the XServe, at a very minimum (if you’re not doing anything with AFP or other Apple technologies anyway).
Also, have you tried msyqladmin refresh? Perhaps (if it works) an hourly refresh cronjob would be enough to keep it from bogging?
Ok, I just successfully completed this bloody install (wipes brick powder from forehead). Some hints:
[1] Follow the instructions completely on page 1 first! You have to do those before anything else. For example, the reason Mr. Shankly is gettig the sasl2 error message during epaulsen5’s update is because he hasn’t successfully completed the cyrus-sasl install on page 1.
[2] As the orginal author says, go back and reread the troubleshooting part several times. Quite likely some of your problems are from there. For example, you can’t use the avelsieve filter in SquirrelMail until you’ve gone in and made the group mail and the permissions 705 for the /usr/lib/sasl2/pwauxprop.* files. And you should also do the chflags nouchg on them so that repairing permissions on the server doesn’t hose the install later.
[3] Now for the tricky part–the timsieved.pkg from page 1 instructions doesn’t work as near as I can tell. I too had to follow epaulsen5’s directions (they are quoted at the top of page 19) to get timseived to activate and send out replies. You’ll know you’ve probably reached this point in the process when you can log into SqurrelMail and correctly set up a vacation notice and view it and emails sent to the account show up in SqurrelMail, but your mail log never shows an outgoing reply to the sender.
[4] Also, if you’re getting an error about “Can’t create INBOX/Send” in the left panel of SquirrelMail, you need to go run the /usr/share/squirrelmail/config/conf.pl script and choose D for pref-defined settings for specific IMAP servers. Type “cyrus” in and hit return and then your settings should be correct for cyrus imap.
[5] cyradm seems like quite a useful addition to any server admin’s arsenal. It also contains some perl libraries that help fix some of the scripts in the cyrus/bin folder (the ones that complain that they can’t find the sieve perl libraries). I’d recommend you go and install that too just for fun (search for the article on how to install it; that one works perfectly).
I hope this helps others. All told, I spent 8 or 10 hours trying to figure out the various things I was doing wrong, so maybe this will lower that time for one or two other people out there…
PS: MacTroll, your timseived package really does seem to be non-functional for a 10.3.9 XServe G5 default install. I redid the install of timsieved.pkg, the BDB.pkg, and the AvelSieve.pkg a total of three times (after removing all three receipts each time) and it still refused to work (although BDB and AvelSieve both were working after I reread the troubleshooting guide a couple times!). Epaulsens5’s config/build instrucs were necessary to create a working timsieved–perhaps they could be integrated into the page 1 install instructions at some point?
In any case, thanks to everyone who posted on this thread & MacTroll, the OP. I’ve finally got autoresponders working on my XServe! Woohoo!
Just a quick note that I think this new look is incredibly pretty BTW! Much much better than the last iteration.
Recent Comments