If you found this error for any particular domain say unixsurgeon.com, then first check the mx record for this domain. If the MX record is pointing to a different server, then just remove the domain entry unixsurgeon.com from the /etc/localdomains, And add the same entry in /etc/remotedomains. After that restart the exim service.

[root@p-root]# /etc/init.d/exim stop

[root@p-root]# /etc/init.d/exim start

It will solve your problem. And Other option is find the following line in exim.conf and comment it.

[root@p-root]# vi /etc/exim.conf

drop
condition = ${if match{$sender_helo_name}{$primary_hostname}}
message = “REJECTED – Bad HELO – Host impersonating [$sender_helo_name]“

======================================================================================

Enjoy Linux !!!

Implement security features in your server like:

1) DDOS protection using CSF through “SYNFLOOD”.
2) Install apache modules like mod_dosevasive and mod_security in your server.
3) The best,free & open sources solution to protect from DDOs :- http://deflate.medialayer.com/
4) Configure APF and IPTABLES to reduce the DDOS.

Description here :-

1.) DDOS protection using CSF through “SYNFLOOD”. & Connection tracking :- Please modify these option through CSF
:-
# Enable SYN Flood Protection. This option configures iptables to offer some
# protection from tcp SYN packet DOS attempts. You should set the RATE so that
# false-positives are kept to a minimum otherwise visitors may see connection
# issues (check /var/log/messages for *SYNFLOOD Blocked*). See the iptables
# man page for the correct –limit rate syntax
SYNFLOOD = Default: 0
SYNFLOOD_RATE = 100/s
SYNFLOOD_BURST = 150

# Connection Tracking. This option enables tracking of all connections from IP
# addresses to the server. If the total number of connections is greater than
# this value then the offending IP address is blocked. This can be used to help
# prevent some types of DOS attack.
#
# Care should be taken with this option. It’s entirely possible that you will
# see false-positives. Some protocols can be connection hungry, e.g. FTP, IMAPD
# and HTTP so it could be quite easy to trigger, especially with a lot of
# closed connections in TIME_WAIT. However, for a server that is prone to DOS
# attacks this may be very useful. A reasonable setting for this option might
# be arround 300.
#
# To disable this feature, set this to 0
CT_LIMIT = Default: 50 (means 50 connections per ip address)
# Connection Tracking interval. Set this to the the number of seconds between
# connection tracking scans
CT_INTERVAL = Default: 30
# Send an email alert if an IP address is blocked due to connection tracking
CT_EMAIL_ALERT = Default: 1
# If you want to make IP blocks permanent then set this to 1, otherwise blocks
# will be temporary and will be cleared after CT_BLOCK_TIME seconds
CT_PERMANENT = Default: 0
# If you opt for temporary IP blocks for CT, then the following is the interval
# in seconds that the IP will remained blocked for (e.g. 1800 = 30 mins)
CT_BLOCK_TIME = Default: 1800
# If you don’t want to count the TIME_WAIT state against the connection count
# then set the following to “1″
CT_SKIP_TIME_WAIT = Default: 0
# If you only want to count specific states (e.g. SYN_RECV) then add the states
# to the following as a comma separated list. E.g. “SYN_RECV,TIME_WAIT”
#
# Leave this option empty to count all states against CT_LIMIT
CT_STATES =
# If you only want to count specific ports (e.g. 80,443) then add the ports
# to the following as a comma separated list. E.g. “80,443″
#
# Leave this option empty to count all ports against CT_LIMIT
CT_PORTS = 80,443
====================================================
2) Install apache modules like mod_dosevasive and mod_security in your server= :-

mod_evasive and mod_security modules are used to secure Apache Web Server from DDoS and brute force attacks by implementing web application firewall.

The mod_evasive authoring site (zdziarski.com) states that mod_evasive is an evasive maneuvers module for Apache to provide evasive action in the event of an HTTP DoS or DDoS attack or brute force attack. It is also designed to be a detection and network management tool, and can be easily configured to talk to ipchains, firewalls, routers, and etcetera..

*Note: mod_evasive module has been known to cause problems with frontpage server extensions. If you use frontpage server extension, you should thoroughly test your mod_evasive installation before deploying a production server.

# wget http://www.zdziarski.com/blog/wp-content/uploads/2010/02/mod_evasive_1.10.1.tar.gz
#tar -xvzf mod_evasive_1.10.1.tar.gz
# cd mod_evasive
# /usr/local/apache/bin/apxs -cia mod_evasive.c
# mv mod_evasive.loT mod_evasive.lo
# /usr/local/apache/bin/apxs -cia mod_evasive.c
# httpd -M|grep evasiv
# vi /etc/httpd/conf/httpd.conf (edit httpd.conf with the following details)

<IfModule mod_evasive20.c>
DOSHashTableSize   3097
DOSPageCount   2
DOSSiteCount   50
DOSPageInterval   1
DOSSiteInterval   1
DOSBlockingPeriod   600
</IfModule>

# cd /usr/local/apache/modules/
Then download mod_evasive20.so through web and place it in modules directory and change the permission with 755.

# /etc/init.d/httpd restart
==================================================================================

3) The best,free & open sources solution to protect from DDOs :- http://deflate.medialayer.com/ :-

(D)DoS Deflate is a lightweight bash shell script designed to assist in the process of blocking a denial of service attack. It utilizes the command below to create a list of IP addresses connected to the server, along with their total number of connections. It is one of the simplest and easiest to install solutions at the software level.

netstat -ntu | awk ‘{print $5}’ | cut -d: -f1 | sort | uniq -c | sort -n

IP addresses with over a pre-configured number of connections are automatically blocked in the server’s firewall, which can be direct iptables or Advanced Policy Firewall (APF). (We highly recommend that you use APF on your server in general, but deflate will work without it.)
Notable Features :-

* It is possible to whitelist IP addresses, via /usr/local/ddos/ignore.ip.list.
* Simple configuration file: /usr/local/ddos/ddos.conf
* IP addresses are automatically unblocked after a preconfigured time limit (default: 600 seconds)
* The script can run at a chosen frequency via the configuration file (default: 1 minute)
* You can receive email alerts when IP addresses are blocked.

Installation :-

wget http://www.inetbase.com/scripts/ddos/install.sh
chmod 0700 install.sh
./install.sh

Uninstallation :-

wget http://www.inetbase.com/scripts/ddos/uninstall.ddos
chmod 0700 uninstall.ddos
./uninstall.ddos
===================================================================

4) Configure APF and IPTABLES to reduce the DDOS. :-
Ans :- Please install APF/CSF or iptables to reduce the DDOS ,also an hardware firewall (cisco guard ) also help to mitigate DDOS attacks.

Enjoy Linux…!!!!

Standard Method :-

1. At the bottom of the cPanel interface, locate and click the “Cron Jobs” icon.

2. Click on the “Standard” tab.

3. The first option calls for you to enter the email address of where you want the results of the
cron job to be sent. Simply enter the email address in the provided field and move onto the next step.

4. For “Entry 1″ you will see the text “Command to run” with a text box beside. Input the command or path to the script you want to run in the field.

Example :- php -q /home/username/public_html/cron.php

5. Below “Command to run”, there are five options that will allow you the set the time and intervals for your cron job. Those options are listed as follows:

Minute(s)
Hour(s)
Day(s)
Month(s)
Weekday(s)

Once you create the Cron job, a confirmation page will be displayed stating “Cron Updated”.

6. After making the appropriate selections, click the “Save Crontab” button to create the entry. If you elect to reset the changes and go back to the default settings, simply click the “Reset Changes” button.

7. Click the “Go Back” tab and you will be redirected back to the main Cron Job screen.

8. Check your email address to view the results of the cron job.

Advanced Method :-

1. From the main Cron Job screen, click the “Advanced (Unix Style) tab.

2. The first option calls for you to enter the email address of where you want the cron job results to be sent. Simply enter the email address in the provided text box.

3. From there, enter the Minute(s), Hour(s), Day(s), Month(s) Weekday and Command in the provided text boxes.

4. Next, click the “Save Crontab” button to create the entry. If want to the reset the changes and revert back to the default settings, simply click the “Reset Changes” button.

5. A confirmation page will be displayed stating “Cron Updated!” Click the “Go Back” button and you will be redirected back to the main Cron Job screen.

6.) Check your email address to view the results of the cron job.

If you want to benefit from cron jobs and use them effectively, you will need to have some familiarity with Linux commands. This is especially true when creating cron jobs in the Advanced Unix variation. For this reason, it is recommended to inquire within your web host about the files and scripts you want to run before executing them.

Enjoy Linux..

Actually its called ‘cron daemon’. Cron is an automatic task machine. You will use it on your Unix or Linux operating system for doing some tasks at specific intervals. If you set the clock and forget the task. The cron daemon runs the work for you.

What is cron tab?

Cron tab is a text file that contains a Cron Job or your scheduled applications information.

On most of Linux distributions crond is automatically installed and entered into the start up scripts. To find out if it’s running do the following command to check crond deamon is running or not:-

[root@p-root]$ ps aux | grep crond

root 331 0.0 0.7 1124 123 ? s Nov11 0:00 crond

p-root 8660 3.9 2.1 1132 345 tty1 s 11:11 0:00 grep crond

The top line shows that crond is running, and the bottom line is the search we just run.

Crontab file contains the following informations :-

1: minutes (Value is 00 – 59. exact minute the cron executes)
2: hour (Value is 00 – 23. hour of the day the cron executes. 0 means midnight)
3: day (Value is 01 – 31. day of the month the cron executes)
4: month (Value is 01 – 12. month of the year the cron executes)
5: weekday (Value is 00 – 06. day of the week the cron executes. Sunday=0,Monday=1…)

field allowed values
—– ————–
minute 0-59
hour 0-23
day of month 1-31
month 1-12 (or names, see below)
day of week 0-7 (0 or 7 is Sun, or use names)

Examples :-

If you have installed a script in your public_html/ directory called mail.sh.

If you want to run this file each night at 11.30 PM every day:

30 23 * * * /home/username/public_html/mail.sh
30 – represents the minute of cron work
23 – represents the hour of the day
The * represent every day, month, and weekday.

If you want to set the cron job every sunday at midnight 11.30 PM:

30 23 * * 0 /home/username/public_html/mail.sh
0 – represents the Sunday.

If you want the cron job to run at 1:00 and 2:00 A.M:

* 1,2 * * * /home/username/public_html/mail.sh

This runs your cron at 1A.M and 2A.M every day, every month and every week.

If you want to run the above task only from Monday to Friday and at 11.30 P.M:

30 23 * * 1-5 /home/username/public_html/mail.sh

This runs your cron from Monday to Friday and everyday at 11.30 PM.

Multiuser cron :-

As Linux or Unix is a multiuser OS, Some of the applications have to be able to support multiple users, cron is one of these. Each user can have their own crontab file. Which can be created/edited/removed by the command crontab. This command creates an individual crontab file and although this is a text file, as the /etc/crontab is, it should not be edited directly. The crontab file is often stored in /var/spool/cron/crontabs/username (Unix/Slackware etc..) , and /var/spool/cron/username (Redhat , CentOS, Fedora) . But might be kept elsewhere depending on what flavor you are using.

To edit or create your crontab file, use command crontab -e and this will open in editor.

Cron Commands:

crontab filename Install filename as your crontab file

crontab -e Edit your crontab file, or create one if it doesn’t already exist.
crontab -l Display your crontab file.
crontab -r Remove your crontab file.
crontab -v Display the last time you edited your crontab file.

For more information please check man page of cron.

====================================================================

Enjoy Linux …

Today I was hunting about monitoring tool in linux and found lots of monitoring tools (i.e. Nagios, openNMS, Cacti,Centreon etc..) And I try to install nagios. You can also install nagios by following steps :-

Prerequisites:

1. Apache
2. PHP
3. GCC compiler
4. GD development libraries
5. PERL Modules
6. RRDTOOL

And you can install these packages through yum:-

[root@p-root]# yum install httpd

[root@p-root]# yum install php php-mysql php-gd php-ldap php-xml

[root@p-root]# yum install gd gd-devel

[root@p-root]# yum install gcc glibc glibc-common libstdc++-devel gcc-c++

[root@p-root]# yum install install perl-DBI perl-DBD-MySQL

[root@p-root]# yum install install perl-Config-IniFiles

[root@p-root]# yum install install rrdtool perl-rrdtool

Now create new nagios user account and give it password….

[root@p-root]# useradd nagios

[root@p-root]# passwd nagios

Now create nagcmd group for external commands to be submitted through the web interface. Add both the nagios user and the apache user to the group.

[root@p-root]# groupadd nagcmd

[root@p-root]# usermod –a –G nagcmd nagios

[root@p-root]# usermod –a –G nagcmd apache

Now download Nagios and Nagios-Plugins :-

[root@p-root]# wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.1.tar.gz

[root@p-root]# wget http://prdownloads.sourceforge.net/sourceforge/nagiosplug/nagios-plugins-1.4.11.tar.gz

[root@p-root]# tar –zxvf nagios-3.2.1.tar.gz

[root@p-root]# cd nagios-3.2.1

[root@p-root]# ./configure – -with-command-group=nagcmd

[root@p-root]# make all

[root@p-root]# make install

[root@p-root]# make install-init

[root@p-root]# make install-config

[root@p-root]# make install-commandmode

[root@p-root]# make install-webconf

(it will create nagios web config file in apache conf.d direcotry)
Now create nagiosadmin account for nagios web interface.

[root@p-root]# htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin

Password:

[root@p-root]# /etc/init.d/httpd restart

Now install nagios-plugin.

[root@p-root]# tar –zxvf nagios-plugins-1.4.11.tar.gz

[root@p-root]# cd nagios-plugins-1.4.11

[root@p-root]# ./configure –with-nagios-user=nagios –with-nagio-group=nagios

[root@p-root]# make

[root@p-root]# make install

Now you have installed all the required packages and services.
Now start nagios.

[root@p-root]# chkconfig –add nagios

[root@p-root]# chkconfig nagios on

Verify your nagios config file.

[root@p-root]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

If there is no error it means your nagios configuration is correct and you can start nagios service.

[root@p-root]# /etc/init.d/nagios start

Now access your nagios web interface :-

http://localhost/nagios

==============================================
NRPE Installation and Setup:-

Download and Install NRPE

You may download nrpe from http://www.nagios.org/download/download.php

[root@p-root~]# wget http://prdownloads.sourceforge.net/sourceforge/nagios/nrpe-2.12.tar.gz

Extract the Files:

[root@p-root~]# tar -xzf nrpe-2.12.tar.gz
[root@p-root~]# cd nrpe-2.12

Compile and Configure NRPE

You need the openssl-devel package installed to compile NRPE with ssl support. So make sure that open ssl is already installed on the server.

Install NRPE:

[root@p-root~]# ./configure

General Options:

————————-
NRPE port: 5666
NRPE user: nagios
NRPE group: nagios
Nagios user: nagios
Nagios group: nagios

[root@p-root~]# make all

[root@p-root~]# make install-plugin

[root@p-root~]# make install-daemon

[root@p-root~]# make install-daemon-config

[root@p-root~]# make install-xinetd

Post NRPE Configuration

Edit Xinetd NRPE entry:

Add Nagios Monitoring server to the “only_from” directive

[root@p-root~]# vi /etc/xinetd.d/nrpe

Entry will be like this:-

service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /etc/nrpe.conf –inetd
log_on_failure += USERID
disable = no
# only_from = 127.0.0.1
}

only_from = 127.0.0.1

Edit services file entry:

Add entry for nrpe daemon

[root@p-root~]# vi /etc/services

nrpe 5666/tcp # NRPE

Restart Xinetd and Set to start at boot:

[root@p-root~]# chkconfig xinetd on

[root@p-root~]# service xinetd restart

Test NRPE Daemon Install

Check NRPE daemon is running and listening on port 5666:

[root@p-root~]# netstat -at |grep nrpe

Output should be:-

tcp 0 0 *:nrpe *.* LISTEN

or

[root@p-root]# netstat -plan | grep 5666

tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 15721/xinetd

Check NRPE daemon is functioning:

[root@p-root]# /usr/local/nagios/libexec/check_nrpe -H localhost

Output should be NRPE version:

NRPE v2.12

======================================================================

Enjoy Linux !!!

They all are OpenSource softwares and licensed under the terms of the GNU Public Licence(GPL).But I prefered “TestDisk & PhotoRec” most,becasue TestDisk can recover lost partitions and also can make non-booting disks bootable again.PhotoRec can recover lost files including video, documents and archives from Hard Disks and CDRom and lost pictures from digital camera memory.PhotoRec can be used on existing partitions, or can be used to recover files on deleted partitions without having to recover the underlying partitions.Both PhotoRec and TestDisk can be run on Linux,DOS, Windows,FreeBSD, NetBSD, OpenBSD, Sun Solaris, and Mac OS X, and, their developers claim, can be compiled and run on most Unix systems.

Data recovery is the process of retrieving data from corrupted or damaged storage media when it cannot be accessed. The storage media in question will often be a hard disk, but it can also be removable media such as CDs, DVDs, Blu-rays, and storage tapes. There are many different reasons why a system administrator may need to use data recovery tools.

At boot up, mainstream Linux distributions perform routine scans to identify and fix any inconsistencies in the file system. A damaged file system might be caused by the computer not shutting down in an orderly fashion, which can occur say in the event of a power cut. However, such routine scans will not detect hardware failure which might exist for a long period without being noticeable to users. Accesses to bad sectors on the media can make the situation worse, and with further usage as well as the passage of time, the media can eventually become unreadable.

A.) Mondo Rescue :- Tool for configuring and maintaining network machines
B.) TestDisk :- Partition scanner and disk recovery tool
C.) Safecopy :- Copy utility ignoring errors
D.) PhotoRec :- Digital Picture and File Recovery
E.) Ddrescue :- GNU data recovery tool

To Download :-

1. TestDisk
2. Safecopy
3. PhotoRec
4. Ddrescue
5. MondoRescue

Enjoy Linux !!!

Today i am hunting regarding how to reset the default Admin password for Vtiger 5.0.4 Open source CRM Application,because i just forgot password for my admin panel,After half an hour I got the solution and worked perfectly for me. I am sharing some tricky steps for the same:-

1. Login to the mysql database.
(if you have root access of your server then)

[root@p-root]# mysql -u root

2. Using the following commands on mysql command line :-

use ‘vtiger_database_name’;

For versions < 5.0.4 :

update vtiger_users set user_password = ‘HTy&N9@nSd$RM’ where user_name = ‘admin’;

For versions 5.0.4 or later:

update vtiger_users set user_password = ‘HTy&N9@nSd$RM’, crypt_type = ” where user_name = ‘admin’;

This will reset the password to ‘admin’ & “HTy&N9@nSd$RM” is your new password for login.

Note: Replace ‘admin’ with whichever user_name you want to reset the password for.

Enjoy Linux…

Like DOS , DDOS also tries to deny the important services running on a server by broadcasting packets to the destination server in a way that the Destination server cannot handle it. The speciality of the DDOS is that, it relays attacks not from a single network/host like DOS. The DDOS attack will be launched from different dynamic networks which has already been compromised.

Normally, DDOS consists of 3 parts . One is the Master ,Other the slave and atlast the victim. The master is the attack launcher i.e the person/machine behind all this. The slave is the network which is being compromised by the Master and Victim is the target site/server . Master informs the compromised machines, so called slaves to launch attack on the victim’s site/machine. Hence its also called co-ordinated attack.

One common method of attack involves saturating the target (victim) machine with external communications requests, such that it cannot respond to legitimate traffic, or responds so slowly as to be rendered effectively unavailable. In general terms, DoS attacks are implemented by either forcing the targeted computer(s) to reset, or consuming its resources so that it can no longer provide its intended service or obstructing the communication media between the intended users and the victim so that they can no longer communicate adequately.

DDoS Process :-

DDOS is done in 2 phases. In first phase attackers try to compromise weak machines in different networks around the world. This phase is called Intrusion Phase. Its in the next phase that they install DDOS tools and starts attacking the victims machines/site. This Phase is called Distributed DoS attacks phase.

Comman Reasons/Loop holes :-

1) Vulnerable softwares/Applications running on a machine or network.

2) Open network setup.

3) Network/ machine setup without taking security into account.

4) No monitoring or DataAnalysis are being conducted.

5) No regular Audit / Software upgrades being conducted.

———————————————————————————————————

netstat -alpn | grep :80 | awk ‘{print $4}’ | cut -d: -f1 |sort |uniq -c
netstat -alpn | grep :80 | awk ‘{print $5}’ | cut -d: -f1 |sort |uniq -c

———————————————————————————————————

RedHat: netstat -ntu | awk ‘{print $5}’ | cut -d: -f1 | sort | uniq -c | sort -n

BSD: netstat -na |awk ‘{print $5}’ |cut -d “.” -f1,2,3,4 |sort |uniq -c |sort -n

You can also check for connections by running the following command.
netstat -plan | grep :80 | awk ‘{print $4 }’ | sort -n | uniq -c | sort

These are few step to be taken when you feel the server is under attack:
——————————————————————————-
Step 1: Check the load using the command “w”.
Step 2: Check which service is utilizing maximum CPU by “nice top”.
Step 3: Check which IP is taking maximum connection by netstat -anpl|grep :80|awk {’print $5′}|cut -d”:” -f1|sort|uniq -c|sort -n
Step 4: Then block the IP using firewall (APF or iptables “apf -d < IP>” )
——————————————————————————-

How to prevent from DDoS :-

Implement security features in your server like:

1) Install apache modules like mod_dosevasive and mod_security in your server.
2) DDOS protection using CSF through “SYNFLOOD”.
3) The best,free & open sources solution to protect from DDOs :- http://deflate.medialayer.com/
4) Configure APF and IPTABLES to reduce the DDOS.

Basic server securing steps :
===============================
5) Configure sysctl parameters in your server to drop attacks.

You can block the IP which is attacking your server using Ipsec from command prompt.
=========
>> netsh ipsec static add filterlist name=myfilterlist
>> netsh ipsec static add filter filterlist=myfilterlist srcaddr=a.b.c.d dstaddr=Me
>> netsh ipsec static add filteraction name=myaction action=block
>> netsh ipsec static add policy name=mypolicy assign=yes
>> netsh ipsec static add rule name=myrule policy=mypolicy filterlist=myfilterlist filteraction=myaction
========

Enjoy Linux..

In Clam AV :-

Clamd is the scanning daemon, clamav-milter is the milter, and freshclam is the process that updates the virus definitions on regular basis.

1.Install gmp, gmp-devel, sendmail, sendmail-cf, sendmail-devel, zlib, zlib-devel, bzip2, bzip2-devel.

2.Get the sendmail source from sendmail.org. Extract it, go into the libmilter subdirectory. Run “make” and “make install”. That will install libmilter into /usr, where sendmail can find it. No need to build the whole sendmail.

3. Download the latest stable ClamAV distribution from http://www.clamav.net or from sourgeforge http://sourceforge.net/projects/clamav/files/

4. Next you will need to create a user & group for clamav to use:

# useradd clamav

Some OS’s require you to add the group as well:

# groupadd clamav

#useradd -g clamav -s /bin/false -c “Clam AntiVirus” clamav

5. Extract the ClamAv tar ball, build it, install it (three lines, two are make):

# ./configure –prefix=/usr/local/clamav –disable-zlib-vcheck –enable-milter

# make

# make install

6. Configure /usr/local/clamav/etc/clamd.conf. I changed the following:

# Example (default is uncommented you just add the # or comment that line )

And uncomment the following lines :-

LogTime: yes

LogSyslog yes

LogFacility LOG_MAIL

PidFile /var/run/clamav/clamd.pid

TemporaryDirectory /tmp

LocalSocket /var/run/clamav/clamd.socket or LocalSocket /tmp/clamd

FixStaleSocket yes

User clamav

7. Configure /usr/local/clamav/etc/freshclam.conf. I changed the following:

# Example (default is uncommented you just add the # or comment that line )

And uncomment the following lines :-

LogSyslog yes

LogFacility LOG_MAIL

PidFile /var/run/clamav/freshclam.pid

DatabaseMirror db.us.clamav.net

NotifyClamd /usr/local/clamav/etc/clamd.conf

8. # mkdir /var/run/clamav

9. # chown clamav.clamav /var/run/clamav/

10. # chmod 700 /var/run/clamav

11. Create an empty log file for clamav updates:

# touch /var/log/clam-update.log

# chown clamav:clamav /var/log/clam-update.log

12. Start the base services to make sure they work. You may want to “tail -f /var/log/maillog” while you’re doing this:

# /usr/local/clamav/sbin/clamd

# /usr/local/clamav/bin/freshclam -d

13. Configure the milter. Add the following to /etc/mail/sendmail.mc right before the MAILER(smtp)dnl line. It’s two lines, the second beginning with “define”:

INPUT_MAIL_FILTER(`clamav’, `S=local:/var/run/clamav/clmilter.sock, F=, T=S:4m;R:4m;C:30s;E:10m’)dnl

define(`confINPUT_MAIL_FILTERS’, `clamav’)

14. Make the new sendmail.cf by issuing a “make -C /etc/mail” command.

15. Start the milter process to test it:

/usr/local/clamav/sbin/clamav-milter -lo /var/run/clamav/clmilter.sock

16. Restart sendmail to make it pick up the configuration changes (service sendmail restart).

17. Then send a test mail.

18. Please add clamd service in your init.d directory to run this server at boot time of your machine.

Enjoy Linux…!!!!

Today i am installing fantastico on my linux server but i am getting some problem.I have installed properly but i am not able to see Fantastico in Cpanel so i searched on google and found a solution after a long time so i thought for people who are suffering from same problem so i put this article on my site for the Linux guys ……………..

# SSH to your server and enter following commands:

————————————————————————————————————————————-

cd /usr/local/cpanel/whostmgr/docroot/cgi

wget -N http://files.betaservant.com/files/free/fantastico_whm_admin.tgz

tar -xzpf fantastico_whm_admin.tgz

rm -rf fantastico_whm_admin.tgz

————————————————————————————————————————————-

NOTE: if you have problems contacting this server, please try this alternate location:

wget -N http://netenberg.com/files/free/fantastico_whm_admin.tgz

————————————————————————————————————————————-

Go to WHM, login as root and click on Tweak Settings, then you should ensure that both the Ioncube loader is selected for the backend copy of PHP. Save changes.

Now go here:
WHM -> Add-Ons (Plugins on v11.x or higher) -> Fantastico De Luxe WHM Admin (scroll down the left menu).

Upon loading, Fantastico De Luxe WHM Admin will auto-update your existing installation (if existing). All admin files (masterfiles, tarballs, settings etc) will be moved to or created at /var/netenberg.

————————————————————————————————————————————-

After the installation is complete, click on “Settings” and go through the settings. While some settings are not important, some other (marked below with an *) are essential for a proper functioning of Fantastico installations.
Language: Select the language for the admin backend AND default language for users without a language selected.
Email notifications: Enter an email address in order to receive notifications when users perform installations using Fantastico.
Master files settings (*): If you are not an advanced user who modifies the master files, leave this to “Remove”. Change this only if you know what you are doing.
PHPsuexec (*): VERY ESSENTIAL!!! Changing this value will not install or de-install phpsuexec for you. It will only tell Fantastico that you have phpsuexec installed or not installed on your server. Change to “installed” if you perform installations which produce an “Internal Server Error”. Notice: Changes will not apply to existing installations! You have to re-install in order to have working installations.
Path to netPBM: Enter the full path to the netPBM binaries in order to enable Gallery installations. As long as this field has no value, your users will not be able to install Gallery.
Select Fantastico licensing and files server: If the Fantastico pages take long to load switch to the server that works best for you. Fantastico will auto-switch if connections time out.
Update preference: Select latest version (sometimes experimental) or stable version (best working).

————————————————————————————————————————————-

Now you have installed Fantastico perfectly.Go to Cpanel and check it r u able to see Fantastico under Cpanel or not ? If you are not able to see then Follow the steps.

————————————————————————————————————————————-

If it is wget-1.10.2-3.3.fc5 or wget-1.10.2-8.fc6.1, or any version that yum installs on those OSes (they will typically end with .fc5 or .fc6 or .el5) we suggest that you replace it immediately with an older and/or stabler version. This version does not honor the “-P” switch.

An alternate version that we know works is wget-1.10.2-3.2.1 (though more recent versions should also work).

You can use the following commands for this purpose.

For 32-bit:

————————————————————————————————————————————–

rpm -qa wget ;

wget ftp://ftp.funet.fi/pub/mirrors/ftp.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/wget-1.10.2-3.2.1.i386.rpm

chattr -ia /usr/bin/wget

rpm -e wget ;

rpm -ivh –force wget-1.10.2-3.2.1.i386.rpm ;

rpm -qa wget ;
————————————————————————————————————————————–
For 64-bit:

————————————————————————————————————————————–

rpm -qa wget ;

wget http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/x86_64/os/Fedora/wget-1.10.2-15.fc7.x86_64.rpm ;

chattr -ia /usr/bin/wget

rpm -e wget ;

rpm -ivh –force wget-1.10.2-15.fc7.x86_64.rpm ;

rpm -qa wget ;
————————————————————————————————————————————–

Now reinstall your Fantastico and check it ………………..Its Done !!!

————————————————————————————————————————————–

Uninstall Fantastico