Modules Matching mail • AWStats 2.0 Description Generates and analyzes statistics from Web, proxy, wap, streaming, ftp or mail server log files using AWStats log analyzer. Download Website Author Laurent Destailleur (Eldy) Last updated 2013-11-30 12:25:53 • AWStats 1.8 1.8 Description Generates and analyzes statistics from Web, proxy, wap, streaming, ftp or mail server log files using AWStats log analyzer.

Custom User Configurations Select the generic selections for keyboard, language and timezone. Partitions You should partition the server with at least this layout: / /usr /var This will protect your server from runaway log files. Firewall Configuration I chose to select the 'no firewall' option. I consider this device to be a traffic management device and not a security device. Upstream security should be handeld by an actual firewall. Of course, many may disagree with this and choose to load IPTables.

DirectAdmin or Webmin; Easy upgrade between versions from shell; Pre-configured to work on a cPanel server with all the standard cPanel ports open; Pre-configured to work on a DirectAdmin server with all the standard DirectAdmin ports open; Auto-configures the SSH port if it's non-standard on installation; Block traffic.

Just make sure you have the right chains configured to allow traffic to flow properly. Package Selection When you get to the package selections, DE-SELECT EVERYTHING. Go back and choose only the following items: Editors ->you'll need this to vi files Development Tools ->you'll need this to compile software Once the machine builds itself, it will reboot. Fix LANG Variable Once it reboots, we need to edit the LANG variable. RedHat's LANG variable setting of LANG='en_US.UTF-8' can cause compilation errors in some perl code used by MailScanner and SpamAssassin. In Red Hat Linux you must edit the file /etc/sysconfig/i18n to change the lines: LANG='en_US.UTF-8' SUPPORTED='en_US.UTF-8:en_US:en' To: LANG='en_US' SUPPORTED='en_US.UTF-8:en_US:en' You then need to re-set and export the LANG variable: [ sysconfig]# LANG='en_US' [ sysconfig]# export LANG Step II - Install Postfix I chose to use postifx instead of sendmail for my MTA. I like postfix because its configuration is very understandable.

Also, I believe it is a bit more lightweight than sendmail. Disable existing Sendmail services Before you install postfix, you need to disable the existing sendmail items running on your Linux box. Service sendmail stop chkconfig sendmail off b. Install Postfix Download postfix 2.1.5 from www.postfix.org and install as per document. Make sure you add the required records in passwd, group and aliases files. Postfix and Mailscanner will not work without them!

Accept all of the default settings when you 'make install' c. Configure Postfix Postifx has two files which control most of its functionality. These are main.cf and master.cf. Specific main.cf edits: myhostname = titan.corp.com mydomain = corp.com myorgin = $mydomain inet_interfaces = all mydestination = $myhostname, localhost.$mydomain $mydomain mynetwork_style = host Note: some of these items need to be changed, while some only need to be uncommented. Test Postfix Build It is very importiant to test postfix now to make sure everything works.

Send an email to this mail server. You can telnet on port 25 to this box and manually send an email. Configure Postfix to forward email Since we do not want this device to be the final destination for our mail, we need to configure Postfix to forward all mail for our domain to our SMTP mail server. We need to make sure that only mail for our domain is forwarded, and mail for other domains is dropped (do not become a open mail relay - very bad!) Edit this item in main.cf relay_domains = lab.net This tells Postfix which domains it should relay mail.

All mail destined for this doamin (and only this domain) will be forwarded to its remote SMTP server. You can put multiple domains here, just seperate them with a comma or whitespace. Add line to end of main.cf transport_maps = hash:/etc/postfix/transport This tells Postfix what method to use to resolve the destination address for relayed mail: Add line to end of '/etc/postfix/transport' lab.net smtp:[192.168.2.225] This command specifically maps the domain 'lab.net' to the IP address 192.168.2.225 and tells Postfix to use SMTP as the transport. All mail destined for lab.net which is relayed thru this Spam Gateway will be forwarded via SMTP to 192.168.2.225.

Net Collection Rate Formula on this page. Then run command: postmap /etc/postfix/transport This command builds the hash table/file which Posfix will use to forward mail. If you don't do this, it wont work.

Finally add this line to main.cf append_at_myorigin = no These lines will make sure your Spam Gateway does not add any of its own header domain info to the mail as it passes thru. Test Again Stop and start postfix to make sure all changes take. Postfix stop postfix start I know this is redundent, but you really should test your system again before installing MailScanner.

Make sure that mail gets passed thru the system wihtout problem. If you do encounter a problem, it will be alot easier to fix it now than after you've installed MailScanner, SpamAssassin and ClamAV. Step III - Install MailScanner a. Install MailScanner MailScanner installation is very easy to install. Just download the package from I use the version for RedHat/Mandrake. Place the tar file in you directory of choice then run: tar zxvf MailScanner-.tar.gz Run the install script:./install. The Science Of Sound Thomas D Rossing Pdf Viewer. sh Use chkconfig to make sure MailScanner is set for the proper run levels.

Chkconfig --list grep MailScanner You should see: MailScanner 0:off 1:off 2:on 3:on 4:on 5:on 6:off Also, you'll need to disable postfix via chkconfig. MailScanner starts postfix itself. Chkconfig postfix off b. I can understand your choice or ClamAV as virus scanner, because it is totally free and open source, but I have concerns about its ability to keep out the newest viruses (and that is the most important job for an AV program. I found BitDefender offers free use (for all) on Linux systems as well as F-Prot and Antivir (for Linux home use only). They are all easy to install and are as good as each other and (sorry to say) better than clamAV in catching new viruses.

One could also use any commercial AV with unix support. I found Sophos works really well.

They all work well and are updated automatically (with little tweaking) by MailScanner. MailScanner uses ways to interface with Postfix which are completely unsupported. In fact, they might change any time on Postfix updates and break MailScanner (or worse: cause data loss due to MailScanner's assumptions on how postfix accesses the data). Such breakages (so far, to my knowledge, without data loss possibility) have happened in the past and might happen again in the future. So if you insist on using MailScanner instead of the much more robust amavisd-new (or other smtp-proxying scanners), you should at least be aware that you need to be very careful whenever you update either Postfix or MailScanner. There has been a lot of discussion about this on the postfix mailinglists in the past.

Regards, Sven.