Booservers - All about dedicated servers

Find which site is sending spam email from apache@yourdomain, How to track spam sent out from your server through php/apache

Thu, 04 Sep 2008 15:00:35 +0000

When you have a lot of clients (Domains) on your server, it's almost impossible to track all emails sent from your server through php scripts.

So i found a solution and i going to share with everyone.

Requeriments
Linux
Ensim
root access

1. Go to virtualhost's apache conf in my server is /etc/httpd/conf/virtual

CODE

cd /etc/httpd/conf/virtual

2. Now you can list all sites in your server

CODE

3. Now you have to edit each site's config file. [use your favorite file editor]

CODE

nano site1 <-- change filename for each site name listed on that directory

4. Search for ifModule mod_php (Mine looks like this <IfModule mod_php4.c>)

5. Inside that tag put the next code

CODE

php_admin_value sendmail_path "/usr/sbin/sendmail -t -i -f emailcop@sitename" <-- replace sitename with the domain name of that client.

6. now search in the same file for ifmodule sapi_apache (Mine looks like this <IfModule sapi_apache2.c>)

7. Inside that tag put the same code as php tag code

CODE

php_admin_value sendmail_path "/usr/sbin/sendmail -t -i -f emailcop@sitename" <-- replace sitename with the domain name of that client.

8. Save file

9. Repeat same procedure for each site listed on the directory

10. Finally restart apache/httpd

CODE

type: service httpd restart

Now you can look at your /var/log/maillog folder and see which site is sending email through php scritps the line will look something like this:
[

CODE

Jul 4 11:31:00 secure sendmail[7890]: m64FV0HG007890: Authentication-Warning: yourservername: apache set sender to emailcop@domainname using -f
Jul 4 11:31:07 secure sendmail[7890]: m64FV0HG007890: from=emailcop@domainname, size=308, class=0, nrcpts=1, msgid=<200807041531.m64FV0HG007890@yourservername>, relay=apache@localhost
Jul 4 11:31:07 secure sm-acceptingconnections[13146]: m64FV7cp013146: from=<emailcop@domainname>, size=665, class=0, nrcpts=1, msgid=<200807041531.m64FV0HG007890@yourservername>, proto=ESMTP, daemon=MTA, relay=localhost.localdomain [127.0.0.1]
Jul 4 11:31:07 secure sendmail[7890]: m64FV0HG007890: to=dest@domain-dest, ctladdr=emailcop@domainname (48/48), delay=00:00:07, xdelay=00:00:00, mailer=relay, pri=30308, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (m64FV7cp013146 Message accepted for delivery)

]

Voila!! email identified!! going out through domainanme, if you think is spam you should go to that domain root folder and scan for scripts sending email.

Thanks for reading

Source: http://forums.theplanet.com/index.php?showtopic=90590

4 Primary Areas For Tuning Your Server

Thu, 04 Sep 2008 14:57:07 +0000

I just thought I would add my two cents in for everyone. I posted an old howto with some sysctl.conf, but I think that was when I was running on my previous server using and older version of redhat. So here's a fresh howto that is a little more complete.

These configs are based on my server specs, which is a Dual 2.0GHz Xeon with 2GB of RAM running RedHat Enterprise. Depending on your server's RAM you might have to reduce some of the settings, which I'll try make notes with each section.

First, is the /etc/sysctl.conf file. Most people overlook tweaking these settings, always thinking it is a mysql or apache problem. You can get a tremendous boost in throughput by adjusting these settings. These are the settings I use on my server, and have come about by constantly adjusting and monitoring performance, and this is what works best for me, your mileage may vary based on server specs and traffic. I suggest finding some guides and reading up about what each seting does before you make changes. (Note: most out there are pretty dated unfortunatly). Also, some people out there like to have tcp_window_scaling, sack, fack, etc, turned off, but I leave them on. I guess it is just a personal preference thing. So don't complain, but feel free to leave your comments, testing, and results.

/etc/sysctl.conf

CODE

# Kernel sysctl configuration file for Red Hat Enterprise Linux

# Controls IP packet forwarding

net.ipv4.ip_forward = 0

# Controls source route verification

net.ipv4.conf.default.rp_filter = 1

net.ipv4.conf.all.rp_filter = 1

# Disables IP source routing

net.ipv4.conf.default.accept_source_route = 0

net.ipv4.conf.all.accept_source_route = 0

# Controls the System Request debugging functionality of the kernel

kernel.sysrq = 0

# Controls whether core dumps will append the PID to the core filename.

# Useful for debugging multi-threaded applications.

kernel.core_uses_pid = 1

# Increase maximum amount of memory allocated to shm

# Only uncomment if needed!

# kernel.shmmax = 67108864

# Disable ICMP Redirect Acceptance

net.ipv4.conf.default.accept_redirects = 0

net.ipv4.conf.all.accept_redirects = 0

# Enable Log Spoofed Packets, Source Routed Packets, Redirect Packets

net.ipv4.conf.default.log_martians = 1

net.ipv4.conf.all.log_martians = 1

# Decrease the time default value for tcp_fin_timeout connection

net.ipv4.tcp_fin_timeout = 25

# Decrease the time default value for tcp_keepalive_time connection

net.ipv4.tcp_keepalive_time = 1200

# Turn on the tcp_window_scaling

net.ipv4.tcp_window_scaling = 1

# Turn on the tcp_sack

net.ipv4.tcp_sack = 1

# tcp_fack should be on because of sack

net.ipv4.tcp_fack = 1

# Turn on the tcp_timestamps

net.ipv4.tcp_timestamps = 1

# Enable TCP SYN Cookie Protection

net.ipv4.tcp_syncookies = 1

# Enable ignoring broadcasts request

net.ipv4.icmp_echo_ignore_broadcasts = 1

# Enable bad error message Protection

net.ipv4.icmp_ignore_bogus_error_responses = 1

# Make more local ports available

# net.ipv4.ip_local_port_range = 1024 65000

# Set TCP Re-Ordering value in kernel to '5'

net.ipv4.tcp_reordering = 5

# Lower syn retry rates

net.ipv4.tcp_synack_retries = 2

net.ipv4.tcp_syn_retries = 3

# Set Max SYN Backlog to '2048'

net.ipv4.tcp_max_syn_backlog = 2048

# Various Settings

net.core.netdev_max_backlog = 1024

# Increase the maximum number of skb-heads to be cached

net.core.hot_list_length = 256

# Increase the tcp-time-wait buckets pool size

net.ipv4.tcp_max_tw_buckets = 360000

# This will increase the amount of memory available for socket input/output queues

net.core.rmem_default = 65535

net.core.rmem_max = 8388608

net.ipv4.tcp_rmem = 4096 87380 8388608

net.core.wmem_default = 65535

net.core.wmem_max = 8388608

net.ipv4.tcp_wmem = 4096 65535 8388608

net.ipv4.tcp_mem = 8388608 8388608 8388608

net.core.optmem_max = 40960

After you make the changes to the file, you can make them effective immediately by typing in /sbin/sysctl -p

Also, you will need to issue /sbin/sysctl -w net.ipv4.route.flush=1 to flush the routing table to make some of these changes happen instantly.

Here's some URLs with useful info, benchmarks, etc... (I believe one was posted from someone below)
http://www.aarnet.edu.au/engineering/netwo.../mtu/local.html
http://sverre.home.cern.ch/sverre/TenGBE_w...er_04232003.pdf
http://www.hep.ucl.ac.uk/~ytl/tcpip/linux/...en/datatag-tcp/
http://www-didc.lbl.gov/TCP-tuning/TCP-tuning.html
http://ipsysctl-tutorial.frozentux.net/chu...html/index.html

-------------------------------------------

Second is the MySQL /etc/my.cnf settings file. A lot of people just leave this file with its default settings until they notice problems with their server performance. Please note that I'm not including the datadir or socket settings since those can vary based on your server setup. Also I'm only including the base [mysqld] section and not any of the [safe_mysqld], [mysqldump], or [myisamchk] sections.

Also, update your MySQL to the latest version, if you are still running 3.x you should be dragged out into the street and beaten with a stick, seriously. Just download the MySQL RPMs from the MySQL website, it takes 30 seconds to upgrade. They usually release a new version every month. Be aware of the difference between 4.0.x and 4.1.x (or higher).

CODE

[mysqld]

connect_timeout=15

interactive_timeout=100

join_buffer_size=1M

key_buffer=256M

max_allowed_packet=16M

max_connections=500

max_connect_errors=10

myisam_sort_buffer_size=64M

read_buffer_size=2M

read_rnd_buffer_size=2M

sort_buffer_size=2M

table_cache=1024

thread_cache_size=100

thread_concurrency=4

wait_timeout=300

query_cache_size=128M

query_cache_limit=1M

query_cache_type=1

skip-innodb

For people with a single CPU be sure to set thread_concurrency to 2 (4 is for Dual CPUs). People with 1GB of RAM, you might want to consider lowering the key_buffer to 64M and the myisam_sort_buffer_size to 32M. This really just depends on how much free memory your system has during peak traffic hours. If you increase these too much and your system runs out of physical RAM and starts swapping to disk, your system is going to eat it hard.

For more information about Mysqld variables, please read the following articles as they explain all the settings in-depth and how to fine-tune them: Article 1 and Article 2 and Article 3

-------------------------------------------

Third is Apache. Some people run 1.x, and some run 2.x, me personally I run 2.x because of the better performance. But some people are tied to the older version because of other software packages.

The first thing to do if you are running 1.x is to get mod_gzip and use it. If you are running 2.x then use mod_deflate (it is included). This compresses all your HTML/TXT/XML data before it is sent, saving you bandwidth, and faster load times for your users.

If you are serving up pages + images then you *probably* want to set your keepalive to on, and have your settings something like this:

Timeout 60
KeepAlive On
MaxKeepAliveRequests 1000
KeepAliveTimeout 10

By setting the KeepAliveTimeout low you won't have all those lingering connections. You can probably set it even lower if you like.

If you are only serving up html (or php or whatever) pages, and using another web server for your images (like tux). Then you probably want to set your KeepAlive to Off since the user will only be requesting 1 file at a time.

Most people have the bad habit of instantly increasing their MaxClients to 256. This can be BAD if you don't take into account memory availability. You need to determine how much memory you have free, how much each apache process consumes, then do the math to figure out what you can safely set the MaxClients to. If you exceed your physical memory then once again the server will swap to the HD and the server will take a dive in performance.

Comment out / remove and Dynamic Shared Object (DSO) modules that you do not use! There are a ton loaded by default, most which you will never use. I commented out 20+ personally! Read the apache documentation on what each one does, the apache docs are very detailed.

If possible, set the AllowOverride option to None. This prevents apache from checking for the .htaccess file in every directory whenever a request is made. However if you use .htaccess files then you have to leave the setting there, but if you can limit it down to certain directories, then do it.

Mask your Apache version by using the following settings:
ServerSignature Off
ServerTokens ProductOnly

That's just good practice, you can also hide your PHP info by setting expose_php = Off in your /etc/php.ini file.

Fourth is PHP. One thing to do is use a program like eAccelerator which caches pre-compiled versions of your php files to help reduce overhead and increase performance. It is a free download from sourceforge, but it will require a little know-ho on your part to install. There are plenty of other guides on how to install this. It is very simple and quick.

A lot of people use the redhat PHP RPMs, which can be quite bloated. My libphp4.so module is only 2.07MB in size. (I don't remember what the default redhat one is, but I'm willing to bet it is larger). Also Redhat never seems to keep up to date with the latest PHP (or MySQL) version, I always recommend updating as soon as a new release is published.

Here's my configure line. There's a lot of settings you may not use, and they could be ones that you use that I don't. You can view your current configure line via the phpinfo() function. These include all the big things such as GD, XML, SHM, etc.. Some people maybe want to enable a certain memory-limit to prevent PHP from eating too much memory per process.

Also, I don't use mm simply because I found it would crash apache on an almost daily basis. I had problems with session storage, and also it would not restart after rotating logs...

CODE

./configure

--prefix=/usr

--exec-prefix=/usr

--bindir=/usr/bin

--sbindir=/usr/sbin

--sysconfdir=/etc

--datadir=/usr/share

--includedir=/usr/include

--libdir=/usr/lib

--libexecdir=/usr/libexec

--localstatedir=/var

--sharedstatedir=/usr/com

--mandir=/usr/share/man

--infodir=/usr/share/info

--disable-cgi

--disable-debug

--disable-rpath

--disable-memory-limit

--disable-ipv6

--disable-safe-mode

--enable-pic

--enable-discard-path

--enable-inline-optimization

--enable-gd-native-ttf

--enable-gd-imgstrttf

--enable-magic-quotes

--enable-sysvsem

--enable-sysvshm

--enable-sysvmsg

--enable-shmop

--enable-track-vars

--enable-exif

--enable-wddx

--enable-bcmath

--enable-calendar

--enable-ftp

--enable-inline-optimization

--with-apxs2=/usr/sbin/apxs

--with-mysql=/usr

--with-pear

--with-config-file-path=/etc

--with-exec-dir=/usr/bin

--with-gd

--with-png-dir=/usr

--with-jpeg-dir=/usr

--with-freetype-dir=/usr

--with-gettext

--with-openssl

--with-regex

--with-ttf=/usr

--with-expat-dir=/usr

--with-dom=/usr

--with-dom-xslt=/usr

--with-dom-exslt=/usr

--with-iconv

--with-db4=/usr

--with-gdbm=/usr

--with-zlib=/usr

--with-zlib-dir=/usr

--with-xmlrpc

--with-xml

--with-bz2=/usr

--with-cdb

--enable-mbstring

-------------------------------------------

When compiling programs (like PHP, eaccelerator, etc..), you can fine-tune some of your compile-options to enhance performance for your CPU's capabilities (and remove excess stuff like debug info)

As mentioned before, I run dual xeon's (P4's for all practical purposes). If you are using a different CPU then you might have to go look up the proper flags at the GCC website.

Before compiling a program, you can set the following flags:

CODE

export CFLAGS="-O3 -pipe -mcpu=pentium4 -march=pentium4 -fomit-frame-pointer"

export CXXFLAGS="${CFLAGS}"

export CHOST="i686-pc-linux-gnu"

export MAKEOPTS="-j2"

export LDFLAGS="-Wl,-O1"

These flags are considered "stable" and should enhance performance a little for software that you compile with these options. There are tons of other flags, however some reduce precision for certain math (which can cause problems in certain software) and others may reduce stabililty.

-------------------------------------------

I guess that's about it... Use the information at your own risk. Hopefully it will help some people out, or at least point them in the right direction.

Please don't post questions that are like: "here's my config, can you optimize it for X server?". I don't check these forums that often, so I probably won't reply to your question.

Server tuning is more of an art than just entering X setting to Y number. Before making changes, keep your old configs. Also get a monitoring program so you can graph out your server load and other vitals. That way you can see before & after results. Also, if you run a forum, let your users know that you are going to make changes, and get their feedback on response time and such from them.

Enjoy.

Source: http://forums.theplanet.com/index.php?showtopic=48880

How to setup email Smart Host to send emails via Gmail or DynDNS's smtp.

Thu, 04 Sep 2008 14:47:08 +0000

Lately my TP server was having problems sending emails to Yahoo addresses. Most emails were put under mail queue for hours. I decided to setup a Smart Host under Exim. If the recipients' emails are Yahoo addresses, the Smart Host will be engaged.

There are two SMTPs that can be used - Gmail or DynDNS. While Gmail's smtp is free, a copy of the email will be placed under the SENT EMAIL folder once it is processed. This will take up the 2Gb space soon if you have a lot of emails to process. Also, there is no one-click solution to purge emails under SENT EMAIL folder.

So I decided to use DynDNS.com's MailHop Outbound service. It is sold at the block of 150 relays per day @ $15/year. Meaning, you can process 150 mails each day. If you have more, then you have to purchase more blocks. To find out how many emails you have processed under DynDNS, log into your account and view the statistics.

# Select the SMTP to use:
For Gmail:
First, enable POP for your gmail account. You do that in the �Forwarding and POP� section of the settings.

For DynDNS:
Subscribe to the MailHop Outbound service.

# Next, create a domain list. This domain list will hold the list of domains to send via gmail or DynDNS, one domain per line. Save your domain list as /etc/exim/gmail.domains or /etc/exim/dyndns.domains .

# Then, add a domain list to your exim configuration. For WHM/cPanel, go to Exim Configuration Editor >> Advanced Editor and enter this line below the very top box of Exim Configuration Editor:

QUOTE

domainlist use_gmail_domains = /etc/exim/gmail.domains

QUOTE

domainlist use_dyndns_domains = /etc/exim/dyndns.domains

# Seach for the string "begin authenticators". In the box after this string, create an authenticator.

QUOTE

gmail_login:
driver = plaintext
public_name = LOGIN
client_send = : YourGmailUsername@gmail.com : YourGmailPassword

QUOTE

dyndns_login:
driver = plaintext
public_name = LOGIN
client_send = : YourDyndnsUsername : YourDyndnsPassword

Note that in a default exim configuration there are usually no authenticators, so don�t forget the begin authenticators statement if this is your first one.

# Under the ROUTER CONFIGURATION box, add a router:

QUOTE

send_via_gmail:
driver = manualroute
domains = +use_gmail_domains
transport = gmail_smtp
route_list = "* smtp.gmail.com byname"

QUOTE

send_via_dyndns:
driver = manualroute
domains = +use_dyndns_domains
transport = dyndns_smtp
route_list = "* outbound.mailhop.org byname"

# Under the TRANSPORTATION CONFIGURATION box, forcing it to use AUTH and TLS (TLS is not required for DynDNS):

QUOTE

gmail_smtp:
driver = smtp
hosts = smtp.gmail.com
hosts_require_auth = smtp.gmail.com
hosts_require_tls = smtp.gmail.com

QUOTE

dyndns_smtp:
driver = smtp
hosts = outbound.mailhop.org
hosts_require_auth = outbound.mailhop.org

# Save Exim config and restart Exim.

Source: http://forums.theplanet.com/index.php?showtopic=90364

Install Mailscanner MRTG

Thu, 15 Dec 2005 21:55:06 +0000

This will install Mailscanner MRTG on your system. I have tested it on Ensim 3.1.10 and Ensim 3.5.17. Others have also done this on CPanel, but make sure you make the change noted...

Regular, I am not responsible for your box/you are doing this at YOUR OWN RISK... It should not screw anything up, but you are ultimately responsible if it does. I will help out as much as I can, but I am not a genius.

PREREQUISITES
1) MRTG *MUST* be installed (HOW-TO)
2) Mailscanner *MUST* be installed (I use gpans MS/SA/CM HOW-TO, but there is a MS Only HOW-TO too)

INSTRUCTIONS
cd ~
wget http://umn.dl.sourceforge.net/sourc...rtg-0.05.tar.gz
tar -xzvf mailscanner-mrtg-0.05.tar.gz
cd mailscanner-mrtg-0.05
cp mailscanner-mrtg.conf /etc/MailScanner/
cp mailscanner-mrtg.cfg /etc/mrtg/
cp mailscanner-mrtg /usr/sbin/
cp mailscanner-mrtg.include /etc/httpd/conf/
cp /etc/httpd/conf/httpd.conf /etc/httpd/conf/httpd.conf.bk

For CPanel Users
mkdir /usr/local/apache/htdocs/mailscanner-mrtg
cp web/* /usr/local/apache/htdocs/mailscanner-mrtg/
pico -w /etc/MailScanner/mailscanner-mrtg.conf
Find the two lines that start with:
Incoming Queue Dir =
Outgoing Queue Dir =
and change it to look like this:
Incoming Queue Dir = /var/spool/exim_incoming/input/
Outgoing Queue Dir = /var/spool/exim/input/

For Ensim/Red Hat/Fedora Users
mkdir /var/www/html/mailscanner-mrtg
cp web/* /var/www/html/mailscanner-mrtg/

Continued... FOR ALL USERS
pico -w /etc/httpd/conf/httpd.conf
Add this line to the very bottom
Include /etc/httpd/conf/mailscanner-mrtg.include
Ctrl + X to quit, y to save

Run this command 3 times. Ignore the errors and wait, it takes a few seconds each time.
mrtg /etc/mrtg/mailscanner-mrtg.cfg
-- IGNORE THE ERRORS (They are normal) --

service httpd restart
If this fails, check that you copied the file mailscanner-mrtg.include to the /etc/httpd/conf folder. Also recheck that you added the Include line above. If all else fails comment out the Include line and post your errors. DO NOT CONTINUE until httpd restarts successfully.

pico -w /etc/crontab
Add this line to the bottom of the file
0-59/5 * * * * root /usr/bin/mrtg /etc/mrtg/mailscanner-mrtg.cfg >> /dev/null
Ctrl + X to quit, y to save

Go to http://hostname.domain.com/mailscanner-mrtg

Email with attachments from command line

Thu, 15 Dec 2005 21:53:40 +0000

Sending emails from command line
I�ll describe possible ways to send emails from the command line. Of course there are much nicer ways to do it, but you may be in the situation (such as the one that drove me to do a deeper research and come out with this solution) and will need an easy and fast way to send mails from the prompt.

Simple text emails:
You can send simple emails by using the already installed sendmail program with the following command at the prompt:

echo "Simple, small body Text goes here" | mail -s "The Subject goes here" user@domain.com

If you have already typed a message in a text file, then import the text into the body of the email you are sending by using command:

mail -s "The Subject goes here" user@domain.com < text_file

Disadvantage: the email will be sent using header From: root@host.domain.com

Advanced emails with attachments:
If you need to send emails containing attachments, then I�ll recommend you to use an additional program not included on the standard Linux distributions, since there it were no way I could find a way to use the build in tools to do it.
This is a mature software, very well documented and with constant development to keep up to date and using most possible features we�ll need.
Program: Email
Version: 2.2.2
WebSite: http://email.cleancode.org/

As root:
Create a temp folder to download the source:
mkdir email
cd email
wget http://email.cleancode.org/download/email-2.2.2.tar.gz
tar �zxvf email-2.2.2.tar.gz
cd email-2.2.2

Run the following commands to have it installed:
./configure

Create the installation file:
make

Run the installation:
su -c 'make install'

At the end you�ll get the program installed with:
Binary directory: /usr/local/bin
Email Files /usr/local/etc/email

Edit the configuration file:
You can select to send email by SMTP or by sendmail.
I personally use sendmail for easiness.
pico -w /usr/local/etc/email/email.conf

For sendmail:
Comment out lines: (add # at the beginning of the line)
#SMTP_SERVER = '127.0.0.1'
#SMTP_PORT = '25'

Uncomment line: (remove # from the beginning of the line)
SENDMAIL_BIN = '/usr/lib/sendmail -t -i'

Set sender personal info with something like:
MY_NAME = 'System Administrator'
MY_EMAIL = 'info@domain.com'
REPLY_TO = 'info@domain.com'

Exit and save
Ctrl x
y

For SMTP:
You got the idea, just fill out SMTP variables with proper info.

Edit the signature file:
pico -w /usr/local/etc/email/email.sig

Set it as appropriate with relevant info.
I�d recommend removing line: (to keep system privacy)
On System: %h

Exit and save
Ctrl x
y

System installed and configured.

Some usage example:
Let say you are using Mailsacanner with ClamAV, and a valid attachment was removed, then a customer contacted you with the email MailScanner sent him, including the file name and info and the path were the attachment was quarantined:
It�ll read something like:

...
The original e-mail attachment "file_name.zip"
� �
Note to Help Desk: Look on the E-MailSystem MailScanner in /var/spool/MailScanner/quarantine/20040730 (message i6UKnWp02396)
�

With that info will do:
cd /var/spool/MailScanner/quarantine/20040730/i6UKnWp02396

Verify the mentioned file exists:
ls
decompressed_file_name.pdf file_name.zip

Execute the email command to send the attachment:
email -s "Attachment" -a file_name.zip user@domain.com

Info: -s = Subject -a = Attachment

For the email body, the system default editor will open up, usually vi
Type in whatever message you want to tell:
To start typing:
Shift a

Dear customer:
Find attached the removed file.

Regards,

To finish typing press:
[ESC]
To quit vi type:
:exit

As soon as vi exists, the email will be sent, and will give you a nice progress bar.

Read the README file for more usage options and tweaks.
pico /path/to/download/folder/email-2.2.2/README

Credits: http://www.integrese.com/

Easy Mailscanner + Clam Antivirus + SpamAssassin Updated 5/9/2003

Thu, 15 Dec 2005 21:52:15 +0000

We have put together the following package which will install Mailscanner, Clam Antivirus and SpamAssassin on your Ensim 3.1, or Ensim Pro 3.5 server.

This package installs:
Mailscanner 4.22
Clam Antivirus 0.60
SpamAssassin 2.55

We have tested it on upgrades from 4.11 + Mailscanner versions without issues. If you have an older Mailscanner install, we would recommend uninstalling it first and deleting the /etc/MailScanner folder before running this package.

This package does not use f-prot as you need a commercial license for use in a business environment.

Installation:

1) Make sure you are su root (or -)

2) Download the appropriate installer to a folder on your server, then install it

Ensim Pro 3.5.x

wget http://download.cheetaweb.com/mails...it-3.5.0.tar.gz
tar -zxvf mailscanner-kit-3.5.0.tar.gz
cd mailscanner-kit-3.5.0
./mailscanner-clamav-spamassassin-3.5.0.sh

Ensim 3.1.x
wget http://download.cheetaweb.com/mails...t-0.2.72.tar.gz
tar -zxvf mailscanner-kit-0.2.72.tar.gz
cd mailscanner-kit-0.2
./mailscanner-ensim-0.2.sh

3) You will need to configure MailScanner as described

service sendmail stop
chkconfig --del sendmail
chkconfig --level 2345 MailScanner on
service MailScanner start

*NOTE 1* For Ensim 3.1 installs, this package requires that you be running a perl 5.6.0 environment.

*NOTE 2 * If your /home partition is mounted separately from /, you will need to change the the Incoming Queue to the following after installation, or Mailscanner will not run:

Incoming Queue Dir = /var/spool/mqueue.in

You will also need to edit /etc/cron.d/mqueuecron to run more frequently, i.e.

*/10 * * * * root /usr/lib/opcenter/virtualhosting/MailQueueCleaner

*NOTE 3* SpamAssassin is configured to only tag emails by default. You will need to reconfigure the delivery preferences in MailScanner.conf if you wish it to delete, bounce or otherwise remove the messages that have been tagged as spam.

Credits: http://www.cheetaweb.com/

Booservers - All about dedicated servers

Find which site is sending spam email from apache@yourdomain, How to track spam sent out from your server through php/apache

4 Primary Areas For Tuning Your Server

How to setup email Smart Host to send emails via Gmail or DynDNS's smtp.

Install Mailscanner MRTG

Email with attachments from command line

Easy Mailscanner + Clam Antivirus + SpamAssassin *Updated 5/9/2003*

Easy Mailscanner + Clam Antivirus + SpamAssassin Updated 5/9/2003