apt-get install gcc g++ make flex bison openssl libssl-dev perl perl-base perl-modules libperl-dev libaio1 libaio-dev zlib1g zlib1g-dev libcap-dev bzip2 automake autoconf libtool cmake pkg-config python libreadline-dev libdb4.8-dev libsasl2-dev
Print a count of the messages in the queue:
exim -bpc
Print a listing of the messages in the queue (time queued, size, message-id, sender, recipient):
exim -bp
Print a summary of messages in the queue (count, volume, oldest, newest, domain, and totals):
exim -bp | exiqsumm
Print what Exim is doing right now:
exiwhat
Test how exim will route a given address:
root@localhost# exim -bt [email protected] [email protected] <-- [email protected] router = localuser, transport = local_delivery root@localhost# exim -bt [email protected] [email protected] router = localuser, transport = local_delivery root@localhost# exim -bt [email protected] router = lookuphost, transport = remote_smtp host mail.remotehost.com [1.2.3.4] MX=0
Run a pretend SMTP transaction from the command line, as if it were coming from the given IP address. This will display Exim’s checks, ACLs, and filters as they are applied. The message will NOT actually be delivered.
exim -bh 192.168.11.22
Display all of Exim’s configuration settings:
exim -bP
Exim includes a utility that is quite nice for grepping through the queue, called exiqgrep. Learn it. Know it. Live it. If you’re not using this, and if you’re not familiar with the various flags it uses, you’re probably doing things the hard way, like piping `exim -bp` into awk, grep, cut, or `wc -l`. Don’t make life harder than it already is.
First, various flags that control what messages are matched. These can be combined to come up with a very particular search.
Use -f to search the queue for messages from a specific sender:
exiqgrep -f [luser]@domain
Use -r to search the queue for messages for a specific recipient/domain:
exiqgrep -r [luser]@domain
Use -o to print messages older than the specified number of seconds. For example, messages older than 1 day:
exiqgrep -o 86400 [...]
Use -y to print messages that are younger than the specified number of seconds. For example, messages less than an hour old:
exiqgrep -y 3600 [...]
Use -s to match the size of a message with a regex. For example, 700-799 bytes:
xiqgrep -s '^7..$' [...]
Use -z to match only frozen messages, or -x to match only unfrozen messages.
There are also a few flags that control the display of the output.
Use -i to print just the message-id as a result of one of the above two searches:
exiqgrep -i [ -r | -f ] ...
Use -c to print a count of messages matching one of the above searches:
exiqgrep -c ...
Print just the message-id of the entire queue:
exiqgrep -i
The main exim binary (/usr/sbin/exim) is used with various flags to make things happen to messages in the queue. Most of these require one or more message-IDs to be specified in the command line, which is where `exiqgrep -i` as described above really comes in handy.
Start a queue run:
exim -q -v
Start a queue run for just local deliveries:
exim -ql -v
Remove a message from the queue:
exim -Mrm <message-id> [ <message-id> ... ]
Freeze a message:
exim -Mf <message-id> [ <message-id> ... ]
Thaw a message:
exim -Mt <message-id> [ <message-id> ... ]
Deliver a message, whether it’s frozen or not, whether the retry time has been reached or not:
exim -M <message-id> [ <message-id> ... ]
Deliver a message, but only if the retry time has been reached:
exim -Mc <message-id> [ <message-id> ... ]
Force a message to fail and bounce as “cancelled by administrator”:
exim -Mg <message-id> [ <message-id> ... ]
Remove all frozen messages:
exiqgrep -z -i | xargs exim -Mrm
Remove all messages older than five days (86400 * 5 = 432000 seconds):
exiqgrep -o 432000 -i | xargs exim -Mrm
Freeze all queued mail from a given sender:
exiqgrep -i -f [email protected] | xargs exim -Mf
View a message’s headers:
exim -Mvh <message-id>
View a message’s body:
exim -Mvb <message-id>
View a message’s logs:
exim -Mvl <message-id>
Add a recipient to a message:
exim -Mar <message-id> <address> [ <address> ... ]
Edit the sender of a message:
exim -Mes <message-id> <address>
To configure a smart host, create /etc/exim.conf.local on the source server (server1 in this example) and add the following lines. Be sure to change to the hostname or IP of the smart host server.
|
1
2
3
4
5
6
|
@ROUTERSTART@ smart_route: driver = manualroute domains = !+local_domains transport = remote_smtp route_list = * host.name.of.smart.host.server |
Assuming this server (server1) is a cPanel server, next run /scripts/buildeximconf and then /scripts/restartsrv_exim. If not, simply restart your Exim server using normal init scripts.
Assuming you’re installing the yum version of Exim on a CentOS/RHEL server, you’ll need to make two configuration changes. The first is to allow the IP of the mailserver to relay through the smarthost. Open the configuration at /etc/exim/exim.conf, find the line referenced below and edit it replacing x.x.x.x with your mailserver IP.
|
1
|
hostlist relay_from_hosts = 127.0.0.1 : x.x.x.x |
Second, you’ll need to tell Exim not to listen only on the localhost address for incoming mail, which is the default. Again find the configuration line below and add a hash (#) in front of it to comment it out.
|
1
|
local_interfaces = <; 127.0.0.1 ; ::1 |
Save the modified config file and restart Exim on this server.
That’s it; watch the logs for a bit to make sure it’s working! The easiest way is to just tail -f /var/log/exim_mainlog on both servers and then send a message from server1 to a remote host, and watch for the mail to travel out server2!
You should download yumdownloader postgrey the you should extract this rpm and take some files for usage:
rpm2cpio postgrey-1.34-4.fc18.noarch.rpm | cpio -idv
the you can need copy some postgrey configuration and executable files from ./usr/sbin:
./usr/sbin/postgrey
./usr/sbin/postgreyreport
to /usr/local/sbin
./etc/postfix/postgrey_whitelist_clients.local
./etc/postfix/postgrey_whitelist_recipients
./etc/postfix/postgrey_whitelist_clients
to /etc folder
then you need create postgrey working folder for postgrey database
mkdir /var/spool/exim/postgrey && chown mailnull.mail /var/spool/exim/postgrey
to start postgrey you can like this:
/usr/local/sbin/postgrey -d –unix=/var/spool/exim/postgrey/socket –exim –syslog-facility=local6 –user=mailnull –group=mail –dbdir=/var/spool/exim/postgrey –delay=60 –max-age=35 –retry-window=12h –greylist-text=Greylisted. Please, try again later. –whitelist-clients=/etc/postgrey_whitelist_clients –whitelist-recipients=/etc/postgrey_whitelist_recipients –whitelist-clients=/etc/postgrey_whitelist_clients.local –auto-whitelist-clients=5
if you can start, you maybe missing some dependencies like:
yum install perl-BerkeleyDB perl-Net-DNS perl-Net-Server perl-Digest-HMAC perl-IO-Multiplex perl-Digest-SHA1
You should create new ACL rule in your exim.conf
begin acl
# ACL that is used after the RCPT command
check_recipient:
# postgrey [TOP]
defer
log_message = greylisted host $sender_host_address
!senders = : postmaster@*
# domains = +local_domains : +relay_to_domains
!hosts = /etc/virtual/domains
!authenticated = *
verify = recipient/callout=20s,use_sender,defer_ok
set acl_m3 = request=smtpd_access_policy\n\
protocol_state=RCPT\n\
protocol_name=${uc:$received_protocol}\n\
instance=${acl_m2}\n\
helo_name=${sender_helo_name}\n\
client_address=${substr_-3:${mask:$sender_host_address/27}}\n\
client_name=${sender_host_name}\n\
sender=${sender_address}\n\
recipient=$local_part@$domain\n\n
set acl_m3 = ${sg{\
${readsocket{ /postgrey/socket/full_address }{$acl_m3}\
{5s}{}{action=DUNNO}}\
}{action=}{}}
message = ${sg{$acl_m3}{^\\w+\\s*}{}}
condition = ${if eq{${uc:${substr{0}{5}{$acl_m3}}}}{DEFER}{true}{false}}
# add “greylisted by ..seconds” header to mail which has successfully
# passed the greylisting.
warn
!senders = : postmaster@*
# domains = +local_domains : +relay_to_domains
!hosts = /etc/virtual/domains
!authenticated = *
message = ${sg{$acl_m3}{^\\w+\\s*}{}}
condition = ${if eq{${uc:${substr_0_7:$acl_m3}}}{PREPEND}{true}{false}}
# postgrey [END]
# to block certain wellknown exploits, Deny for local domains if
# local parts begin with a dot or contain @ % ! / |
deny domains = +local_domains
local_parts = ^[.] : ^.*[@%!/|]
After this you can restart you exim server and check if you exim use greylisting.
You can fix this by editing wp-includes/functions.php then you should find php function wp_get_mime_types() and add additional array values, for example:
‘sh’ => ‘application/sh’, or some others file extensions
ssh -l root IP_address_old_server php -i > php_versions.txt
ssh -l root IP_address_new_one php -i >> php_versions.txt
and now you can analyze outputs:
cat php_versions.txt | sort | uniq -u
Its perfect IDN conversation tool http://mct.verisign-grs.com/
Sometimes useful if you forgot this:
disable: csf -x
enable: csf -e
more information: csf- h
First of all stop mysql server and run:
mysqld_safe –skip-grant-tables
In new console connect to mysql:
mysql –user=root mysql
update user set Password=PASSWORD(‘reseted_password’) where user=’root’;
flush privileges;
directadmin pre-install:
yum install wget screen gcc gcc-c++ flex bison make bind bind-libs bind-utils openssl openssl-devel perl quota libaio libcom_err-devel libcurl-devel gd zlib-devel libcap-devel bzip2 db4-devel cyrus-sasl-devel perl-ExtUtils-Embed autoconf automake libtool
run screen and install:
screen
wget http://www.directadmin.com/setup.sh && chmod 755 setup.sh
begin directadmin installation: ./setup.sh
Its very simple to list MySQL users:
use mysql;
SELECT User FROM mysql.user;
Fix:
/scripts/update_local_rpm_versions --edit target_settings.munin uninstalled
If you have minimal Centos OS installation you should install perl and wget and screen packages, also disable selinux protection:
yum install wget perl screen
setenforce 0
sed -i s/SELINUX=enforcing/SELINUX=disabled/g /etc/selinux/config
screen
cd && wget -N http://httpupdate.cpanel.net/latest && chmod +x ./latest && ./latest
And should wait WHM/cPanel installation about 2 hours.
An Error 522 means that the connection started on the origin web server, but that
the request was not completed. The most common reason why this would occur is
that either a program, cron job or resource is taking up more resources than it should
causing the server not to be able to respond to all requests properly. The origin web
server is not functioning consistently for each request. Contact your hosting provider
to identify and resolve the issue.
Dropbox is a great solution for free backups of your wordpress website. You can use one of many available Dropbox plugins. Everything works out of the box. 😉