Linux Tips, Tricks, Tutorials & Fixes

Here are the following few things that you should do at your end: -->> Plugins: Before you install any plugin on your website, ask yourself “Is this plugin necessary?”. Plugins are one of the biggest causes of WordPress websites being slow. The more plugins you install without research, the more likely you will face performance issues; however the sheer number of plugins you have installed is not the reason a WordPress website can slow down. Certain plugins are known for causing websites to be slow. There are many reasons for this including bad coding, calls to external servers and persistent calls and updating of your WordPress database. Pay close attention to how much CPU plugins use too. Many plugins can bottleneck your CPU due to persistent processes. -->> Themes: A design that has been coded badly, or uses images throughout the design, will add unnecessary weight to your page. It is not uncommon for some WordPress themes to be a few megabytes in size. Such...

Here are 7 possible causes for slow-loading pages. 1. Un-Optimized Images This is usually the most common reason for slow websites; there are lots of images, all of which are full-size and uncropped. 2. Use of Server-Intensive Dynamic Scripts Dynamic websites, such as those that generate their pages from data stored in databases, are slower than simple HTML websites. And while the slight delay is not often noticed on small, low-traffic websites, it is often noticeable as a website increases in size and popularity. To remedy this situation, we suggest caching. Caching enables you to store copies of frequently accessed dynamic documents and allows files to be accessed more quickly. 3. No Compression of Web Pages Another way to speed up your website is to compress your pages. 4. Too Much Flash Flash is a great tool for adding interactivity or animation to a website. However, flash is also very bulky and causes websites to load slowly. So when creating your flash...

When troubleshooting mail or attempting to discover the source of spam originating from your server, it is often useful to enable extended Exim logging. To enable extended logging in Exim to trace nobody mails. Try the following trick . 1. Edit /etc/exim.conf 2. On the second line add : log_selector = +address_rewrite +all_parents +arguments +connection_reject +delay_delivery +delivery_size +dnslist_defer +incoming_interface +incoming_port +lost_incoming_connection +queue_run +received_sender +received_recipients +retry_defer +sender_on_delivery +size_reject +skip_delivery +smtp_confirmation +smtp_connection +smtp_protocol_error +smtp_syntax_error +subject +tls_cipher +tls_peerdn \ Make sure all that comes on a single line. 3. Save and exit. 4. Restart Exim.

Use following two script to catch the spammer. 1. exim -bpr | grep "<*@*>" | awk '{print $4}'|grep -v "<>" | sort | uniq -c | sort -n That will show you the maximum number of emails currently in the mail queue have from or to the email address in the mail queue with exact figure. 2. exim -bpr | grep "<*@*>" | awk '{print $4}'|grep -v "<>" |awk -F "@" '{ print $2}' | sort | uniq -c | sort -n That will show you the maximum no of email currently in the mail queue have for the domain or from the domain with number. Also you can try following command that will show you the script which is using script to send the email. If it is from php then use /var/spool/exim/input egrep "X-PHP-Script" * -R Just cat the ID that you get and you will be able to check which script is here causing problem for you. That may help you a lot to catch the spammer.