* Darrell Cormier;
Carlos E. R. wrote: My understanding of a good approach follows:
1. Firewall (of course, although I have not gotten there yet) 2. postfix - setup and operational 3. antivirus software (I've heard recommended: F-prot, antivir, and clam antivirus. Comments on these appreciated) 4. SpamAssassin 5. Amavis
And then make them all work together. Is this a good/safe approach? Any information on this will be greatly appreciated. I am also struggling through the man pages of some of these. Are there any good references available on the web for getting all this configured? I know that Togan has a great guide for firewall2 which I am currently reading, but how about the rest of these and making it all work together?
I would go for a Proxy Setup for the services I will be accessing on the internet and also would again choose Proxy setup for the services I will be offering to the internet. 1. Firewall Following the Unofficial guide should get you up and running 2,3,4,5) As I see it, all Mail Transport Agents (postfix, sendmail) are actually do proxying (they relay mail for other MTA). Use fetchmail to download the mail from your ISP, let it hand it over to postfix which should hand it over to content filter (antivir is free for private use) and let the content filter deliver the mail to postfix which should relay it to your internal mail server. Use squid for http proxying, use ftp-proxy which comes with proxy-suite for ftp access. I use tircproxy for IRC proxying Use Xntp for time setup and configure the on on the firewall to get synced with pool.ntp.org and then allow it to act as a time server for your internal machines. Make sure you chroot all services you are offering Himm maybe I should start writing a guide on this subject rather than preparing the final version of the susefirewall2 guide. Have nice weekend -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx