Hello All, If you re having problems with bounce on qmail, if you re desperate about qmail getting crazy with thousands of email, then, let me tell you, that your quest ends here! The tools that will be used in this “kind of tutorial” are included right here :
Basic things you should know [*]Where are the mail stored ? Usually, for a mail like email@example.com you ll find the emails in /var/qmail/mailnames/mydomain.com/hello/Maildir/new or /cur. You can view their content with nano or vi or any text editor, and read them from your linux console, given they do not contains too much html gibberish.
[*]Where is the queue stored ? The queue, is the as it sounds to be, “all the mails that have not been yet delivered” (delivered to a local user or to a remote user(not hosted on your mail server))
Delivering the queue to the local users is not a big process, but delivering it to remote destination, well, might give a hard time to qMail sometimes ! (as for any other mail system of course) So, the queue is physically stored in folders within /var/qmail/queue/ Let’s not bother with the details of all folders in that path, for the moment, we dont care.
When Apache HTTPD web server generates any web pages or error pages, some important information about the version and other details implemented on the system are displayed in th web site server header. For example, the information text may be like this:
Server: Apache/2.0.53 (Ubuntu) PHP/4.3.10-10ubuntu4 Server at xx.xx.xx.xx Port 80
The line in the server header expose important version and variant information about the Linux operating system and Apache software used on the machine, indirectly expose the possible security holes that are existed to the hackers, or at least make malicious attackers easier to identify your system for available attack points.
To ensure that the Apache HTTP web server does not broadcast this message to the whole world publicly and fix possible security issue, modify these two directives ServerTokes and ServerSignature in httpd.conf configuration file.
I accidentally broke my installation quite badly, but luckily I had some settings and other bits and pieces ready for just this occasion. Note that the following is for Debian based systems!
Step One – Get a list of installed packages
Once you have your machine set up more or less as you want it, export the list of installed packages to a file like this:
dpkg --get-selections > package.list
Step Two – keep the list safe!
Keeping the list safe is more important than keeping it up to date. I keep mine in my DropBox account with a few other essential items. Using DropBox means I can grab the file via the web if I need it in a hurry. Not much point if I needed to install DropBox before I could access the file!
Step Three – Recover the Backup
Bring everything back in one massive update if things go wrong: sudo dpkg --set-selections < package.list
sudo apt-get dselect-upgrade
Warning, the final step will probably take some time to finish, and while it is pretty good it won't be perfect - you may want to include your apt sources in DropBox too. Personally I find it preferable to the manual option.
For those who love using the terminal, here is a ‘.bashrc’ file I created, mainly for those who’ve had issues with their own. Hopefully it’ll benefit those of whom love aliases, functions, and such. Probably more than you need, so modify all you want. I’ve organized it best I can to make it easier for using and modification. This is also for those many who’ve had a difficult time finding a good source for their own on the net, like it was for me.
Oh, and any modifications that others wish to share are always welcome.
Just extract the tar file and put in your home directory. You may have to overwrite the current one, so be sure to backup whatever beforehand. FYI, the default text in the ‘.bashrc’ is included in this version so if you haven’t modified it at all, you should have nothing to worry about.
To refresh it, just type in the terminal:
…or just close your terminal window and open it again.
Patience is a virtue, but for many, it is often a difficult concept to practice. That is especially true for web users visiting a website that takes a long time to load. Users are enamored with speedy websites, and when a site responds slowly, visitors lose their patience and are less likely to come back.
Improving the speed of your website is important not only to users, but to search engine rankings as well. Last April, Google announced that they are now including website speed in their search ranking algorithms.